Quality is delighting customers
1 You read User Requirment Docs.
2.Then Write test case as per Requiremnt for +ve & -ve.
3.After realease check test case & add or remove as per fianl product.
comman for all
Before write test cases you have to prepare a test scenario of the application.For test scenario you have to look over the major functionalites page by page.After prepairation of test scenario you can write test cases.
to write the test cases make sure u have good knowledge on functionality of the application. Then if u are provided with documents like business design doc, functional doc, use case doc, better go thru it. to make the test cases look simple and readble, segregrate them in to GUI, +VE, -VE test cases
in GUI u may consider things like AVAILABILITY, ALLIGNMENT, CONSISTENCY, SPELL CHECK and LOCATION OF THINGS MENTIONED
where as in rest of 2 cases in mentioned have +ve and -ve flow respectively
Few things that I would keep in mind while writing test cases.
The replies metioned by our friends are to the point & few more that I am contributing :
- create a template & get that approved by the higher authority.
- understand the application's expected behavour.
- make sure that you know about what is not expected behaviour of the application.
- Does your manager expect you to write test cases that are descriptive(like - go to action 'add account'. Click on the action, etc) or has to be crisp & short(like open the Add Account form). Get this confirmed.