Which of the following best describes the way in which statement coverage is measured?
Answer : C
Statement coverage is a metric used in white-box testing that measures the percentage of executable statements in the code that have been executed by the test cases. It is calculated as the number of statements executed by the tests divided by the total number of executable statements in the code, providing an indication of how much of the code has been tested.
You are an experienced tester on a project with incomplete requirements and under pressure to deploy.
What type of testing should you do?
Answer : D
When working on a project with incomplete requirements and under pressure to deploy, exploratory testing is particularly suitable. This type of testing allows testers to use their expertise and intuition to explore the system's functionality and identify defects without needing detailed specifications. Exploratory testing is flexible and can quickly adapt to changes and gaps in the requirements.
Which two of the following statements describe the advantages provided by good traceability between the test basis and test work products?
I . Analyzing the impact of changes.
ii . A measure of code quality.
iii . Accurate test estimation.
iv . Making testing auditable.
Select the correct answer:
Answer : B
Good traceability between the test basis and test work products provides several advantages: i. Analyzing the impact of changes: Traceability allows for easy identification of which parts of the test work products will be affected by changes in the requirements or design, facilitating impact analysis. iv . Making testing auditable: Traceability ensures that there is a clear connection between the requirements and the test cases, which makes the testing process auditable and provides evidence that all requirements have been tested.
Select the roles required in a formal review:
Answer : A
In a formal review, the roles involved typically include the author, management, facilitator (also known as moderator), review leader, reviewers, and scribe. Each role has specific responsibilities to ensure the effectiveness and efficiency of the review process:
The author creates and refines the work product being reviewed.
Management allocates resources and supports the review process.
The facilitator manages the review meeting, ensuring it proceeds smoothly.
The review leader plans the review and ensures it meets its objectives.
Reviewers examine the work product to identify defects.
The scribe records issues raised during the review meeting.
You are performing the role of tester on an Agile project. Which of the following tasks would be your responsibility?
i. Understanding, implementing, and updating the test strategy.
II . Ensuring the proper use of testing tools.
Hi. Coaching other team members in the relevant aspects of testing.
iv . Actively collaborating with developers and business stakeholders to clarify requirements, especially in terms of testability, consistency, and completeness.
v. Participating proactively in team retrospective meeting, suggesting and implementing improvements.
Select the correct answer:
Answer : A
In an Agile project, a tester's responsibilities include understanding, implementing, and updating the test strategy (i), actively collaborating with developers and business stakeholders to clarify requirements, especially in terms of testability, consistency, and completeness (iv), and participating proactively in team retrospective meetings, suggesting and implementing improvements (v). These activities ensure that testing is integrated into the development process, promoting continuous feedback and improvement. The ISTQB CTFL syllabus underlines the collaborative nature of Agile testing and the tester's role in contributing to the team's overall quality goals.
Consider the following examples of risks identified in different software development projects
[1]. It may not be possible to generate the expected workloads to run performance tests, due to the poor hardware equipment of the machines (load injectors) that should generate these workloads.
[ii]. A user's session on a web application is not invalidated after a certain period of inactivity (configured by the system administrator) of the user,
[iii]. The test team will not have an adequate requirements specification (since many requirements will still be missing) by the time test design and analysis activities should begin according to the test plan.
[IV]. Following a failure, the system is unable to continue to maintain its pre-failure operation and some data becomes corrupted.
Which of the following statements is TRUE?
Answer : A
In software testing, risks are categorized into product risks and project risks. Product risks are associated with the potential of a product to fail in meeting its quality criteria. Project risks are related to potential issues that could affect the project's ability to deliver a product.
[i] is a project risk because it concerns the availability and adequacy of hardware resources for performance testing.
[ii] is a product risk because it pertains to a security and functionality issue within the web application.
[iii] is a project risk because it involves the availability of necessary requirements documentation for the testing process.
[iv] is a product risk because it relates to the system's functionality and data integrity after a failure.
Thus, statement A correctly classifies [ii] and [iv] as product risks and [i] and [iii] as project risks.
Which of the following statements about the testing quadrants is TRUE?
Answer : B
The correct statement is B. According to the ISTQB CTFL syllabus, the testing quadrants help to categorize tests based on their purpose and whether they are technology-facing or business-facing, and whether they support the team or critique the product. Quadrant Q2 includes tests that are business-facing and support the team, such as automated acceptance tests produced during Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD) .
Quadrant Q3 includes business-facing tests that critique the product, such as exploratory testing, usability testing, and user acceptance testing. These tests are typically manual and focus on evaluating the product from a user perspective, rather than being part of a continuous integration process.
Quadrant Q4 includes technology-facing tests that critique the product, such as performance tests, security tests, and other non-functional tests, which can be automated but are not related to unit tests produced during TDD .