Basic principles in software testing

Of the many principles that each software testing tester has probably identified for himself, there are the main ones in the opinion of the community of testers who would like to single out:

1) Exhaustive testing is not possible with any of the testers. I think that everyone understands that it is impossible to test all possible cases and combinations, of course, if this is not a trivial case. All cases simply can not be included in the test suite, since it would take us a very long time and in the end would not be worth the effort. If every tester sits down and carefully thinks through all the scenarios, and this can be better. Therefore, in software testing is taken after he focused efforts in testing for more risky and priority cases.

2) Accumulation of bugs. If you take the product and break it in moderation, then during the testing you can see that the bulk of the bugs are in one or more modules, so you can see the effect of the accumulation of bugs. Typically, this can be observed in completely different products. In order to effectively test our product, you should distribute your efforts in testing at real density, while theoretically the expected density. Over time, the trend with accumulation of bugs can vary from module to module. This should be monitored and redistributed in future testing.

3) Efficiency of early testing. It is very important that testing starts as early as possible and anticipates possible mistakes that the developer can make. Before you develop and test a product, you should determine all the specifics, possible conflicts in the specification, the impossibility of a new fish-therapy, Remember, the earlier there are bugs the cheaper to fix them.

4) Paradox of the pesticide. If you write test cases, run them many times, then eventually these cases will not help us find new bugs. Therefore, there is a practice in testing, when they revise and modernize test cases to catch some new bugs. Test cases can be complicated, be versatile so as to cover all the components, all that is needed in our turn will help us find more interesting and new bugs.

5) Testing depends on our product. There are many programs, products, and each of them should be approached individually in terms of testing. In some more efforts in testing you need to be safe, in some kind of usability. Therefore, you should not row all the products under the same comb and test it on any one template.

6) Testing shows the presence of bugs in the product, but not their absence. Many people think that if the new functional has passed the testing phase, then everything is bugs. This is the error of judgment. In the testing process, many bugs can be skipped and this will not mean anything if it passed the test, but now this product is 100% working correctly. Software testing companies helps to find all the bugs.

7) The product is well tested and it seems that there are no obvious bugs, then this is a good product. Sometimes by testing and looking for functional bugs, we forget to look at the other side and ask if the user needs it. If this fitcha does not meet expectations and its needs, no matter how high-quality our product was - it's not so important.

© ReachLink SA/NV 2009 - Terms & Conditions | News | Articles