CTAL-TTA_001 · Question #39
Select TWO solutions how the team could achieve significant benefits in the use of this tool within the next 6 months? (3 credits, for 1 out of 2 correct 1 credit) 3 credits [K4]
The correct answer is B. Change the development process C. Select and implement a test management tool to complement the test suite. B (Change the development process) and C (Select a test management tool) are correct because they address the systemic factors that unlock the full value of an automation tool already in place. Without integrating automation into the development workflow (CI pipelines…
Question
Select TWO solutions how the team could achieve significant benefits in the use of this tool within the next 6 months? (3 credits, for 1 out of 2 correct 1 credit) 3 credits [K4]
Options
- AIntroduce data-driven or keyword driven scripting techniques
- BChange the development process
- CSelect and implement a test management tool to complement the test suite
- DIdentify critical parts of the system and concentrate on automating some of those tests for that
- EGet business testers involved in the automation process
How the community answered
(38 responses)- A5% (2)
- B66% (25)
- D11% (4)
- E18% (7)
Explanation
B (Change the development process) and C (Select a test management tool) are correct because they address the systemic factors that unlock the full value of an automation tool already in place. Without integrating automation into the development workflow (CI pipelines, definition-of-done, etc.), the tool sits underused regardless of its quality; pairing it with a test management tool provides visibility into results, coverage, and progress - producing measurable, demonstrable value quickly.
A (data-driven/keyword-driven scripting) is a valid long-term maturity improvement but requires significant redesign of existing scripts and team training, making it unlikely to yield significant benefits within 6 months. D (identifying critical areas to automate) is a good initial strategy but implies starting the automation effort over, rather than maximising an existing tool; and if the team already has a test suite, the problem is exploitation, not selection. E (involving business testers) sounds collaborative but automated scripting demands technical skills that business testers typically lack, so onboarding them would consume the 6-month window rather than deliver benefits within it.
Memory tip: Think of B and C as the "infrastructure" answers - process (how work flows) and tooling ecosystem (what supports the tool). Automation tools underdeliver when the process doesn't embrace them and when there's no system to manage what they produce. The other options are either "later-stage maturity" (A) or "pre-automation setup" (D, E) activities.
Topics
Community Discussion
No community discussion yet for this question.