A set of instructions to test a software program

A bug reports

A user manual

A set of requirements

Verification is checking whether the software is built right, while

validation is checking whether the right software is built.

Verification is checking whether the software meets the requirements, while validation is checking whether the software works correctly.

Verification and validation mean the same thing.

Verification is done by the development team, while validation is done by the testing team.

Testing without any knowledge of the internal workings of the software

Testing with knowledge of the internal workings of the software

Testing performed by the end-users

Testing performed by the developers

Testing without any knowledge of the internal workings of the software

Testing with knowledge of the internal workings of the software

Testing performed by the end-users

Testing performed by the developers

Testing a new version of the software

Testing the software after a defect has been fixed

Testing the software after a change has been made

Testing the software after a new feature has been added

Testing performed by the development team

Testing performed by the testing team

Testing performed by the end-users

Testing performed by the client

Functional testing tests the software's features, while non-functional testing tests its performance and security.

Functional testing tests the software's performance, while non-functional testing tests its features.

Functional testing and non-functional testing mean the same thing.

Functional testing tests the software's security, while non-functional testing tests its performance

Testing the software with no plan or documentation

Testing the software based on a detailed test plan

Testing the software based on user feedback

Testing the software based on a set of requirements

A set of instructions for executing a test case

A document that outlines the approach and scope of testing

A tool used for automating testing

A report that documents the results of testing

To prove that the software works as intended

To find defects and issues in the software

To increase the speed of software development

To reduce the cost of software development

Verification is checking that the software meets the requirements, while validation is checking that the software works as intended.

Verification is checking that the software works as intended, while validation is checking that the software meets the requirements.

Verification and validation mean the same thing.

Verification and validation are not related to software testing

Regression testing tests the same functionality multiple times, while retesting tests the software after defects have been fixed.

Regression testing tests the software after defects have been fixed, while retesting tests the same functionality multiple times.

Regression testing and retesting mean the same thing.

Regression testing tests new functionality, while retesting tests existing functionality.

Functional testing tests the software's features, while non-functional testing tests its performance and security.

Functional testing tests the software's performance, while non-functional testing tests its features.

Functional testing and non-functional testing mean the same thing.

Functional testing tests the software's features, while non-functional testing tests the software's behavior under stress.

To test the extremes of input values

To test the most common input values

To test the least common input values

To test the input values with the highest priority

To test the software's functionality under different loads

To test the software's internal structure and code

To test the software's performance under stress

To test the software's security vulnerabilities

Static testing is testing without executing the software, while dynamic testing is testing by executing the software.

Static testing is testing by executing the software, while dynamic testing is testing without executing the software.

Static testing and dynamic testing mean the same thing.

Static testing is testing by observing the software, while dynamic testing is testing by modifying the software.

To test the software's functionality under different loads

To test the software's performance under stress

To test the software's security vulnerabilities

To ensure that the software meets the user's requirements

Black box testing is testing by executing the software, while white box testing is testing without executing the software.

Black box testing is testing without knowledge of the internal structure of the software, while white box testing is testing with knowledge of the internal structure of the software.

Black box testing and white box testing means the same thing.

Black box testing is testing by observing the software, while white box testing is testing by modifying the software.

To find as many defects as possible

To ensure that the software meets the user's requirements

To complete testing as quickly as possible

To minimize the cost of testing

To ensure that the software meets the user's requirements

To find defects and issues in the software

To document the steps for executing a test

To evaluate the performance of the software

A collection of test cases

A collection of test data

A collection of test plans

A collection of test scripts

Testing that is performed without any documentation

Testing that is performed without any specific goals or objectives

Testing that is performed without any knowledge of the software

Testing that is performed to discover and learn about the software

To find defects and issues in the software

To prioritise defects and issues for resolution

To document and track defects and issues through resolution

To ensure that all defects and issues are resolved before release

A set of tools and processes used for automated testing

A set of guidelines for manual testing

A set of rules for software development

A set of standards for documentation

The physical location where testing is performed

The hardware and software used for testing

The process of setting up and configuring the testing environment

The set of conditions under which testing is performed

A document that outlines the results of testing

A document that outlines the goals of testing

A document that outlines the approach for testing

A document that outlines the resources required for testing

To provide an overview of the testing process and results

To provide detailed information about the testing process and results

To provide a list of defects and issues discovered during testing

To provide recommendations for future testing

Testing that is focused on high-risk areas of the software

Testing that is focused on low-risk areas of the software

Testing that is performed without any specific goals or objectives

Testing that is performed to evaluate the performance of the software

Developing test plans and test cases

Executing test cases and reporting defects

Managing the testing process and team

Analysing test results and making recommendations

To reduce the time and effort required for testing

To eliminate the need for human testers

To increase the accuracy and reliability of testing

To ensure that all testing is performed consistently and uniformly

To provide a high-level overview of the testing approach and goals

To provide a detailed plan for testing the software

To provide a list of all test cases and scripts

To provide a detailed analysis of the software's performance