Amazon came to my college (Tier 3) for QAE Intern leading to Placement role on AUGUST 2021, during my 7th SEM.

These are my notes that I prepared on my own, which got me the offer.

These notes are made after scavenging the web for Amazon QAE, or QAE in general previous interview experiences from Articles, Leetcode Discussions, Glassdoor, YouTube videos etc.

1. Questions related to Job Description

2. Testing Scenarios

3. A scenario is given then you will need to write test cases and also tell the strategy you will use to tackle that scenario
   I am at my best when under pressure and can always be relied upon to be resilient, innovative and determined

4. Make a test plan for a website that uploads and downloads files

   • To start with I want to ask you more about the scope of the problem at hand
   • Are we focusing on a generic website having just the feature of uploading any type of file type of any size and then just download it, and it has just 2 buttons ?
   • Thats great
   • One more question, is the webiste in production and live, or is it in local
   • Thats great to know
   • I would like to structure my answer into the following parts : UI, Fucntional, Backend, Performance, Database, Accessibility test cases/plan
   • UI -> I would test whether the website's look and feels remains coherent across both desktop and mobile environments, across differnt aspect ratios and across firesticks tv or such appliance.
   • Functional -> I would test wheather all the files types like JPG, Jiif, py, c, cpp, ipynb, pdf, doc, txt etc are successfully uploaded
   • Weather the different file sizes are supported like KB, MB, GB, TB
   • Backend -> I would open up postman and fire a response from there, and check if I am getting a status 200 OK or not, both while firing the upload and download functionality.
   • Performance -> I would check the working of the app accross differnt network speeds, like 2G, 3G, 4G, 5G or direct LAN support, it should be able to still download and upload they file though the speeds are low in the lower connectivity rates
   • Database -> I would open up the server side logs and check if the responses are fine or not, and also check out the console errors
   • Accessibilty -> I would test out the text-to-speach feature were, I have to ensure the correct location of the upload and download buttons are being pointed out along with the options of the files what to upload

5. Scenario based and some testing scenario's

6. Few technical questions regards on skills mention in resume.

7. Find the sum of digits in a number

8. Tranversing from back to front and vice versa of an array

9. What are the things to be tested when considered a mobile App

• To start with I want to ask more about the scope of the problem at hand
• We know that every app has a functionality around which all its feature revolves around what's the feature of this app
• Thats great to know
• My next question is, is the app in production and live, or is it in local
• I would like to divide my answer into the following parts : UI, Functional, Backend, Performance, Database and Accessibility test cases/plan.
• UI -> As its a mobile app so, the feature using in a desktop environment is not there, therefore for UI i would test weather the look and feel of the differnt screens of the app remain same across differnt aspect ratios of devices.
• Funct -> I would start by testing the login screen, as its the first thing that usually pops up when one opens a app
  • I would test whether the username, email and password are following the regex rules that they are meant to follow
  • Test the search feature passing in different catogary of items,
  • Test wheather the add to cart button is working or on and the count of items getting inserted is maintained
  • Test the payment feature with all the modes of payment and check if the linking of credit/debit card option is working
  • I would test the filter tab where, I will test each range of value is actually resulting in the search results
  • I would test the logout feature and change user feature

10. Did you ever debuged anything and reported any bugs ?

11. Given a pen and told me to write positive, negative and end to end scenarios test cases for that.

12. Test cases based on a scenario. A scenario is given then you will need to write test cases and also tell the strategy you will use to tackle that scenario.

13. How you'll test "add pay card" page ?

14. Mobile application testing to chat bots testing

15. How would you test a chat bot option on web page

16. Assume you are watching Amazon prime on a laptop and all of a sudden it stops working. How would you debug

17. Find a pair such that the product is maximum

18. Check if first string is anagram of second

19. How do you test an e-commerce application ?

20. Count of characters in string, test case generation for payment page, test data generation

21. Closest Palindrome to the number

22. Find array contains duplicate numbers

23. Amazon Leadership Principle

24. Test Data Generation

The role of a quality assurance engineer is to follow a set of activities and methodologies (like SRS, FRS, and BRS) designed to ensure that the developed software meets all the required specifications.
SRS = Software Requirement Specification, summary of project covering the functionality and features of a technology, and desired business goals, advantageous for cutting down the non-productive parts.
FRS = is the most detailed document laid out by developers and testers, covering all the software components and expected interactions, business aspects, compliance, and security requirements
BRS = The product performance expectations, key targets, as well as other business objectives the client is seeking to achieve with a certain product

Give test cases for add to cart button

• Ask about scope of the problem
• Are we focusing on a single type of button or is it generic
• Are you expecting a answer for a specific platform (like OS), or generic
• Should the answer be local specific
• Structure your answer => Whether it is UI, Fucntional, Backend, Performance, Database or Accessibility test case *
• UI -> Can talk about language localisation (looks fine when a differnt language is inside that)
• Can talk about responsiveness, like aspect ratio, browser
• Funcional -> Testing on a firetv, or any global platforms
• Performance -> its a very business critical, load, stress, chaos testing, testing on network speeds, like 2G, 3G, 4G, (through throtlling)
• Accessibilty -> Screen readers, placement of button
• Handle error scenarios

Straight forward P0 test cases
Selenium -> automate a login in gmail
It would also change according to the locals

Debugging why the add to cart button is not working :

• Try to check internet connection
• Try to check for differnt tabs, incognito mode
• Inside : did it start happening after the code was moved into production
• Did it start happening after a new update/release was pushed
• See the console errors
• see the server side logs
• Try to hit the api through postman and check if we are getting a successfull response

• Ability to write test plan for the feature, execute and maintain
• Knowledge of Test Case Enumeration and Test Data Generation
• Strong knowledge of QA methodology and tools
• Ability to understand technical specifications and analyze log files.
• Knowledge in Java/Perl/Python based automation
• Good coding knowledge and problem solving skill (for automation)
• Knowledge with testing methodologies such as regression, automation, monkey testing, etc.

Black Box Testing - It is a way of software testing in which the internal structure or the program or the code is hidden and nothing is known about it. Mostly done by software testers.

Functional Testing - It verifies the operations and actions of an application. Based on requirements of customer.

Non-functional testing - It verifies the behavior of an application. It is based on expectations of customer.

Regression Testing - is the process of testing the modified parts of the code and the parts that might get affected due to the modifications to ensure that no new errors have been introduced in the software after the modifications have been made.

Regression means return of something and in the software field, it refers to the return of a bug.

White Box Testing - It is a way of testing the software in which the tester has knowledge about the internal structure or the code or the program of the software. Done by software developers.

Please UPVOTE if you found this helpful :)