Software Testing Techniques Quiz

A set of activities to discover defects and evaluate the quality of software work products.

The software work product being tested.

Goals of testing, like evaluating work products, finding defects, and verifying requirements.

Testing finds defects; debugging fixes them.

General guidelines for all aspects of software testing.

Attempting to test every possible scenario, which is impossible for most software.

Finding defects early in the development process to save time and money.

A small number of components often have the majority of defects.

Repeated tests can become less effective at finding new defects.

No single testing method works for every project.

Verification doesn't guarantee success; validation is also crucial.

Set of activities involved in testing, often tailored to the specific situation.

Defining test objectives and choosing the best approach to achieve them.

Ongoing check of test progress and actions taken to meet objectives.

Analyzing the test basis to identify testable features and prioritize test conditions.

Elaborating test conditions into test cases and other testware.

Creating or acquiring testware for test execution.

Running tests and comparing actual results to expected results.

Assessment and reporting of testing at a project milestone.

All work products created, supporting the overall testing process, including the test plan, test cases, test data, and more.

Tracking connections between work products in testing, such as between test cases and requirements.

Responsibilities for test management (overall process) and testing (technical aspects).

Skills like thoroughness, communication, analytical thinking, and technical knowledge needed by testers.

A practice from XP where any team member with relevant skills can take on testing roles.

Testers testing without direct involvement from developers, to improve defect finding.

A high-level blueprint of the software development process, showing how different phases and activities relate to each other. Examples include waterfall, V-model, spiral, prototyping, iterative, and incremental models.

A set of principles and practices that emphasize iterative development, collaboration, and rapid feedback, promoting flexibility and responsiveness to change.

Methods like TDD, ATDD, and BDD where tests are defined before writing any code, driving development and ensuring testing is a core part of the process.

A philosophy and set of practices that aim to integrate development and operations, automating processes and ensuring seamless delivery of software.

Moving testing activities to earlier phases of the SDLC, catching defects sooner and reducing costs.

Team meetings after development cycles to review successes, failures, and identify areas for improvement in the process.

Different stages of testing, each with specific objectives and focused on a particular level of the software, ranging from unit testing to system integration testing.

Testing individual units of code (functions, classes, modules) in isolation, primarily done by developers.

Testing individual components or modules in isolation, often done by testers or developers with a deeper understanding of the component.

Testing how different components interact with each other, ensuring they work together as intended.

Testing the entire system as a whole, ensuring it meets all requirements and works as expected.

Testing how the system integrates with external systems or components, like databases or other applications.

Confirming the system is acceptable to the users and stakeholders, focusing on user stories, acceptance criteria, and business needs.

Different categories of testing based on the goals and approaches, such as functional testing (checking features), performance testing (checking speed), and security testing (checking vulnerabilities).

Testing the functionality of the software, ensuring it performs actions as specified, like calculating a result or displaying data correctly.

Testing aspects other than functionality, like performance, security, usability, reliability, and maintainability.

Testing how the software performs under various load conditions, measuring response times, throughput, and resource utilization.

Testing the software's vulnerability to attacks, identifying security flaws and weaknesses like SQL injection or unauthorized access.

Testing how easy and enjoyable the software is to use, gathering feedback from real users on the interface and overall experience.

Retesting after a fix is applied, to verify the defect is resolved and the software works correctly.

Retesting existing functionality after changes are made to the software, ensuring that the new changes have not introduced any new defects.

Testing the software after it is released, ensuring any changes or updates do not introduce new defects or affect existing functionality.

Testing the software based solely on its external behavior and specifications, without knowledge of its internal structure or code.

Testing the software based on its internal structure and code, analyzing code paths, branches, and conditions, to ensure thorough coverage.

The documents and information that serve as the foundation for testing, including requirements specifications, design documents, user stories, and acceptance criteria.

Input values used during test execution to evaluate the software's behavior and compare it to expected results.

A detailed set of instructions used to automate the execution of a test case, often involving a test automation tool.