Hurdles in Testing
As in many other development projects, testing is not free from hurdles. Some of the hurdles normally encounters are:
- Usually late activity in the project life cycle
- No “concrete” output and therefore difficult to measure the value addition
- Lack of historical data
- Recognition of importance is relatively less
- Politically damaging as you are challenging the developer
- Delivery commitments
- Too much optimistic that the software always works correctly
Defect Distribution
In a typical project life cycle, testing is the late activity. When the product is tested, the defects may be due to many reasons. It may either programming error or may be defects in design or defects at any stages in the life cycle.
Testing Fundamentals
Before understanding the process of testing software, it is necessary to learn the basic principles of testing.
Testing Objectives
Testing is a process of executing a program with the intent of finding an error.
A good test is one that has a high probability of finding an as yet undiscovered error.
A successful test is one that uncovers an as yet undiscovered error.
The objective is to design tests that systematically uncover different classes of errors and do so with a minimum amount of time and effort.
Secondary benefits include:
Demonstrate that software functions appear to be working according to specification.
Those performance requirements appear to have been met.
Data collected during testing provides a good indication of software reliability and some indication of software quality.
Testing cannot show the absence of defects, it can only show that software defects are present.
Test Information Flow
Software Configuration includes a Software Requirements Specification, a Design Specification, and source code.
A test configuration includes a Test Plan and Procedures, test cases, and testing tools.
It is difficult to predict the time to debug the code, hence it is difficult to schedule.
RELATED POST
TEST CASE DESIGN
TEST CASE DESIGN TWO
DESIGN OF TEST CASES PART THREE
TEST CASE DESIGN PART THREE
TEST CASE DESIGN PART FOUR
TEST CASE DESIGN PART FIVE
TEST CASE DESIGN PART SIX
TEST CASE DESIGN PART SEVEN
TEST CASE DESIGN PART EIGHT
TEST CASE DESIGN PART NINE
REVIEWS AND APPROVAL OF TEST CASES
WRITING SOFTWARE TEST CASES PART ONE
WRITING SOFTWARE TEST CASES PART TWO
WRITING SOFTWARE TEST CASES PART THREE
WRITING SOFTWARE TEST CASES PART FOUR
No comments:
Post a Comment