Agile Technical Tester Free Sample Questions

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.

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.

This is a specific, verifiable, and testable criterion that defines a key behavior of the feature.

This is a specific, verifiable, and testable criterion that defines the required data elements for the feature.

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.

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.

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.