You may be wishing that you had a magic tool that would automate all of the testing for you. If so, you will be disappointed.
Category: ISTQB – CTFL
Let’s review what you have learned in this chapter. From Section 5.1, you should now be able to explain the basic ideas of test organization.
5.6.2 What goes in an incident report? An incident report describes some situation, behavior or event that occurred during testing that requires further investigation. In
Recognize the content of the [IEEE 829] incident report. (K1) Write an incident report covering the observation of a failure during testing. (K3) Let’s wind
5.5.3 Project risks We just discussed the use of testing to manage risks to product quality. However, testing is an activity like the rest of
Describe a risk as a possible problem that would threaten the achievement of one or more stakeholders’ project objectives. (K2) Remember that risks are determined
Summarize how configuration management supports testing. (K2) In this brief section, we’ll look at how configuration management relates to and supports testing. You will come
5.3.2 Reporting test status Test progress monitoring is about gathering detailed test data; reporting test status is about effectively communicating our findings to other project
Recall common metrics used for monitoring test preparation and execution. (K1) Understand and interpret test metrics for test reporting and test control (e.g., defects found
5.2.6 Test approaches or strategies The choice of test approaches or strategies is one powerful factor in the success of the test effort and the