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

Questions 11–15

1. 11foundation · easy

   Which artifact is most important to pass from component-level testing to integration-level testing?

   • AThe final test report for the entire system
   • BThe list of defects found during component testing
   • CThe test data used for component testing
   • DThe component test scripts and stubs used to simulate dependencies
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A team automates component tests for a microservices-based system. They want to reuse the same test scripts for integration testing, but the integration environment has different authentication mechanisms and data formats. What is the most appropriate approach?

   • ADuplicate the component test scripts and modify the copies for the integration environment to avoid impacting component testing.
   • BRun the component test scripts as-is in the integration environment and accept the failures as integration issues.
   • CRefactor the component test scripts to use abstraction layers for authentication and data handling, then reuse them in integration tests.
   • DDiscard the component test scripts and write new integration tests from scratch to ensure proper coverage.
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   A team has a legacy system with no existing test automation. They are planning to introduce automation at the component, integration, and system levels. The system is critical and changes frequently. They have a limited budget for tools and training. What is the most important factor in their automation strategy?

   • AUse open-source tools exclusively to save costs, even if they lack features.
   • BPrioritize test levels based on risk and business impact, and start with a pilot to validate the approach.
   • CAutomate all test levels at once to get comprehensive coverage quickly.
   • DFocus only on system-level tests because they cover the most.
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A company has a complex system with multiple microservices. They have automated tests at the component, integration, and system levels. The system-level tests take a long time and are often flaky. The team wants to reduce the feedback time for developers while maintaining confidence in the system. What is the best strategy?

   • ARun only system tests on every commit and skip the lower levels.
   • BRun all test levels only on a weekly basis to save resources.
   • CRun all test levels on every commit to get maximum feedback.
   • DRun component and integration tests on every commit, and run a subset of system tests on a nightly basis, with a full system test suite before releases.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A team has a large set of UI test scripts for system testing. They want to reuse them for acceptance testing, but the acceptance tests require different test data and user roles. What is the most efficient way to handle this?

   • ARefactor the scripts to separate test data from test logic and use data-driven testing.
   • BUse the system test scripts but manually change the data and roles before each acceptance run.
   • CRun the system test scripts in the acceptance environment without changes.
   • DCreate a separate set of acceptance test scripts by copying and modifying the system test scripts.
   Reveal Solution Discussion Select an answer first