Question 1: What is the role of testing in Agile development?

• To test only at the end of the development cycle.
• To test individual components after each sprint.
• To ensure the product meets the acceptance criteria and quality standards through continuous testing. (Correct answer)
• To rely solely on automated testing tools.

Correct answer: To ensure the product meets the acceptance criteria and quality standards through continuous testing.

In Agile, testing is an integrated and continuous activity throughout the development lifecycle, not just an end-of-project phase. This continuous approach, including unit, integration, and system testing, helps identify defects early, ensures quality, and verifies that the product consistently meets defined acceptance criteria and user expectations. It supports rapid feedback and iterative development.

Question 2: What is the purpose of 'Test-Driven Development' (TDD) in Agile?

• To automate testing after the code is written.
• To write tests after the functionality is implemented.
• To write tests before the code to ensure functionality is met. (Correct answer)
• To focus only on testing the code's performance.

Correct answer: To write tests before the code to ensure functionality is met.

Test-Driven Development (TDD) is a development practice where developers write automated tests *before* writing the actual code. The process involves writing a failing test, then writing just enough code to make the test pass, and finally refactoring the code. This approach ensures that functionality is explicitly defined and verified, leading to higher quality code and better design.

Question 3: What is 'continuous integration' (CI) in Agile?

• Developing code in isolation and integrating at the end.
• Integrating code into a shared repository continuously, with automated tests running after each integration. (Correct answer)
• Delaying integration until all features are complete.
• Only testing code in a staging environment.

Correct answer: Integrating code into a shared repository continuously, with automated tests running after each integration.

Continuous Integration (CI) is a development practice where developers frequently merge their code changes into a central repository. Each integration is verified by an automated build and test process, allowing teams to detect and address integration issues early. This practice reduces integration problems and ensures a consistently working codebase.

Question 4: What is the benefit of using automated testing in Agile?

• To eliminate the need for manual testing.
• To speed up testing, enabling frequent testing throughout the development process. (Correct answer)
• To replace all manual testing with code-based testing.
• To focus only on unit testing of individual components.

Correct answer: To speed up testing, enabling frequent testing throughout the development process.

Automated testing significantly reduces the time and effort required for repetitive test execution. This speed allows Agile teams to run tests frequently, often after every code change or integration, providing rapid feedback on the health of the application. It enables continuous testing, which is crucial for maintaining quality in fast-paced Agile environments.

Question 5: What does 'Acceptance Test-Driven Development' (ATDD) focus on?

• To write tests based on user stories and ensure they meet the specified requirements.
• To perform unit testing after the code is completed.
• To focus on the performance testing of the application.
• To automate only the testing of the back-end services.

Acceptance Test-Driven Development (ATDD) is a collaborative approach where team members (developers, testers, and business stakeholders) define acceptance tests *before* development begins. These tests are derived from user stories and requirements, serving as concrete examples of desired behavior. ATDD ensures a shared understanding of "done" and verifies that the developed features meet the business's specified needs.

Question 6: What does the term 'refactoring' mean in Agile testing?

• Changing the overall design of the application.
• Refining the code to improve its performance or maintainability without changing its behavior. (Correct answer)
• Replacing old code with new features.
• Writing code that is easier to understand for new developers.

Correct answer: Refining the code to improve its performance or maintainability without changing its behavior.

Refactoring is the process of restructuring existing computer code without changing its external behavior. The goal is to improve non-functional attributes of the software, such as readability, maintainability, and internal structure, making it easier to understand and modify in the future. This practice helps keep the codebase clean and adaptable in Agile development.

Question 7: What is 'exploratory testing' in Agile?

• Performing scripted tests based on predefined criteria.
• Writing test scripts before starting the test execution.
• Simultaneously learning about the application and testing it, often in an unscripted manner. (Correct answer)
• Testing only the most critical paths of the application.

Correct answer: Simultaneously learning about the application and testing it, often in an unscripted manner.

Exploratory testing is an unscripted, hands-on approach where the tester simultaneously designs, executes, and learns about the software. Instead of following predefined test cases, testers use their knowledge and intuition to explore the application, discover defects, and identify areas for further investigation. This method is highly effective for finding issues that might be missed by scripted tests.

Question 8: Why is regression testing important in Agile?

• To test new features in isolation.
• To ensure that existing functionality is not broken after changes. (Correct answer)
• To verify that the product meets customer acceptance criteria.
• To focus only on functional testing.

Correct answer: To ensure that existing functionality is not broken after changes.

Regression testing is crucial in Agile to verify that new code changes, bug fixes, or configuration updates have not adversely affected existing, previously working functionality. By repeatedly running tests on stable parts of the application, teams can quickly detect unintended side effects. This ensures the product remains stable and reliable with each new iteration.

Question 9: What does 'smoke testing' mean in Agile?

• Testing the application for high performance and load handling.
• Initial testing to check if the basic functionalities work after a new build.
• Testing the security of the application.
• In-depth functional testing of new features.

Smoke testing is a quick, high-level test performed on a new software build to determine if the most critical functions are working correctly. It's like a "health check" to ensure the build is stable enough for more extensive testing. If the smoke test fails, the build is typically rejected, saving time and resources from further testing on a broken version.