Test Levels CT-AT Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A team is adapting their traditional test levels to Agile. They have a large legacy system that is not easily testable in small increments. What is the best approach to adapt acceptance testing to Agile?

   • ADefine acceptance criteria for each user story and automate acceptance tests as part of the definition of done.
   • BPerform acceptance testing only at the end of the project to ensure the entire system meets requirements.
   • CUse only exploratory testing for acceptance, as it is faster.
   • DSkip acceptance testing for stories that are not critical to the business.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A team developing a mobile banking app uses a two-week sprint. The product owner has just accepted a user story that adds a new transaction categorization feature. The developers have completed unit tests for the new code. What is the most appropriate next test level to perform before the feature is integrated into the main branch?

   • AAcceptance testing with the product owner to confirm the feature meets business expectations.
   • BSystem testing to validate the entire application against the requirements of the new feature.
   • CRegression testing of the entire application to ensure no existing functionality is broken.
   • DComponent integration testing to verify the new module interacts correctly with existing transaction modules.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   An Agile team is developing a new feature that will be deployed to production at the end of the sprint. They have completed unit and integration testing. What is the most important test level to perform before deployment to ensure the feature meets business needs?

   • AAcceptance testing to validate that the feature satisfies the acceptance criteria and business requirements.
   • BComponent testing to verify each unit of code works correctly.
   • CPerformance testing to ensure the system meets non-functional requirements.
   • DIntegration testing to verify that components work together.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   An Agile team is planning testing for a new e-commerce checkout feature. They want to ensure that the feature works correctly from a technical perspective and also meets business expectations. According to the Agile Testing Quadrants, which combination of testing activities should the team include?

   • AExploratory testing (Q2) and security testing (Q4) only, covering business and non-functional aspects.
   • BAutomated unit and integration tests (Q1) plus exploratory testing (Q2) to cover both technology and business-facing aspects.
   • CAutomated unit tests (Q1) and performance testing (Q4) only, focusing on technical quality.
   • DUser acceptance testing (Q2) and system testing (Q3) only, focusing on business and system behavior.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   An Agile team is working on a large system with multiple teams contributing to the same codebase. They have a continuous integration pipeline that runs unit tests on every commit. However, integration defects are often found late. What is the best way to improve the integration of test levels to catch these defects earlier?

   • AUse only system testing in the CI pipeline to catch integration issues.
   • BIncrease the number of unit tests to cover integration scenarios.
   • CPerform integration testing only at the end of the sprint when all features are complete.
   • DAdd integration tests to the CI pipeline that run after unit tests, using test doubles for components not yet developed.
   Reveal Solution Discussion Select an answer first