ISTQB CTFL
Risks, test monitoring, defect management and tools
Easy
Risk management
- Which two factors characterise a risk?
- What value does the likelihood of a risk have?
- What is a product risk?
- What is a project risk?
- What does product risk analysis consist of?
- What does product risk control consist of?
- What is a test approach called that selects and prioritises activities based on risk analysis and risk control?
- What applies to risks with a high risk level?
Test monitoring and completion
- Which metric is a defect metric?
- When is a test completion report produced?
- Which means is suitable for communicating test status?
Configuration management
- What does configuration management do for testing?
- What applies to a configuration item approved for testing?
Defect management
- What typically belongs in a defect report?
- What does severity describe in a defect report?
- What does the ISO/IEC/IEEE 29119-3 standard call defect reports?
Test tools
Medium
Risk management
- How is the risk level determined in the quantitative approach?
- Which examples are project risks?
- What consequences can product risks have when they occur?
- What are the results of product risk analysis used for?
- Which techniques are suitable for risk identification?
- Which responses to an analysed product risk are possible?
- Which testing measures mitigate product risks?
- How is the risk level usually determined in the qualitative approach?
Test monitoring and completion
- Which assignment of metric to category is correct?
- What does a test progress report typically contain?
- What does a test completion report typically contain?
- What are control directives in test control?
- How do test progress and test completion reports differ in frequency?
- What is a cost metric in testing?
Configuration management
Defect management
Test tools
Hard
Risk management
- A defect in the credit function occurs with a likelihood of 0.2 and would cause €50,000 of damage. What is the quantitative risk level?
- Risk A: likelihood 0.5, damage €8,000. Risk B: likelihood 0.1, damage €30,000. Risk C: likelihood 0.3, damage €20,000. In which order should they be treated by risk level?
- Risks are collected in a project for a timetable app. Which are product risks?
- A team notices that the scope keeps growing and the test tool hardly supports the new platform. How should these risks be classified?
- An online bank's risk analysis rates "transfer to wrong IBAN" as very high and "colour scheme in dark mode" as low. Which conclusions are appropriate?
- A shop decides to cover the risk of payment defaults through an external payment provider with a default guarantee. Which risk response is this?
- After the launch of a customer portal, risk monitoring shows that the extra security tests hardly reduced a risk, and a new risk arises from an interface. Which statements are correct?
- Why are identified risks categorised during risk assessment?
Test monitoring and completion
- A test manager reports to the board and to the development team. What should he bear in mind?
- A team is distributed across Berlin, Pune and Toronto. Which forms of communicating test status are particularly suitable?
- A test completion report says only "all tests green", although two risks were not mitigated and three defects are open. What is missing?
- A test manager wants to know whether testing is on schedule and how good the product is. Which metrics fit?
Configuration management
- A customer reports a failure in version 4.2 while the team is already working on 4.5. How does configuration management help?
- Which statements about configuration management in DevOps are correct?
Defect management
- A defect report reads: "Export doesn't work. Please fix quickly!" Which details are missing for it to be useful?
- A typo in the company name on the home page barely affects functionality but must be fixed before a trade fair on Monday. How should severity and priority be rated?
- A reported defect turns out to be already recorded, another is to be fixed only in the next release. Which statuses fit?
Test tools
- A team relies on an open-source UI automation tool whose last version is two years old; the new browser is no longer supported. Which risks show here?
- A company buys an expensive automation tool and expects regression tests to run without further effort from next week. Which objections are justified?
- A team wants to simulate 5,000 concurrent users and provide ready-to-test environments via containers. Which tool types are needed?