|
|
||
|
Activity:
4 comments
414 views
last activity : 07 06 2010 20:18:04 +0000
|
||
|
|
Tradationally testing is taken up at the systems integration phase by which time it is 60 to 75% code complete. Even in a interative approach by the time testing starts the code for that particullay interation has been completed. As such we end up performing a quality control function and that too by taking close 100% of the sample. It is both expensive as well cost of defect fixing is very high. Moreover a root cause analysis will reveal that more often than not the requirements are in question either the developer did not understand them correctly or they were not clearly defined etc.. What is really surprising that so little effort has gone into requirements testing inspite of the cost of unclear requirements remains very high. A simple requirements testing practise would include
1. Testing if the requirments are designed for testing i.e. if we can write test scenarios based on the same. If not then it is very possible that the developers will not be able to understand them.
2. Testing if the requirments are tracable i.e. sections in the requirements can be clearly mapped to deisng modules or existing test scenarios.
3. Testing if the requirements are measurable i.e a requirement for an internet banking application may say - that all access should be logged but if the level of logging is not specified in detail it can lead to major performance and comliance issues.
-Anyone who has experience is setting up this practice or practically using this , please share your experience.
Abhijeet Dixit
|
|
|
|
|
|
|
|
|
|
|
|
Managing people is tough probably beause there is no science behind it. The same stimulus can yeld amazingly different responses from different individuals even sometimes from the same individual. There are too many variables to take into account... |
Usually in payment systems there are standard validations i.e. for the account number, balances, entitlement etc.. Some of them are performed in the payment system and some in the general ledger system. However there is a grey area and is always a... |
Automated testing is ultimatley writing code to verify code. As such the basic act of verification will be based on human intillegence. So Manual verification is the basis or core of testing. |