CTFL 5.3.3: Exemplify how to communicate the status of testing
K2Syllabus section 5.3.3
3 original PrepBench practice questions for learning objective 5.3.3 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.
Practice questions
Question 1
A test manager sends the same detailed defect-by-defect report to the development team and to the executive sponsor. The sponsor soon stops reading it. Which principle of communicating test status explains what went wrong?
- The same dashboard should replace the report for both audiences because dashboards can show status
- A verbal update should replace the report for the sponsor because verbal communication is available
- Different stakeholders are interested in different information, so communication should be tailored
- The report should become more formal because greater formality can suit distributed teams
Show answer
- The same dashboard should replace the report for both audiences because dashboards can show statusChanging both audiences to the same dashboard still ignores their different information needs.
- A verbal update should replace the report for the sponsor because verbal communication is availableChanging only the channel does not tailor the information to what the sponsor needs.
- Correct answer: Different stakeholders are interested in different information, so communication should be tailoredStakeholders differ in what they need, so the communication is tailored.
- The report should become more formal because greater formality can suit distributed teamsGreater formality can suit distributed teams, but it does not correct the untailored information.
Typically, different stakeholders are interested in different types of information, so communication should be tailored accordingly. The options for communicating test status include verbal communication, dashboards, electronic channels, online documentation and formal test reports, and one or more of them can be used — but the content and the channel have to suit the audience.
Syllabus section 5.3.3
Question 2
A team wants everyone in the organization to be able to see current test progress at any moment, without having to ask anyone for it. Which option for communicating test status fits that need best?
- Verbal communication with team members and other stakeholders
- Electronic communication channels, for example email and chat
- Dashboards, for example CI/CD dashboards, task boards and burn-down charts
- A formal test completion report issued at the end of the test activity
Show answer
- Verbal communication with team members and other stakeholdersVerbal updates require someone to be present and to ask.
- Electronic communication channels, for example email and chatEmail and chat push information at a moment chosen by the sender.
- Correct answer: Dashboards, for example CI/CD dashboards, task boards and burn-down chartsA dashboard shows the current state continuously to anyone who looks.
- A formal test completion report issued at the end of the test activityA completion report comes once, at the end of the activity.
The syllabus lists verbal communication, dashboards such as CI/CD dashboards, task boards and burn-down charts, electronic communication channels such as email and chat, online documentation, and formal test reports. All are legitimate options, but a dashboard is the one that presents current status continuously and without anyone having to be asked.
Syllabus section 5.3.3
Question 3
A project's teams sit in three countries with little overlap in working hours, and its informal verbal status updates keep being missed. What is appropriate for a project in that situation?
- More formal communication, which may be more appropriate for distributed teams
- Reducing the frequency of reporting, so that fewer updates can be missed
- Appointing an independent test team to take over the status reporting
- Communicating status only through the defect management tool
Show answer
- Correct answer: More formal communication, which may be more appropriate for distributed teamsDistributed teams and time differences are exactly this circumstance.
- Reducing the frequency of reporting, so that fewer updates can be missedReporting less often does not address updates being missed.
- Appointing an independent test team to take over the status reportingIndependence of testing is a separate matter and does not solve distribution.
- Communicating status only through the defect management toolA defect tool records defects; it does not communicate overall test status.
More formal communication may be more appropriate for distributed teams where direct face-to-face communication is not always possible due to geographical distance or time differences. Typically, different stakeholders are interested in different types of information, so communication should be tailored accordingly.
Syllabus section 5.3.3
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.