CTAL-ATT Agile Technical Tester Practice Questions
Prepare for CTAL-ATT with more than an answer.
- Level
- Advanced Level
Domains covered on the exam 4
- Requirements Engineering
- Testing in Agile
- Test Automation
- Deployment and Delivery
- 1
A team's CI server runs a series of checks on every code commit. The process is illustrated below. At which stage would static code analysis tools typically be executed?
flowchart TD A[Commit Code] --> B{Build & Compile} B --> C[Run Unit Tests] C --> D[Package Artifact] D --> E[Deploy to Test Env] E --> F[Run Integration Tests]Show answer details
Correct answer: A
Static code analysis does not require the code to be executed. It analyzes the source code itself for potential issues like coding standard violations, security vulnerabilities, and complex logic. Therefore, it is most efficiently run early in the CI pipeline, typically during or right after the code is successfully compiled (Stage B) and before any dynamic tests (like unit or integration tests) are run. This provides the fastest possible feedback on code quality issues.
- 2
Which of the following activities is NOT considered part of the 'Refactor' step in the TDD cycle?
Show answer details
Correct answer: C
The core rule of refactoring is to improve the internal structure of the code without changing its external behavior. Adding new functionality fundamentally changes the external behavior and is not part of the refactoring step. New functionality should be introduced by starting a new Red-Green-Refactor cycle.
- 3
An Agile team is automating tests for a user story. They have identified three distinct test automation approaches. Which approaches are recognized as valid test automation techniques in the CTAL-ATT syllabus? (Select THREE).
Show answer details
Correct answer: C, D, E
BDD-style testing, using frameworks like Cucumber with Gherkin, is a form of keyword-driven testing that creates executable specifications in a natural language format.
Data-Driven Testing is a key technique where test logic is separated from test data, allowing for easy scalability and maintenance.
Keyword-Driven Testing uses keywords to represent actions, improving readability and allowing non-programmers to contribute to test creation.
- 4
A team is struggling to decide on the appropriate level of test automation for their project to keep up with a planned twice-daily deployment schedule. What is the primary factor they should consider when balancing the benefits and limitations of increasing test automation?
Show answer details
Correct answer: D
The core challenge is balancing speed and quality. The goal is not just to automate, but to automate the right tests. The primary factor is whether the chosen automated suite can execute quickly enough to not block the frequent deployment schedule while still providing confidence that the most critical business risks are covered. Simply automating everything may create a suite that is too slow, while automating too little may allow critical regressions to pass through.
- 5
What is the primary purpose of using Story Mapping during backlog refinement sessions?
Show answer details
Correct answer: C
Story Mapping arranges user stories along two axes: the horizontal axis represents the user's chronological journey (the 'narrative flow'), and the vertical axis represents sophistication or priority. This visualization helps the team understand the big picture, see how features fit together, identify gaps, and prioritize the essential stories needed for a first release or MVP.
- 6
An Agile team is developing a microservices-based application. The team responsible for the 'Order' service needs to perform integration testing, but the 'Payment' service, which it depends on, is unstable and frequently unavailable in the shared development environment. This is causing significant delays and blocking the CI pipeline. Which approach provides the most effective and immediate solution to unblock the 'Order' service team and stabilize their CI pipeline?
Show answer details
Correct answer: A
Service virtualization is the ideal solution for this common microservices challenge. It allows the 'Order' service team to create a virtual service that mimics the behavior, data, and performance of the real 'Payment' service. This decouples the teams, unblocks the CI pipeline, and allows for predictable, repeatable integration testing without relying on the availability of the actual dependent service. Waiting causes delays, skipping tests introduces risk, and using simple stubs may not be sufficient for stateful integration scenarios.
- 7
A mature Agile team follows Test-Driven Development (TDD) principles rigorously. A developer is tasked with implementing a new feature. According to the Red-Green-Refactor cycle of TDD, what is the very first action the developer must take?
Show answer details
Correct answer: D
The TDD cycle is strictly defined as Red-Green-Refactor. The 'Red' phase comes first, which involves writing a unit test for a piece of functionality that does not yet exist. This test must fail (turn red) when run, proving that the test works and the functionality is not yet implemented. Only after this failing test is created does the developer move to the 'Green' phase of writing the minimum amount of production code to make the test pass.
- 8
During a backlog refinement session for a financial application, the team is analyzing the following user story: "As a customer, I want to view my transaction history so that I can track my spending." Which TWO of the following are the most effective, testable acceptance criteria for this story? (Select TWO).
Show answer details
Correct answer: A, C
This is a specific, verifiable, and testable criterion that defines the required data elements for the feature.
This is a specific, verifiable, and testable criterion that defines a key behavior of the feature.
- 9
True or False: In a Keyword-Driven Testing framework, keywords should primarily be implemented to represent low-level UI interactions like 'clickButton' or 'setTextField', as this provides the most granular control for test automation.
Show answer details
Correct answer: B
This is false. A major benefit of Keyword-Driven Testing is abstraction. Keywords should represent business-level actions (e.g., 'loginWithValidCredentials', 'addProductToCart') rather than low-level UI interactions. This makes tests more readable, maintainable, and resilient to minor UI changes. The low-level interactions are encapsulated within the implementation of the business-level keywords.
- 10
Case Study
A retail company, 'GlobalMart', is transitioning to an Agile model for its e-commerce platform. The development team is organized into two-week sprints. They have a CI/CD pipeline that automatically builds and deploys the application to a staging environment after every commit to the main branch. The pipeline currently runs a suite of unit tests, which completes in under 5 minutes.
The QA team has built a separate, extensive suite of automated end-to-end UI tests using Selenium. This suite takes over 3 hours to run. The leadership team is pushing for faster feedback and wants to integrate these UI tests directly into the main CI pipeline to run on every commit. The technical testers on the team have raised concerns about this approach, arguing it will drastically slow down the feedback loop for developers.
Problem
The current setup provides slow feedback on system-level regressions, but integrating the full UI suite into the primary CI pipeline would violate the principle of fast feedback. The team needs a strategy that balances the need for comprehensive regression testing with the need for a rapid CI cycle for developers.
Question
Given the situation at GlobalMart, which strategy represents the most effective and balanced approach to integrating automated testing into their CI/CD process?
Show answer details
Correct answer: C
This strategy provides the best balance. The 'commit' pipeline maintains the fast feedback loop essential for developers, running quick checks like unit and API tests. The 'nightly' pipeline ensures that the comprehensive but slow UI regression suite is still run regularly, providing broader coverage without blocking the primary development workflow. This tiered approach is a standard best practice for managing tests with different execution times in a CI/CD context.
