A Test Case is a set of actions executed to verify a particular feature or functionality of your software application. A Test Case contains test steps, test data, precondition, postcondition developed for specific test scenario to verify any requirement. The test case includes specific variables or conditions, using which a testing engineer can compare expected and actual results to determine whether a software product is functioning as per the requirements of the customer.
1.Test case are need to regular revision and update
Anything changes or update in software requirements its directly affect the test case. So whenever requirements are updated/altered, TC need to be updated.
2.Distribution TC among the other tester who will execute these
Normally different tester test different function/components so TC are divide among the tester according to their areas.
3.Test case have a tendency of interdependence
Interesting and important behaviour of the TCs,denoting that they can but interdependent on each other. Form medium to large application with complex business logic, this tendence is more visible.
1.Keep it simple but not too simple; make it complex but not too complex
2.After documenting the test case,review once as a tester
3.Bound as well as ease the tester
4.Be a contributor
5.Never forget the end user
1.Composite steps
Composite means when write any test case broken down it as many as possible steps.
2.Application behaviour is taken as expected behavior
3.multiple condition in one case
1.User requirements document
In this document that list the business process,user profile,user environment,interaction with other system,functional,non function requirements, performance and security requirements
2.Business use case document
3.Functional requirement document
4.Software project plan
5.QA/test plan
Resources
1. www.softwaretestinghelp.com