Question :-
Suppose Amazon overtake Walmart but there is no merging of any content. Both will be working as two different websites at the front end but will be sharing a common backend process. Please specify the Test scenarios, plan and what kind of testing would you do.
Answer:-
1. As the backend of both e-commerce sites will be same, then the both sites user database should be one
2. User money transactions done in both sites should be reflected in one major account with detailed transactions details of every transaction.
3. The sellers who are tied up respective company there database needs to be maintained pretty well
4. When merged the backend of both, there should be no conflicts in user ids, we should also check the scenarios of users who are registered with both sites.
5. As the front end didn't changed, there should not be mix up in the front end products(as the backend is same, the products of respective sites should not be displayed in the other sites)
6. The promotional mails which will be sent to their respective registered users list should not get mixed(Amazon users should not get walmart mails and vice-versa)
7. If any offers Amazon is offering the same should not get affected or applied to walmart.
8. The money in their respective wallet should not get affected.
9. The respective apps must function same like before merge
10. When one site's changes are made and pushed to the server, the other site functionality should not get affected.
Etc etc
Question:-
Suppose you have a mobile application ready and working fine now client want to have a same application on the website having same functionality. How it will make you change in terms of testing. what are the things you will keep in mind and how will you make test plan of it.
can somebody help and give me the best answer of it.
2. User money transactions done in both sites should be reflected in one major account with detailed transactions details of every transaction.
3. The sellers who are tied up respective company there database needs to be maintained pretty well
4. When merged the backend of both, there should be no conflicts in user ids, we should also check the scenarios of users who are registered with both sites.
5. As the front end didn't changed, there should not be mix up in the front end products(as the backend is same, the products of respective sites should not be displayed in the other sites)
6. The promotional mails which will be sent to their respective registered users list should not get mixed(Amazon users should not get walmart mails and vice-versa)
7. If any offers Amazon is offering the same should not get affected or applied to walmart.
8. The money in their respective wallet should not get affected.
9. The respective apps must function same like before merge
10. When one site's changes are made and pushed to the server, the other site functionality should not get affected.
Etc etc
Question:-
Suppose you have a mobile application ready and working fine now client want to have a same application on the website having same functionality. How it will make you change in terms of testing. what are the things you will keep in mind and how will you make test plan of it.
can somebody help and give me the best answer of it.
Answer :-
1. First we should test the screen alignment in web application when accessed through browser
2. Security testing needs to be done from different browsers
3. Load and stress test needs to be done
4. Extra functionalities as per the req should be tested
5. User database should be verified
6. Compatibility with browsers needs to be tested
7. Screen resolution needs to be tested
8. Offline functionalities should be tested
9. Negative testing like while user browsing that webpage what if power goes off and internet goes off
10. Interruption testing like, while using that webpage receiving skype call, PC updates, antivirus updates etc...
1. First we should test the screen alignment in web application when accessed through browser
2. Security testing needs to be done from different browsers
3. Load and stress test needs to be done
4. Extra functionalities as per the req should be tested
5. User database should be verified
6. Compatibility with browsers needs to be tested
7. Screen resolution needs to be tested
8. Offline functionalities should be tested
9. Negative testing like while user browsing that webpage what if power goes off and internet goes off
10. Interruption testing like, while using that webpage receiving skype call, PC updates, antivirus updates etc...
Post a Comment