CTFL 5.1.7: Summarize the testing quadrants and their relationships with test levels and test types
K2Syllabus section 5.1.7
4 original PrepBench practice questions for learning objective 5.1.7 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.
Practice questions
Question 1
Real end users work through the new claims screens without scripted steps and judge whether the screens are workable in their daily job. Into which testing quadrant does this test fall?
- Q1 — technology facing, supporting the team
- Q3 — business facing, critiquing the product
- Q4 — technology facing, critiquing the product
- Q2 — business facing, supporting the team
Show answer
- Q1 — technology facing, supporting the teamQ1 holds component and component integration tests, which are technology facing and automated.
- Correct answer: Q3 — business facing, critiquing the productUser-oriented, unscripted judgement of the product is business facing and critiques it.
- Q4 — technology facing, critiquing the productQ4 holds smoke tests and non-functional tests other than usability tests.
- Q2 — business facing, supporting the teamQ2 holds functional tests, examples and user story tests that check the acceptance criteria.
In the testing quadrants, tests can be business facing or technology facing, and they can support the team (guide the development) or critique the product (measure its behaviour against expectations). Quadrant Q3 is business facing and critiques the product: it contains exploratory testing, usability testing and user acceptance testing, which are user-oriented and often manual — exactly what these end users are doing.
Syllabus section 5.1.7
Question 2
Which tests belong to the quadrant that is business-facing and SUPPORTS the team?
- Functional tests of user stories and acceptance tests defined with the customer (e.g. ATDD)
- Performance tests and security tests run against the system
- Component tests and component integration tests of the code
- Exploratory testing and usability testing of the finished product
Show answer
- Correct answer: Functional tests of user stories and acceptance tests defined with the customer (e.g. ATDD)Functional user-story and acceptance tests (e.g. via ATDD) express business needs and guide development.
- Performance tests and security tests run against the systemPerformance and security tests are technology-facing tests that critique the product.
- Component tests and component integration tests of the codeComponent and integration tests are technology-facing tests that support development.
- Exploratory testing and usability testing of the finished productExploratory and usability tests critique the product rather than support development.
The business-facing, team-supporting quadrant contains tests that express what the business wants and guide development: functional user story tests, examples and acceptance tests (ATDD/BDD). Component tests are technology-facing/supporting; exploratory and usability tests critique the product.
Syllabus section 5.1.7
Question 3
In the testing quadrants model, which two pairs of viewpoints define the four quadrants?
- Manual versus automated, and functional versus non-functional
- Business facing versus technology facing, and support versus critique
- Unit versus integration, and positive versus negative testing
- Static versus dynamic, and black-box versus white-box
Show answer
- Manual versus automated, and functional versus non-functionalManual/automated and functional/non-functional are not the axes defining the quadrants.
- Correct answer: Business facing versus technology facing, and support versus critiqueThe axes are business- vs technology-facing and support- vs critique-the-product.
- Unit versus integration, and positive versus negative testingTest levels and positive/negative testing are not the quadrant-defining viewpoints.
- Static versus dynamic, and black-box versus white-boxStatic/dynamic and black-/white-box are not the axes of the testing quadrants.
In the testing quadrants model, tests can be business facing or technology facing, and can support the team (guide development) or critique the product (measure behaviour against expectations). The combination of these two viewpoints determines the four quadrants.
Syllabus section 5.1.7
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.