Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
3 views2 pages

Corrected Manual Testing Interview QA

The document provides a comprehensive overview of manual testing concepts, including definitions, purposes, and key differences between related terms. It outlines when to stop testing, the advantages of automation, and distinguishes between regression testing and retesting, as well as between builds and releases. The content serves as a guide for interview preparation in software testing roles.

Uploaded by

asustuf305
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views2 pages

Corrected Manual Testing Interview QA

The document provides a comprehensive overview of manual testing concepts, including definitions, purposes, and key differences between related terms. It outlines when to stop testing, the advantages of automation, and distinguishes between regression testing and retesting, as well as between builds and releases. The content serves as a guide for interview preparation in software testing roles.

Uploaded by

asustuf305
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Manual Testing Interview Q&A - Corrected & Enhanced

Q1. What do you mean by Software Testing?

Software testing is the process of evaluating and verifying that a software product or application

does what it is supposed to do. It helps identify bugs or issues to ensure the product meets quality

standards. It evaluates the software in terms of correctness, completeness, usability, performance,

and security.

Q2. Why is testing required?

Testing is essential to:

1. Ensure the product meets business and user requirements.

2. Detect bugs early, reducing cost and time to fix.

3. Provide quality assurance to stakeholders.

4. Prevent revenue loss or reputation damage from defective software.

5. Improve the development process via feedback and verification.

Q3. When should we stop testing?

Testing can be stopped when:

1. All test cases are executed with acceptable pass percentage.

2. Testing deadlines are met with no high-priority bugs.

3. Code coverage and test coverage reach a defined threshold.

4. Risk analysis suggests residual defects are acceptable.

5. Stakeholders formally agree on test completion.

*Note: 100% test coverage is rarely practical.*

Q6. What is the difference between Verification and Validation?

Verification: Ensures the product is built correctly (i.e., process compliance).

Validation: Ensures the correct product is built (i.e., meets requirements).


- Verification is static (reviews, walkthroughs).

- Validation is dynamic (actual testing).

- Verification answers: Are we building the product right?

- Validation answers: Are we building the right product?

Q12. What are some advantages of automation testing?

1. Faster execution and reusability of scripts.

2. Reduces human error.

3. Supports continuous integration via CI/CD tools.

4. Saves manual testing effort for repetitive tasks.

5. Provides detailed test reports with minimal QA involvement.

Q85. What is the difference between Regression and Retesting?

- Regression Testing: Verifies new changes haven't broken existing functionality.

- Retesting: Confirms that a specific bug fix works.

Retesting is done on the same defect; regression is on overall application.

Q88. What is the difference between Release and Build?

- Build: A version of the software shared for internal testing.

- Release: A stable version deployed to end users after complete testing.

*Release notes usually include versioning, fixes, and known issues.*

You might also like