ISTQB Agile Technical Tester - Advanced Level

Explore how epics organize large requirements and how user stories detail functionality, framed as a user I want, to achieve a benefit, with acceptance criteria as rule- or scenario-oriented goals.

Practice creating epics and user stories in Jira within an onboarding epic, define acceptance criteria with given/when/then, and map backlog with traceability in a scrum workflow.

Learn how requirements engineering techniques—from gathering to management—guide agile teams to polish user stories, add context, and identify gaps through continuous, collaborative feedback loops by all agile members.

Analyze and refine user stories and epics with requirements engineering techniques: storyboards, story mapping, personas, diagrams, and use cases, equipping testers to clarify and improve agile requirements.

Explore story mapping, a two-axis backlog visualization that ranks user stories by priority and implementation effort, guiding early releases and testing priorities.

Convert user stories into a story map, plan mvp releases, define acceptance criteria, and identify gaps to report to the product owner in an agile testing context.

Explore storyboards as a visual, sequential representation of the system that reveals user stories, themes, and gaps, guiding test approaches and acceptance criteria.

Learn how personas reveal gaps and inconsistencies in user stories by modeling fictional users with different motives, enabling better acceptance criteria and exploratory testing coverage.

Explore how diagrams support requirements and system understanding, covering behavior diagrams (use case, state machine) and structure diagrams (class, entity-relationship) to analyze data flow and gaps.

Learn how to model system interactions with use case diagrams and specifications, using extend and include, and analyze basic, alternative, and exception flows for comprehensive use case testing.

Explore the requirements engineering process in agile testing, including elicitation of user needs and constraints, documentation with user stories and acceptance criteria, negotiation and validation among stakeholders, and ongoing management.

Identify, document, negotiate, and manage requirements to shape acceptance criteria for user stories, including definition of ready, using elicitation techniques, clear documentation, stakeholder validation, and change management in agile projects.

Quantitative questionnaires gather numerical data using closed-ended questions to identify acceptance criteria and measure non-functional aspects; they enable large stakeholder input and simple data analysis for test scenario development.

Qualitative questionnaires use open-ended questions as a follow-up to quantitative data, not substitutes for quantitative data. They generate user stories and functional acceptance criteria, while quantitative methods cover non-functional criteria.

Learn how qualitative interviews use open-ended questions with stakeholders to uncover backgrounds, context, and motives, and how this data informs, follows questionnaires, and deepens acceptance criteria and user stories.

Explore techniques for eliciting requirements and improving thinking, including observation with stakeholders, six thinking hats for perspectives, and low fidelity prototyping to review acceptance criteria.

Apply the invest and smart techniques to craft independent, negotiable, valuable, estimable, small, and testable user stories, and use boundary value analysis and decision table testing to define acceptance criteria.

Explore agile testing techniques including TDD, BDD, and acceptance test driven development, plus experience-based testing, test charters, and code quality practices with static analysis and refactoring, via practical Java examples.

Explore test driven development and behavior driven development in an agile project, using user stories and BDD scenarios to introduce acceptance test driven development and improve product quality.

Master test driven development by writing a failing test first, coding to pass, and refactoring in iterative cycles; embrace shift-left, early testing, and a robust design.

Behavior driven development unites developers, testers, and business representatives to analyze user stories with a ubiquitous language and verify behaviors via automated given-when-then scenarios.

Identify acceptance criteria from user stories and convert them into atomic, semantic scenarios. Use given-when-then or rule-based formats, explore with testing, manage conditions, data, and mapping.

Explore how Zephyr Scale integrates with Cucumber to turn user stories and acceptance criteria into executable Gherkin scenarios, showing given-when-then steps, test cases, and code automation.

Explore behavior driven development (bdd) as a collaborative approach where developers, testers, and product owners craft executable scenarios from user stories using the given-when-then format to verify behaviors.

Explore acceptance test driven development (ATDD) as a business-facing counterpart to TDD and BDD, aligning user stories, acceptance tests, and testable examples to deliver customer-valued functionality.

Learn to blend automation, experience-based, and blackbox testing in agile projects, using risk-aware test charters derived from user stories and time-boxed exploratory sessions.

Explore aspects of code quality, focusing on refactoring test cases in agile projects, analyzing defects and technical debt through code reviews and static code analysis.

Explore test automation in agile projects, covering data-driven and keyword-driven testing, seven automation approaches and levels of automation, and challenges of test suite volume and maintenance.

Explore data driven testing, a test automation technique that separates test logic from data, using a single script with data in CSV or Excel to cover multiple input combinations.

Keyword driven testing defines a domain-specific vocabulary of keywords to write readable test procedures, enabling clearer communication, living documentation, and behavior driven development style across unit, API, and GUI testing.

Apply test automation as a strategy aligned with project objectives, using analytics, model-based, methodical, process-compliant, reactive, directed, and regression-averse approaches to improve efficiency and early defect discovery.

Explore automation in agile projects, including test and deployment automation with continuous deployment, and weigh benefits like faster delivery against challenges such as test suite growth and false positives.

Explore continuous integration and its testing impact in agile projects, balancing fast feedback with thorough verification through five solutions, and apply continuous testing, delivery, deployment, and service virtualization.

Describe continuous integration, continuous testing, and continuous delivery, emphasizing fast feedback, automated tests, risk-based prioritization, parallel test execution, and automatic production deployment.

Explore service virtualization in agile projects, creating virtual services that simulate behavior, data, and performance to enable earlier, realistic testing of APIs and dependent systems.