Old SWQA

Debugging round interview questions with answers. These are real questions asked in real interviews.  1. When you come in the morning, SLA has increased for the job searching portal (website). It was fine till today morning. How are you going to debug it? There is a matrix that shows service and it’s SLA. What are the steps you are going to take to debug this problem? Answer : If the SLA has gone up suddenly it's definitely a critical issue. I will first report this problem to all stakeholders. I will check listed points to debug the problem - 1. Check what went in the latest release if that is one  2. Check for nodes that are down. If there is an unusual number of nodes that are not reachable then report it to the infrastructure team. 3. Check for database repair which can cause slowness 4. Check its client-side delay or server-side delay to narrow down the issue 5. Check the geolocation of where the website is slow in order to narrow down 6. Check network bandwidth in the da...

Different types of Software Testing: Functional Testing types: Unit Testing: Individual units or components of the software are tested. A unit is the smallest testable part of the software. This is usually not manual and mostly done by developers as they write code. Integration Testing: Testing of all integrated modules of the software to make sure modules once combines works as expected or not. The best example would be FE and BE integration testing. System Testing:  The entire system is tested as per the defined requirements. Black box testing performed by QA. End to End Testing: Same as System testing but mimics more real-world use cases and interactions with network, databases and real users. Most companies combine system testing and end-to-end testing as there is a very thin line between both. Sanity Testing: Sanity testing is performed by the QA team to determine SW which is released is ready to do a full round of testing or not. This is usually quick and covers basic func...

What is a test case? A Test Case is a set of actions executed to verify a particular feature or functionality of your software application. The Test case has a set test data, precondition, certain expected and actual results developed for a specific test scenario to verify any requirement. Why test cases are important? Test cases ensure good coverage Test cases are reusable Once written, anyone can execute it If there are no other documents, test cases can be used as baseline documents It's easy to trace the history of pass/fail rate of the particular feature Overall, it helps to improve the quality of the product Who will use test cases? Manual testers, automation testers, developers and management What is a good test case? A good test case or a well-written test case should allow any tester to understand and execute the test How to write a good test case? The main idea is to keep test cases simple, precise, reusable, to focus on one goal an...

This list contains test scenarios for a generic login page E2E positive test cases Verify that valid user name and valid password works Verify login by providing registered phone number (many test cases has to be repeated) Verify that password is hidden and not visible after typing Verify forgot password functionality Verify 2FA functionality Verify concurrent login (maximum number of allowed login sessions at once) Verify “Remember Me” functionality Verify once you click next, after entering a username, password page is visible Verify once you are on password page, you can edit the username Verify login page has an option to create a new account for the first time users If the account is created in one country and accessed in another country, OTP should be asked (If OTP is supported) If the account is accessed simultaneously in two diff countries - OTP should be asked Verify that OTP is asked when the user tries to log in on different machines Verify for username requirements such as ...