Designing Test Cases

Sponsored Links:

A test case is a detailed procedure that fully tests a feature or aspect of a property. Whereas the test plan describes what the test, a test case describes how to perform a particular test. You require to create a test case for each test contained in the test plan.

A test case includes:
• The purpose of the test.
• The special hardware requirements, such as a modem.
• Requirements of special application, as a tool.
• specific configuration or setup requirements.
• The expected results or success criteria for the test.
• A description of how the test.

test cases must be written by a team member who understands the function or technology being tested, & each test case should be submitted for peer review.
Organizations take a variety of approaches to document test cases, which range from developing detailed, recipe-like steps to writing a general description. In detailed test cases, the steps portray exactly how the test. In descriptive test cases, the tester decides at the time of the test & how the test information used.Most organizations prefer detailed test cases, because the determination of pass or fail criteria is usually easier with this type of case. Also, detailed test cases are reproducible & are easier to automate than descriptive test cases. This is important if you compare the test results over time, such as when trying to optimize the settings. Of the Detailed test cases are more time to create & maintain. Moreover, test cases that are open to interpretation are not repeatable & can require debugging, time consuming it would be better spent on the test.

Test Case Design

Test Case ID:
It is the distinctive number assigned to test cases to be identified.

Each test case must have its revision history in order to know when & by whom is created or modified.

Description of test:
The description of the test case if you are going to try.

Function to be tested:
The name of the function to be tested.

It tells in which environment is being tested.

Test Setup:
All you require outside your application
for example printers, network & so on.

Performance Test:
Detailed description of each step of implementation.

Expected results:
The description of what is expected to function.

Actual results:
go / no

If not - give a description of what you have observed.

If you pass - What actually happens when you run the test.

No comments: