A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Testing start process – Programming and Construction

Testing start process has got 4 main phases namely:
– Requirements analysis
– Design
– Programming and construction
– Operation and maintenance

Here, we shall concentrate up on the third phase i.e., the programming and construction phase.
1. This phase takes a lot of time for testing.
2. The whole code written for the program has to be tested again and again many times for consistency till the perfect code is achieved.
3. The following areas are covered during this phase of the testing start process:
– Modular structure of the code
– Interface of the modules
– Data structures
– Functions
– Algorithms
– I/ O handling and so on.
4. Since this phase is quite long in time duration, it is important that you stick to a testing schedule by running tests in a systematic and organized manner on exact dates.
5. The tests then need to be annotated and saved properly.
6. Testers are advised to keep a checklist or a schedule with them to help during the testing periods.
7. If in certain part of the code some errors are found, they need to be rectified at once and again tested through all the tests meant for that segment.
8. These test runs should be recorded.
9. This is the phase where it is important to take help or assistance of the other colleagues other than the responsible programmer.
10. Colleagues can check the code at every step since the programmer might not able to recognize his own mistakes.
11. The program should be explained to the whole development team by the programmer so that the logic that has been used could be questioned and possible errors can be identified.
12. Based up on the errors listed, a check list of the errors should be produced and one by one all these errors should be located and rectified as soon as possible and before moving on to the next phase of the software development.
13. The testers and the programmers must know how to make use of all the available tools.
14. For programmers using various compilers as well as interpreters installed on the system can be useful.
15. Since for all the implementation language differs, the way of code generation capabilities and error analysis.
16. The program under testing must be stressed to the maximum limit.
17. The stress should be focused up on the structure of the program, its internal functions, data structures and all the other visible functions as well as functionality.
18. The test set should be a mixture of both valid and invalid data.
19. Testing of code should be done part by part i.e., either taking a piece of code or module or a group off modules one at a time.
20. Again, one testing should be carried out on the integrated form of these modules.
21. When the number of all possible interactions is kept small it becomes easy to isolate the errors. 22. Instrumentation is another technique that can be used in this regard.
23. It involves insertion of a small code in to the program just for measuring some characteristics of the program. The check list of the tester must also include the following:
– Array bound checks
– Checking of loop controlled variables
– Determination of the range of the key data values
– Tracing execution of the program
– Number of times a single statement is executed.

24. Testing process shall be continued till 0 errors are indicated by the compiler.
25. It is the tendency of the errors to cluster and thus become more error prone.
26. Such modules need to be treated with special scrutiny.
27. There are certain metrics which aid in measuring the thoroughness:
– Statement testing
– Branch testing
– Path testing
28. Among these three, the most used one is the statement testing.
29. The cost of an error decides how much testing it needs.
30. Usually the programs and functions which are quite critical need such a thorough testing as compared to the less critical functions.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>