CTAL-ATT Sample Questions & Answers

Technical debt refers to the implied cost of rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer. Complex, hard-to-maintain code is a classic form of technical debt. While it might function correctly now, it will be more costly and difficult to modify or debug in the future.

The Given step in a Gherkin scenario is used to establish the preconditions and initial context. It sets up the state of the system before the action described in the When step is performed. For example, 'Given I am logged in as a premium user'.

Personas provide context about how, when, and where a user will interact with the system. For the persona 'Sarah', who uses the app during her commute, the tester can derive critical non-functional test scenarios. These include testing how the app behaves with intermittent or switching network connectivity (e.g., Wi-Fi to cellular), how it handles interruptions like phone calls, and its performance on a mobile device with other apps running. This context is invaluable for designing realistic and relevant tests.

This is a key benefit. Once the framework is built, new test variations can be added by non-technical team members, increasing collaboration and test coverage.

This separation is the core concept of data-driven testing. It means a single script can execute hundreds of tests, and data changes don't require code changes.

In Agile, rapid communication is key, especially for critical issues. The best practice is to immediately inform the key stakeholders (developer, PO) to ensure swift awareness and action. This verbal communication should be immediately followed by formal documentation in the defect tracking system to ensure the issue is officially recorded, prioritized, and not forgotten. Waiting for a scheduled meeting would introduce unnecessary delay and risk.

This is the key distinction. Both practices involve automating the build, test, and staging deployment phases. However, in Continuous Delivery, the final step of deploying to production is a manual, business-driven decision (a 'push-button' deployment). In Continuous Deployment, if the entire pipeline passes, the change is automatically deployed to production without any human intervention.

The 'I' in the FIRST mnemonic stands for Independent (or Isolated). This means that unit tests should not depend on each other. The order in which they are run should not matter, and one test's failure should not cause another to fail. This is crucial for accurately pinpointing the source of a defect.

Storyboards provide a visual representation of the system's functional flow, showing the sequence of steps a user takes to accomplish a goal. This visual narrative is extremely effective for identifying gaps, missing error handling, and alternative paths in the workflow, which are all excellent inputs for creating a comprehensive test charter for an exploratory session.

This is false. The primary goal of ATDD is to facilitate collaboration between business stakeholders, developers, and testers to create a shared understanding of the requirements before development begins. The acceptance tests, derived from these collaborative discussions, serve as executable specifications that drive development, rather than being an after-the-fact verification activity.

This is the most effective Agile solution. By adopting ATDD/BDD, the team shifts from a sequential to a collaborative model. Defining tests upfront creates a shared understanding and allows for smaller, vertical slices of functionality to be built and tested in parallel. The tester can work on test automation and environment setup while developers work on the first slice, enabling concurrent work and ensuring the story is fully tested and 'done' within the sprint.