Lots of issues are faced with test cases when some one refer to a test case document for any review, test execution or any kind of reference these issues could be related to:

-	Terminology followed by the test case writer
-	The formatting of the document
-	Language followed to mention test case attributes(Test Objective, steps, TC ID’s etc)
-	Organization/grouping of test cases within the document with respect to software feature for which test cases are written.
-	Different test case writer follow different patterns
-	Other issues.

So after reading this paper following advantages can be achieved:

-	Find a common language to write ‘Test Case Attributes’ so that multiple test case writers are on the same track.
-	Find a way to write/organize test cases in a document to make the review/execution/test scope analysis/updating an easy task.
-	Make the STC document a good source of product learning for a newcomer.
-	Find a way to be ready with requirements (Hardware/Software) before starting testing phase.
-	Find a practiced way to derive test cases from an FDD (feature description document) to capture maximum test scenarios.

Emphasis in this document will be on how to create/update ‘Test Case’/’Test Case Document’. Guidelines for writing/updating test case attributes, test case document/formatting will be provided here. It has been prepared based on test team members feedback and my experience.