Quality is delighting customers
This problem was raised six months back by someone. I suggested practical approach which I implemented successfully so you may refer the solution to this at Concern-19 and Concern-4 in below url
I welcome your comments.
If requirements are changing continuously, I try to keep my test cases at a high level so that I do not need to spend an excessive amount of time rewriting test cases.
Could u pls explain about the levels of testcase?
How you will set the levels and where you will mention this?
I will be happy if you explain in detail.
High level test case implies not writing the test case steps in detail, instead writing statements that describe the steps in general. Here is an example for a test case to Add User in my scenario -
Normally a test case to add a user would be -
After a few days, the client may decide to change a few things on Add User form.
All this changes would require the test case to be updated. So instead I would write a high level test case for the same scenario in the foll way.
Again if there are some changes you may not have to update the test cases.
Though there may be a lot of changes to this test case, this is how I write test cases at my place.
Nice explanation Tahir.... Yes... A high level test case is nothing but a test case without the concrete data.... during Analysis and Design phase of Testing process we design high level test cases and Priority is also set to those test cases .. and coming down to Implementation and Execution, in this phase a high level test case is converted in low level test cases............ but since the requirement is changing frequently .hence we will simply design High level test cases and test data will be put in, without documenting .....