Scenario-Based Manual Testing Interview Questions

1. How would you test a login page?

• To test a login page, you would:
• Check the login functionality with valid and invalid credentials.
• Test the login with different combinations of usernames and passwords (e.g., empty fields, incorrect password).
• Verify the response to incorrect login attempts (e.g., error messages).
• Test the behavior when the username and password fields are left empty.
• Check for password masking (password characters should be hidden).
• Test the “Forgot Password” functionality.
• Verify the behavior after multiple failed login attempts (e.g., account lockout).
• Test the session management (e.g., login and logout).
• Verify security aspects like SQL injection, XSS attacks, etc.

2. How would you test a shopping cart application?

• To test a shopping cart application, you would:
• Add items to the cart and verify that they are correctly added.
• Remove items from the cart and check that they are removed.
• Update the quantity of items and verify the total price calculation.
• Test the cart’s behavior with an empty cart (e.g., should not proceed to checkout).
• Verify the checkout process (e.g., shipping address, payment options).
• Check for data persistence (e.g., items should remain in the cart after page refresh).
• Test for security aspects (e.g., unauthorized access, data encryption).
• Verify the application’s responsiveness on different devices and screen sizes.

3. How would you test a mobile app using mobile testing?

• To test a mobile app with mobile testing, you would:
• Verify the app installation and uninstallation process.
• Test the app’s functionality and features as per the requirements.
• Check the app’s performance (e.g., loading time, responsiveness).
• Test the app’s behavior under different network conditions (e.g., offline, 3G, 4G, Wi-Fi).
• Verify the app’s compatibility on different devices, OS versions, and screen sizes.
• Test for usability (e.g., navigation, touch gestures, UI elements).
• Verify data security and privacy aspects.
• Test the app’s integration with device features (e.g., camera, GPS, push notifications).

4. How would you test a website?

• To test a website, you would:
• Verify the website’s functionality (e.g., forms, links, buttons).
• Check the website’s responsiveness on different devices and screen sizes.
• Test the website’s performance (e.g., page loading time, speed).
• Verify cross-browser compatibility (e.g., Chrome, Firefox, Safari, IE).
• Test the website’s security aspects (e.g., SSL certificate, data encryption, vulnerability scanning).
• Check for broken links and images.
• Test the website’s usability (e.g., navigation, readability, user interface).
• Verify the website’s content and its consistency.

5. How would you test a web service?

• To test a web service, you would:
• Verify the web service’s request and response format (e.g., XML, JSON).
• Test the web service’s functionality by sending different requests (e.g., valid, invalid).
• Check the web service’s response time and performance.
• Verify the data integrity and accuracy of the responses.
• Test the web service’s error handling (e.g., error codes, messages).
• Verify the web service’s security aspects (e.g., authentication, authorization).
• Test the web service’s behavior under different network conditions.

Most Frequently Asked Manual Testing Interview Questions

1. What is software testing?

Software testing in Performance testing is the process of evaluating and verifying that a software application or system meets specified requirements. It involves executing the software or its components to find errors, bugs, or other issues.

2. When should you stop the testing process?

• The testing process can be stopped when:
• All critical test cases are passed.
• The software meets the defined acceptance criteria.
• The defect rate falls below a certain level.
• The testing deadline or budget is reached.
• The risk of continuing testing outweighs the benefits.

3. What do verification and validation mean in software testing?

Verification is the process of checking whether the product meets the specified requirements and is being built correctly through techniques such as functional testing. Validation is the process of checking whether the final product meets the business needs and requirements, ensuring that the right product is built.

4. What is static testing? When does it start and what does it cover?

Static testing is a type of software testing that involves checking the code, requirements, or design documents without executing the code both . It starts early in the software development life cycle and covers activities such as reviews, inspections, and walkthroughs.

5. Define black-box testing.

Black-box testing is a software testing method where the internal structure or workings of the application are not known to the tester. The tester validates the functionality of the application by inputting data and verifying the output against the expected results.

6. Mention the different types of software testing.

The different types of software testing include manual testing, automated testing, functional testing, non-functional testing, unit testing, integration testing, system testing, security testing, user acceptance testing (UAT), regression testing, and performance testing.

7. What is meant by test coverage?

Test coverage is a metric used to measure the extent to which the testing process covers the application’s code, requirements, or functionality. It helps in identifying areas that are not covered by tests and ensures comprehensive testing.

8. Is it possible to achieve 100% testing coverage? How would you ensure it?

Achieving 100% testing coverage is challenging and often not practical. However, it can be approached by:

• Thoroughly analyzing requirements and creating detailed test cases.
• Using test coverage tools to measure and track coverage.
• Prioritizing testing based on risk and criticality.
• Regularly reviewing and updating test cases to cover new changes.

9. What are unit testing and integration testing?

Unit testing is a type of software testing that focuses on testing individual components or modules of software. Integration testing is a type of testing that focuses on testing the interaction between integrated units or modules to ensure they work together as expected.

10. Can we do system testing at any stage?

System testing is typically performed after integration testing when the entire system is integrated and ready for testing. It is conducted to validate the system’s end-to-end functionality against the specified requirements. Performing testing software at any stage may not provide accurate results, as the entire system may not be fully integrated.