Software Testing A Self-Assessment

Software Testing A Self-Assessment

Computer software test is a difficult so thevastarrayofcomputerprogrammelanguages, working systems, and computer hardware platforms thathave evolved. And, whilerelatively a few people used computer program in 1970s, today about any one in business and training could justlycomplete a work without using a computer. Furthermore, themachine them selves are hundred of time then powerful those

early devices.

The Computer program studies three integer values from input dialog. Thethree values represent the lengths of the sides a triangle. The softwareprogram shows a message at states of matter is triangle,isosceles, or equilateral.

The Psychology of Testing

You test a program, you need to adding some value to it.Adding value through testingmeans rising the quality or reliabilityof computer program. Raising the reliability of program means findingand removing computer errors.

Once again, this is upside-down. “Unsuccessful” denotes somethingundesirable or disappointing. To our way of thinking, a wellconstructedand -executed test of a piece of software is successfulwhen it finds errors that can be fixed. And that same test is also successfulwhen it eventually establishes that there are no more errors tube found. The only unsuccessful test is one that does not properlyexamine the software and, in the majority of cases, a test that found no errors would likely be considered unsuccessful, since the concept of a program without errors is basically unrealistic.

Software test case that finds a new error can just be considered unsuccessful;

quite, it has proven to be a valued investment. An unsuccessful test program case is one at causes a program to produce the accurate result without finding any errors.

Inspections and Walkthroughs

Inspections and walking troughs involve a team of people reading or

visually inspecting a software program. With either method, participants must

conduct some preparative work. The climax is a “meeting of ideas,” at a participant conference. The object of the meeting is check errors but not find solutions the errors. That is test

not debug.

It methods generally are effective in finding from 30 to 70marks of the logic-design and coding errors in typical software programs.They are not effective, however, in detecting high-level design errors,such as errors made in the requirements-analysis process. Note that success rate of 30 to 70 percent does not means at up to 70 percentof all errors might be found. Remember that Chapter 2 tells as we can never know the total number of errors in a software program. Rather, this means these methods are effective in finding up to 70 percent of all errors found by end the testing process.

Soft ware Testing-Case Design

Case module testing is mostly white-box oriented. One reason is that you test larger entities such as entire software programs (which will be the case for subsequent testing processes), white-box testing becomes less feasible.A second reason is that the subsequent testing processes are oriented toward finding otherwise types of errors (for example, errors not necessarily associated with the program’s logic, such as the program's failing to meet its users’ requirements). Hence, the test-case-design procedure for a module test is the following: Analyze the module's logic using one or more of the white-box methods, and then supplement these software test cases by applying black-box methods to the module's specification.