Seven principles of ISEB software testing

2019-04-21 Technology No comment

The ISEB Software Testing Fundamentals training course introduces students to the basics of software testing, including the reasons for testing, the basic testing process, and general principles that support testing good practices. Understanding these principles and understanding how they affect software testers is critical to testing the foundation exams with ISEB software.

1. The test shows an error

In other words, the test can indicate a problem, but there is no problem.

This principle is at the heart of the ISEB software testing guide. A savvy test analyst understands that even if the test does not find any errors, the subject of the test is not an unnecessary error.

The key goal of testing is to identify defects. Working under the assumption that each product contains a defect, the test that displays the error is usually better than the test that does not produce the error. All previous tests should be designed to reveal as many errors as possible.

2. Thorough testing is impossible

Thorough testing imports all possible data into the software to ensure that untested conditions do not occur after the software is released. Extremely simple application exceptions, the number of possible data combinations is very high; for testers, risk and priority are more effective and efficient, so testing is for testing needs.

3. Early testing

Products [including documentation, such as product specifications] can be tested as soon as they are created. The ISEB Software Testing Guide recommends testing the product as soon as possible to fix the error as quickly as possible. Studies have shown that errors found late in the development process usually take more to resolve.

For example: errors in product specifications can be fairly straightforward to fix. However, if the error is transferred to the software code, fixing the error can become expensive and time consuming.

4. Defect clustering

Studies have shown that problems in software projects tend to focus on a limited set of modules or regions. Once these areas are identified, an efficient test manager can focus on testing sensitive areas while still searching for errors in the remaining software modules.


As with over-used pesticides, a set of tests that are reused on the same software product will reduce efficiency. Using a variety of tests and techniques will expose a range of defects in different areas of the product.

6. Testing depends on the context

The same test should not be fully applied. Different software products have different requirements, functions and purposes. For example, tests designed to be executed on a website may be less effective when applied to an intranet application. If you do it on a forum, the tests designed for credit card payment forms may be unnecessarily strict.

In general, the greater the probability and impact of damage caused by software failure, the greater the investment in performing software testing.

7. No error fallacy

The statement test found no errors and was different from the statement software "no error". To ensure that the appropriate software test procedures are performed in each case, the tester should assume that all software contains some [though already understood] faults.


Good practices in software testing are an important part of ensuring the quality of IT products. While software testing does not guarantee that the software does not contain any errors, it does help identify and reduce failures, thereby increasing the likelihood of successful software implementation.

Compuclever Antivirus Plus,Click here! New Neuro-editing Technology For Ultimate Wealth Success (view mobile),Click here!

leave me a message

Copyright@WaiWaitech inc. © Technology All rights reserved.  

User login ⁄ Register