A simple Test Case Writing

A test case is a detailed procedure that fully tests a feature of the software application or an aspect of a feature, depending on the complexity of the application..this describes the various permutation and combination of steps to be carried out to test a feature.




To design a test case, we need to identify certain things:

• 1. Identify the test case and explicitly associating it with a feature to be tested.
• 2.Mapping test cases with requirements by using requirement traceability matrix.
• 3. Purpose of the test.
• 4.Creating a list of specified criteria for which the test should be tested.
• 5.Creating a list of tests that should be exercised as a consequence of the test.
• 6.Assembling of expected results occurs, when test is executed
• 7.Creative scenario, or conditions in which tests are executed.
• 8.Assimilate all information that adds value to understand the test.Since test case designing is time-consuming. However, if this activity is done extensively then it enables the tester to find the goal of testing with in time.

A test case also includes certain things that is very important in a sucessful testing.

• 1. Purpose of testing.
• 2. Hardware and software environment required.
• 3. Special configuration requirement like making war room.
• 4.Detail of the testing processes.
• 5.Expected results or success criteria of the test.

''Test cases should be written by a team member who understands the function or technology being tested, and each test case should be submitted for peer review.''

Most organizations prefer detailed test cases because determining pass or fail criteria is usually easier with this type of case. In addition, detailed test cases are reproducible and are easier to automate than descriptive test cases. This is particularly important if you plan to compare the results of tests over time, such as when you are optimizing configurations. 

• Detailed test cases are more time-consuming to develop and maintain. 

• On the other hand, test cases that are open to interpretation are not repeatable 

• and can require debugging, consuming time that would be better spent on testing.