Testing is the last step in the software life cycle. Time pressure is well known and increasing because too many defects are found late and have to be repaired. This seminar shows you how to cope with this situation. Early test planning and the use of reviews achieve a high degree of preventive defect removal. Still, at the end you have to execute the tests, in order to measure the final product quality. The ultimate aim, however, is that defects show up during test preparation rather than test execution.

Testing can never completely identify all the defects within software. Instead, it furnishes a criticism or comparison that compares the state and behavior of the product against oracles—principles or mechanisms by which someone might recognize a problem. These oracles may include (but are not limited to) specifications, contracts comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, applicable laws, or other criteria.

Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing is the process of attempting to make this assessment.

A study conducted by NIST in 2002 reports that software bugs cost the U.S. economy $59.5 billion annually. More than a third of this cost could be avoided if better software testing was performed.

OBJECTIVES OF TESTING

Executing a program with the intent of finding an error.

To check if the system meets the requirements and be executed successfully in the Intended environment.

To check if the system is “ Fit for purpose”.

To check if the system does what it is expected to do.

Executing a program with the intent of finding an error.

To check if the system meets the requirements and be executed successfully in the Intended environment.

To check if the system is “ Fit for purpose”.

To check if the system does what it is expected to do