1.Fundamentals of testing (K2)155 minutes
Learning objectives for fundamentals of testing
The objectives identify what you will be able to do following the completion of each module.
1.1 Why is testing necessary? (K2)
LO-1.1.1 Describe, with examples, the way in which a defect in software can cause harm to aperson, to the environment or to a company. (K2)LO-1.1.2 Distinguish between the root cause of a defect and its effects. (K2)LO-1.1.3 Give reasons why testing is necessary by giving examples. (K2)LO-1.1.4 Describe why testing is part of quality assurance and give examples of how testingcontributes to higher quality. (K2)LO-1.1.5 Recall the terms error, defect, fault, failure and corresponding terms mistake and bug.(K1)
1.2 What is testing? (K2)
LO-1.2.1 Recall the common objectives of testing. (K1)LO-1.2.2 Describe the purpose of testing in software development, maintenance and operationsas a means to find defects, provide confidence and information, and prevent defects.(K2)
1.3 General testing principles (K2)
LO-1.3.1 Explain the fundamental principles in testing. (K2)
1.4 Fundamental test process (K1)
LO-1.4.1 Recall the fundamental test activities from planning to test closure activities and themain tasks of each test activity. (K1)
1.5 The psychology of testing (K2)
LO-1.5.1 Recall that the success of testing is influenced by psychological factors (K1):
clear test objectives determine testers’ effectiveness;
blindness to one’s own errors;
courteous communication and feedback on defects.LO-1.5.2 Contrast the mindset of a tester and of a developer. (K2)
Why is testing necessary (K2)20 minutes
Bug, defect, error, failure, fault, mistake, quality, risk.
1.1.1 Software systems context (K1)
Software systems are an increasing part of life, from business applications (e.g. banking) toConsumer products (e.g. cars). Most people have had an experience with software that did not work as expected. Softwarethat does not work correctly can lead to many problems, including loss of money, time or business reputation, and could evencause injury or death.
1.1.2 Causes of software defects (K2)
A human being can make an error (mistake), which produces a defect (fault, bug) in the code, in software or a system, or in adocument. If a defect in code is executed, the system will fail to do what it should do (or do something it shouldn’t), causing afailure. Defects in software, systems or documents may result in failures, but not all defects do so.Defects occur because human beings are fallible and because there is time pressure, complexcode, complexity of infrastructure, changed technologies, and/or many system interactions.Failures can be caused by environmental conditions as well: radiation, magnetism, electronic fields, and pollution can causefaults in firmware or influence the execution of software by changinghardware conditions.
1.1.3Role of testing in software development, maintenance and operations(K2)
Rigorous testing of systems and documentation can help to reduce the risk of problems occurring during operation andcontribute to the quality of the software system, if defects found are corrected before the system is released for operational