There is no ';one size fits all'; answer to your question.
Each project brings unique aspects to the approach.
You may begin by becoming thoroughly acquainted with the full scope of the project. Gain an understanding of the functionality, environment and topology.
Communicate with analysts, architects and developers to clarify your vision.
Become intimately familiar with the specified requirements.
Be imaginative in considering logical grouping of scenarios encompassing aspects such as work flow, interfaces, protocol, storage/retrieval, data requirements, etc...
Maintain some sort of matrix illustrating trace of test cases to requirements to reveal potential efficiencies.
And... about a ';jillion'; other things!
This is perhaps the most challenging aspect of testing.How to create test cases in testing?
Go thru the Requirements documents thoroughly and start splitting the application into different scenario's.
Each scenario should be depicted flawlessly following some guidelines for test case writing. For example, Conditional statements shouldn't be used in a test case, a test case should be independent...........How to create test cases in testing?
You need to extend the TestCase class and create your own Test Methods.
Suppose if you want to create a test method for a method named say, XYZ() then use the method name for test case as:
testXYZ().
This would help you maintain the test cases.
Thank You!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment