Integration Across Test Levels CT-TAS Practice Questions (Page 5)

Questions 21–25

1. 21expert · hard

   A large organization has separate teams for component, integration, and system testing. Each team has its own automation framework and test data. They are merging into a single DevOps team and want to integrate their automation efforts. The system tests are slow and flaky, and the integration tests depend on the component tests being stable. What is the most effective first step?

   • ACreate a new team to handle all test automation and disband the existing teams.
   • BMerge all test scripts into a single repository and run them in one pipeline.
   • CFocus on stabilizing the system tests first before integrating the other levels.
   • DEstablish a common test automation framework and standardize test data management across all teams.
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A team has a comprehensive set of API test scripts used for system testing. They want to reuse these for integration testing, but the integration tests need to run with mocked external services, while the system tests use real services. The team also has a tight release schedule. What is the best approach?

   • ACreate a separate set of integration test scripts that use mocks, and keep the system test scripts unchanged.
   • BRun the system test scripts in the integration environment with real services, but this may cause instability.
   • CSkip integration testing and rely on system testing to cover the integration points.
   • DRefactor the test scripts to support both mocked and real services through configuration, and run integration tests with mocks in the CI pipeline.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A test manager wants to see a single report that shows the status of automated tests across component, integration, and system levels, including which requirements are covered. What is the most effective way to achieve this?

   • AStore all results in a shared spreadsheet and update it after each test run.
   • BUse a test management tool that aggregates results from all levels and links them to requirements.
   • CAsk each team to send their results in separate emails and compile them manually.
   • DCreate a dashboard that only shows system-level results, since they cover the most.
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   An integration test team is about to start testing a new feature. They need to know which component tests have already been executed and their results to avoid redundant testing. What should the component test team provide?

   • AA test execution report with pass/fail status and coverage information.
   • BA list of all test cases that could be written for the component.
   • CA summary of defects found in the component.
   • DThe source code of the component tests.
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   A company is developing a new application and wants to automate tests at the component and integration levels. They have a limited budget and need to choose tools. What is the most important consideration?

   • AChoose tools that are easy to use, even if they lack integration capabilities.
   • BChoose tools that can support both component and integration testing to avoid multiple tool licenses.
   • CChoose the cheapest tools available, even if they have limited features.
   • DChoose tools that are popular in the industry, regardless of fit.
   Reveal Solution Discussion Select an answer first