Formal Testing and Holistic Testing CTAL-AT Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   In holistic testing, why is it important to consider the business context?

   • ATo ensure that all test cases are documented in a formal test plan.
   • BTo reduce the number of test cases needed for the project.
   • CTo ensure the system aligns with business goals and delivers value to stakeholders.
   • DTo eliminate the need for technical testing activities.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which of the following best describes holistic testing?

   • ATesting that is limited to the user interface to ensure a good user experience.
   • BTesting that focuses only on the functional requirements of the system.
   • CTesting that is performed without any documentation to allow for maximum flexibility.
   • DTesting that considers the whole system, including non-functional aspects, user experience, and business context.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   How does the scope of formal testing typically differ from that of holistic testing?

   • AFormal testing is performed only at the system level, while holistic testing is performed only at the unit level.
   • BFormal testing covers only functional requirements, while holistic testing covers only non-functional requirements.
   • CFormal testing is manual, while holistic testing is automated.
   • DFormal testing focuses on verifying specified requirements, while holistic testing considers broader system aspects and context.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A team is working on a project that requires documented evidence of testing for external auditors. They are using Scrum with two-week sprints. Which approach best applies formal testing in this Agile context?

   • AMaintain a test case repository with detailed test cases and record results in a test management tool after each sprint.
   • BCreate a comprehensive test plan at the start of the project and do not update it during sprints.
   • CRely on the product owner's acceptance criteria as the only documentation of testing.
   • DUse exploratory testing and document the findings in a shared document after each sprint.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   An Agile team is struggling to balance formal testing (documented test cases, regression suites) with holistic testing (exploratory, UX, performance). They have limited time in each sprint and are missing defects that only exploratory testing finds, while also facing audit requirements for documented evidence. Which strategy best balances the two approaches?

   • AEliminate formal test cases entirely and rely solely on exploratory testing to save time.
   • BUse formal test cases for critical functionality and regulatory requirements, and allocate time for exploratory testing sessions for the rest.
   • CCreate formal test cases for every feature, including exploratory testing only if time remains at the end of the sprint.
   • DPerform exploratory testing first, then write formal test cases based on the defects found.
   Reveal Solution Discussion Select an answer first