iSQI Certified Tester Advanced Level Agile Technical Tester CTAL-ATT Exam Practice Test

Page: 1 / 14
Total 98 questions
Question 1

Using your knowledge of requirements engineering, which of the following activities would assist the team the most in determining which stories they should commit to in the first sprint?



Answer : B

Understanding the Objective:

The team needs to prioritize and select user stories for the first sprint.

A tool or technique that aligns stories with user value and development goals is essential.

Why User Story Mapping?

Definition: User story mapping visually organizes user stories according to workflows and business value.

Purpose: It helps teams:

Break down epics into smaller stories.

Prioritize stories based on importance and dependencies.

Focus on delivering incremental value in each sprint.

Eliminating Other Options:

A . Create Personas: Personas provide insights into target users but do not directly aid in sprint planning or story prioritization.

C . Consult with a Usability Expert: This addresses specific design concerns, which are not relevant for sprint planning.

D . Create UML Artifacts: Diagrams like state transitions are more relevant for system design and architecture, not backlog refinement or sprint commitment.


Aligned with ISTQB Advanced Agile Technical Tester syllabus, which emphasizes the use of user story mapping for prioritizing and planning work in Agile projects.

Question 2

You are working on a project to develop an application that allows users to collaborate via bespoke, online whiteboards. The first release, delivering core functionality, highlighted misunderstandings of the user stories between testers, developers and the product owner during sprint development Since that release, the developers have agreed to implement a TDD approach for future software development.

Creation of the product backlog for the second release is underway and you have recommended to the project stakeholders that an atdd approach be adopted for the backlog's user stories. What would be a GOOD REASON for making this recommendation?

SELECT ONE OPTION



Answer : D

Acceptance Test-Driven Development (ATDD) is a collaborative approach that involves customers, developers, and testers to define acceptance criteria before development begins. This practice helps ensure that all stakeholders have a shared understanding of the requirements and can prevent misunderstandings like those experienced in the first release.By using examples in ATDD, the team can clarify what the software should do, which aligns with the user stories and supports the Test-Driven Development (TDD) process12.

Reference= The ISTQB Advanced Level Agile Technical Tester documents and resources from Software Testing Help discuss the benefits of ATDD in aligning team members and stakeholders on the expected outcomes of user stories, which is particularly useful when there have been previous misunderstandings34.


Question 3

Which requirements engineering technique would BEST identify how different groups of users may interact with a system, helping to identify gaps and inconsistencies in a user story-'

SELECT ONE OPTION



Answer : D

Story Mapping is a requirements engineering technique that provides a visual representation of the user journey within the system. It helps in identifying how different user groups interact with the system, thereby uncovering gaps and inconsistencies in user stories. This technique allows teams to prioritize and plan releases based on the user's experience and needs.

Reference= The ISTQB Advanced Level Agile Technical Tester syllabus and training materials discuss the use of various requirements engineering techniques, including Story Mapping, to better understand and define user interactions with the system12.


Question 4

You have been working as a tester in an Agile team You have found that the user stories are being defined by the team but it is still unclear what will be a successful outcome Even after story elaboration you are still unclear as to what a story should do As a result, you're not really sure what to test or to know when you'll be done with testing This problem is becoming worse as completed stories are showcased but the product owner is unhappy with the results

You've looked into the matter further and the comments from the product owner indicate that features are missing from the stories. The story is functioning correctly within the limited definition of the story but the product owner is expecting more functionality, such as error handling that isn't being defined in the story

What technique should you implement that would help to further define the product owner's expectations and alleviate the issues that are arising during the show cases?



Answer : C

Acceptance Test-Driven Development (ATDD) involves the whole team collaboratively discussing acceptance criteria, with examples, and then distilling them into a set of concrete acceptance tests before development begins. It's a way to get clear on what to build, and it's done in a way that allows the team to know when a story is complete. ATDD helps to make sure that all the stakeholders have a common understanding of what is being built and what the success criteria are.

Reference= The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of defining testable requirements within an Agile team and creating and implementing various Agile test approaches using appropriate techniques1.It also supports the contribution to test automation activities in an Agile project2, which aligns with the principles of ATDD.


Question 5

Which option below describes the BEST approach for testing a Medium risk mission- or safety-critical system?

SELECT ONE OPTION



Answer : B

For a Medium risk mission- or safety-critical system, a combination of automated, exploratory, and manual black-box tests is recommended. Automated tests ensure consistent and efficient coverage of known scenarios, while exploratory tests allow testers to investigate and discover unknown issues.Manual black-box tests are important for verifying the system from an end-user perspective without knowledge of the internal workings, which is crucial for safety-critical systems.Reference= The ISTQB Advanced Level Agile Technical Tester syllabus and materials emphasize the importance of a comprehensive testing approach that includes various techniques suitable for the system's risk level and criticality123


Question 6

Which of the following elicitation techniques is BEST usedwhen questioning a large number of stakeholders specifically to obtain information for non-functional acceptance criteria?

SELECT ONE OPTION



Answer : B

Quantitative questionnaires are best suited for eliciting non-functional requirements from a large number of stakeholders. This is because they allow for the collection of measurable, statistical data that can be analyzed to understand the stakeholders' needs regarding system qualities like performance, usability, and reliability.These questionnaires can be designed to include specific questions about non-functional aspects, which can then be quantitatively assessed to inform the acceptance criteria1.


Question 7

BDD and ATDD are most commonly used with which test approach?



Answer : C

Why BDD and ATDD Align with Process-Compliant Testing:

Proactive Testing:

BDD and ATDD emphasize collaboration between stakeholders (business analysts, developers, testers, and product owners) to define the requirements before coding begins.

This proactive approach ensures that tests are integrated into the development process, reducing misunderstandings and errors upfront.

Structured Iterative Processes:

Both techniques fit seamlessly into Agile methodologies like Scrum and Kanban, where clear, iterative processes guide development and testing.

During sprint planning or backlog refinement, BDD/ATDD practices are used to refine user stories into concrete, executable test cases.

Specification by Example:

BDD and ATDD rely on defining concrete examples (acceptance criteria) collaboratively, which are directly converted into automated tests. This structured method underscores their alignment with process-oriented strategies.

Integration into CI/CD Pipelines:

The automated tests derived from BDD/ATDD become part of the CI/CD process, continuously validating that the system meets specified requirements. This exemplifies a process-compliant and proactive approach to quality assurance.

'Shift-Left' Testing Philosophy:

These practices embody the 'shift-left' approach, moving testing activities earlier in the lifecycle. This is characteristic of well-defined, process-driven methodologies.

Differentiating from Reactive:

While BDD and ATDD adapt to evolving requirements (a hallmark of Agile), they do so in a structured, iterative way, not as a reaction to unforeseen changes or issues.

Reactive testing typically addresses late-stage feedback or emergent problems, which contrasts with the upfront planning and collaboration integral to BDD/ATDD.


Page:    1 / 14   
Total 98 questions