All you need to know about testing – preparation, process, evaluation and analysis

Type :

Theses

Pages :

72 pages

Format :

.doc

Published date :

04/23/2009

Category :

Business & market

Sub category :

Management

Oboulo.com selection criteria

$ 19.95 Add to cart

Summary :

Principles of testing
1. Testing terminology
Why testing is necessary?
1. Why do software faults occur?
2. What do software faults cost?
3. Exhaustive testing
Fundamental test process
1. What is the fundamental test process?
Psychology of testing
Re-testing and regression testing
1. What is re-testing?
2. What is regression testing?
The 'Oracle Assumption'
Testing in the lifecycle
Models for testing
1. Test design and test execution
The Waterfall Model, pre-Waterfall, and damage to testing
Economics of testing
Big Bang integration
Top-down integration and Stubs
Bottom-up integration and Drivers
Business process-based testing
Conclusion

Abstract

There is a lot of terminology surrounding testing, but not until recently has there been an industry standard. A new standard (first published in August 1998) seeks to provide a standard set of terms: BS 7925-i Glossary of testing Terms. Although a British Standard, it is being adopted by the International Standards Organization (ISO) and will hopefully become an ISO standard within two or three years. An error is something that a human does, we all make mistakes and when we do whilst developing software it is known as an error. The result of an error being made is a fault. It is something that is wrong in the software (source code or documentation - specifications, manuals, etc.). Faults are also known as a defects or bugs but in this course we will use the term fault. When a system or piece of software produces an incorrect result or does not perform the correct action this is known as a failure. Failures are caused by faults in the software. Note that software system can contain faults but still never fail (this can occur if the faults are in those parts of the system that are never used). Another term that should be understood is reliability. A system is said to be reliable when it performs correctly for long periods of time. However, the same system used by two different people may appear reliable to one but not to the other. This is because the different people use the system in different ways. The definition of reliability therefore includes the phrase 'under specified conditions'. When reporting on the reliability of a system it is important to explain under what conditions the system will achieve the specified level of reliability. For example, a system may achieve a reliability of no more than one failure per month providing no more than 10 people use the system simultaneously.