Validating and improving test case effectiveness
Level 3: This is the stage in which you will group some test cases and write a test procedure.
Test procedure is nothing but a group of small test cases maximum of 10. This will minimize human interaction with system and thus QA can focus on current updated functionalities to test rather than remaining busy with regression testing.
Test cases derived from such a model are functional tests on the same level of abstraction as the model.
If you have strong test and QA processes, the number of defect escapes should be small (3-4) and minor in nature.Without clear, quantitative coverage criteria there is no way to know when testing is complete.Application of rigorous, measurable coverage criteria routinely results in software with few, if any, defect escapes.It’s always a good practice to name your test cases in a way that it makes sense to anyone who is going to refer the test cases in future (including YOU! There is a project called “Online” which has a functional area named “Login” Now, I want to write a test case to verify a simple check whether the user is able to login to the website using an email and password.To keep things simple, instead of naming the tests as TC_01, I could use the below naming convention for my test case so that it gives a brief idea of what the test is for just by looking at its name.
Search for validating and improving test case effectiveness:
An all too frequent experience for IT managers is to have a software release go into production after multiple iterations of testing, only to immediately experience significant defects that went undetected during testing.