• admin
• Aug 10,2010
• In: Articles

Why do we test software?

To test the software there are several good reasons.

1. Providing programmers the information they can use to prevent errors.
2. Providing managers with information they need to make a reasonable assessment of risk when using the facility.
3. Creating an object, as free from error.
4. Creating a project, testable, that is a project that you can easily check for compliance, the distorted and that will be easy to maintain.
5. Check distorting objects using as formulated, did not set out the requirements of [MYER79]. It is also called "hacking software".
6. Check whether the object (see its validity), that is to show that it works correctly.

Information necessary for the implementation of paragraph 2, is determined by the extent to which the object is doing the right (ie the quantity of subtests passed and not passed), and some framework within which the object can not be distorted. That is the extent to which the object is not compromised, and the extent to which it operates. That the extent to which the object is free from error, is also abroad, to which it complies with and is not distorted. Thus, we have three main objectives: good design, distorted, verification of compliance.

All that people write, contains errors. Testing something is not equivalent to the assertion that it’s something free from error. Programmer can not think of everything – especially about all the possible interactions between different features and different parts of the program. We are trying to crack the program because only this way provides us with confidence that the product is ready for use.

Another challenge testing – an accumulation of information for management. Given the necessary information and a sufficient number of tests we can with reasonable confidence that the program is ready for use. Ultimately, this is exactly what they pay for the testers, and – assistance in creating a useful program.

The highest purpose of testing – this assurance: the accumulation of information, which is returning to the programmer, it helps to avoid past mistakes and improve the quality of software in the future.

Dirty test (or negative test): a test of the primary purpose of which is to check the distorted, then there is a test designed to crack the program.

Net test (or positive test): test, the primary purpose of which is to check the conformity that is a test designed to demonstrate the correct operation of the program.

The test is effective if its results are revealed symptoms of existing errors.

The specifications typically specify only those requirements that must be checked for compliance (ie, that the object should do) and do not contain requirements that must be checked for a distorted (ie, that the object should not do). Since the number of actions that an object must fulfill, of course, a number of actions that the object should not do, is not limited to, the general considerations we can assume that the dirty tests should be substantially larger than pure. So it really is. In-designed test kits dirty number of tests is one of the net as a 4: 1 or 5:1.

See Also