Traditionally, s/w development has adopted sequential approach to development process, beginning with requirement gathering and ending with formal acceptance testing of the end product. This model is called a V Lifecycle model or Waterfall Lifecycle model.
The deliverables from the first three phases of the lifecycle forms the input for testing process. These deliverables are in the form of specification documents.
• |
Requirements Phase -> complete specification what the software is expected to do |
• |
Architectural Design -> identifying entities within the software and their relationships between entities |
• |
Detailed Design -> where each of the entities scope and behavior are described in detail |
The following table describes the different testing activities and some tools of our expertise.
| Phase |
Testing Activities |
Types of Tools |
Management Tools |
| • |
Requirement Specification |
| • |
Architectural Design |
| • |
Detailed Design |
|
| • |
Planning |
| • |
Design & Specs |
| • |
Input / Data |
|
| • |
Planning |
| • |
Test Requirements |
| • |
Test Management |
| • |
Test Design |
|
| • |
Compuware/ QADirector |
| • |
Mercury/ TestDirector |
|
| • |
Coding |
| • |
Unit Testing |
| • |
Integration Testing |
|
| • |
Unit & Integration |
| • |
White-Box |
| • |
Black-Box |
| • |
Performance |
| • |
Resource testing |
|
| • |
Static Analysis |
| • |
Debugging |
| • |
Code Coverage |
| • |
Dynamic Analysis |
| • |
Memory Leak |
|
| • |
DevPartner |
| • |
TrueCoverage |
|
| • |
System Testing |
| • |
User Acceptance |
|
| • |
User-Interface |
| • |
System |
| • |
Performance |
| • |
Acceptance |
|
|
| • |
Compuware - QALoad |
| • |
Mercury - LoadTest/ LoadRunner |
|
Regardless of the type of testing, it is advisable to observe strictly to the following rules for effective and consistent results
• |
Always test against a specification |
• |
Document the process; strategy, plans, and results. |
• |
Begin at the top ; Finding more errors earlier will ultimately reduce cost |
• |
Test both ends – Positive part, that is it does what it is expected to do; Negative part, that is what it does not what it shouldn’t |
• |
Complement testing wity technique such as static analysis and dynamic analysis |
|
