Quality is delighting customers
Why would some one share confidentail and propritary documents ????
If you have any questions you can ask but not documents.
1)no duplicate test cases
2)no missing functionalities
3)no invalid test cases
4)expected result should be clear
5)should have clear navigation steps
6)test data should be specified (if required)
pre conditions should be specified (if required)
3) No Invalid test cases... what do you mean by this....?? as far as I know.. According to an Study done by IBM , 90 % of the test cases should be Invalid test cases... !
I would appreciate your Clarification..
if the failed test case is causing 50% test cases blocked,how do u handle another test cases?
can u plz send me answer then i vl tell about invalid test cases?
two different questions .. okay no issues.........
If failed test cases are causing 50% test cases blocked , then I shall not continue my testing and rather I would wait for the CM team to get us available an Stable build which is in sane enough condition to be tested...
oh my God.. is there really any relation .....???
SRS documents are requirement documents and testers refer to that document to understand the system requirements before writing test cases. There is no trivial solution or a standard template to generating test cases from a SRS document. You need to review the entire document, understand the requirements and how they tie to the overall solution before writing test cases.
There are a lot of websites that give you pointers on writing effective test cases.