ISTQB Certification Path Quiz

An individual who specializes in identifying and resolving problems within a software system, typically focusing on improving its quality and functionality.

A comprehensive set of guidelines and standards used for evaluating and improving the quality of software development.

A model or framework that predicts the likelihood of defects in software based on various factors.

A set of methods and techniques employed during the software development process to ensure the quality and functionality of the final product.

The process of measuring and analyzing different aspects of software development, such as code complexity, code coverage, and defect density.

A certification program focused on software testing, offering various levels of accreditation based on knowledge and skills.

A process that aims to improve the overall quality and effectiveness of software testing activities.

A role that focuses on providing guidance and training to individuals involved in software quality, helping them achieve excellence in their work.

A system for classifying and evaluating software testing qualifications.

The most basic level of ISTQB certification, ideal for anyone starting in software testing. It's the foundation for further development.

A set of certification levels that progress from basic knowledge to advanced expertise in software testing.

A specialized testing role, often working closely with developers, focusing on the technical aspects of testing.

A testing role that involves analyzing and applying test processes to improve their effectiveness.

A skilled software tester who applies the principles of agile methodologies to their work.

A testing role focused on managing and leading a team of testers using agile principles.

A specialized testing role focused on providing assurance that a software product meets user needs and business requirements.

A black-box testing technique where input values are grouped into partitions based on expected behavior. Test cases are created to cover each partition, ensuring thorough testing across different input scenarios.

A black-box testing technique focused on testing values at the boundaries of each input range. This technique helps identify potential defects at the edges of valid input.

A white-box testing technique that aims to execute every statement in the source code at least once. This technique helps ensure code coverage and identify potential issues within individual code statements.

A white-box testing technique that focuses on exercising both the true and false branches of each decision point in the code. This technique helps identify logic errors within conditional statements.

A test technique based on the system's state transitions and how they react to different events. It helps identify potential issues in the system's state management and transitions between them.

A test technique that uses a collaborative approach, involving developers and business representatives in defining user stories and acceptance criteria for each feature or functionality. This technique promotes better understanding and alignment between development and business stakeholders.

A test technique that uses a structured approach to create test cases based on a predetermined set of rules or procedures. This technique often relies on predefined templates and checklists to ensure comprehensive test coverage.

A test planning element outlining the conditions that must be met before a test can begin. This often includes factors like availability of test environment and test data.

The process of finding and assessing software defects, improving quality and reducing the risk of failure.

A work product created during the testing process to aid in planning, designing, executing, evaluating, and reporting on testing.

Confirms that a software component or feature meets the needs of the stakeholders.

Confirms that a software component or feature complies with the specifications.

A set of activities conducted to detect problems and evaluate software artifacts.

Testing activities are organized and conducted differently based on the development lifecycle.

Testing is frequently seen as verifying that the software meets the specified requirements but it also involves other aspects.

The mistaken belief that testing is limited to executing tests, the process involves many more activities.

The process of figuring out why a software failure happened, like finding the specific code that caused the issue.

A step for debugging where you recreate the problem to examine it in a controlled environment, ensuring the problem consistently occurs.

A task in debugging where you identify the root cause of the software failure, aiming to locate the exact area or code causing the problem.

After fixing a bug, you test the software again to make sure the fix really worked and the issue is gone.

Tests designed to ensure that fixing a bug hasn't accidentally broken other parts of the software.

The process of finding defects in code before you even run the software. It doesn't involve running the program but analyzing the code directly.

Fixing defects found during static testing is simpler than fixing failures in dynamic testing, as you already know where the problem is.

A type of software testing where you run the program to see how it behaves. This is in contrast to static testing, which only examines the source code.

A graphical representation of a system's behavior, showing its possible states and the transitions between them.

A technique used to detect problems with system requirements, such as inconsistencies or missing elements.

The condition of a system or component at a particular time.

An action or event that triggers a change in the system's state.

The process of evaluating a software system to ensure that all possible combinations of conditions and corresponding actions have been tested.

A combination of conditions that is impossible to achieve in a real-world system.

The total number of possible combinations of conditions in a decision table.