Software Testing Technical White Paper: The main goal of Testing is to create robust application which works according to specifications. Testing has no impact on quality of software. It gives much realistic predictions in project completion. It can update code after alterations have been made.
For representing a model, FURPS is an acronym for classifying software quality attributes. FURPS is expressed in expanded form as Functionality, Usability, Reliability, Performance, and Supportability. FURPS are important for making the tests limited and must be a part of project documentation.
There are various software tests such a Unit tests, Business logic, GUI, Web, security, load, and deploy scenarios. Unit test is implemented by developer to validate the work. Business logic test is difficult to test and usually implemented by customer before takeover. GUI is very difficult to identify the user interaction and program flow. Web test is number of requests made in predefined order. Security is implemented in design time. Load test is to mention minimum hardware requirement and must also specify bottle necks. Deploy scenarios will enable support team to confront difficulties before end user does.
There are two basic types of tests, one is Positive (easy) which validate the function and another one is Negative (difficult) which does error handling of function. It gives robustness to application program.
The requirements of tests are clean environment, Specifications, scenarios, manuals, code comments, Test data (quantity and contents), and Limits.
Conclusion:
Software Testing needs a lot of bug. Testing is one of the ways that are derived as a cost center on a project and a struggle is done to justify testing cost. Testing should not be an excuse to write poor code for programmers. It extends development time and shortens support time. The test accomplished extends the time to complete the project but reduces money costs. It allows predict and solve problems.
Download Software Testing Technical White Paper.