Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumSoftware Testing @ OneStopTestingTest Cases @ OneStopTesting

Message Icon Topic: Test case design

Post Reply Post New Topic
Author Message
Mithi25
Senior Member
Senior Member
Avatar

Joined: 23Jun2009
Online Status: Offline
Posts: 288
Quote Mithi25 Replybullet Topic: Test case design
    Posted: 07Jul2009 at 11:46pm
Star


A test case
is a detailed procedure that fully tests a feature or an aspect of a feature.
 Whereas the test plan describes what to test, a test case describes how to
 perform a particular test. You need to develop a test case for each test
listed in the test plan. Figure 2.10 illustrates the point at which test
case design occurs in the lab development and testing proces.


A test case includes:

    * The purpose of the test.

    * Special hardware requirements, such as a modem.

    * Special software requirements, such as a tool.

    * Specific setup or configuration requirements.

    * A description of how to perform the test.

    * The expected results or success criteria for 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.

Organizations take a variety of approaches to documenting test cases; these
range from developing detailed, recipe-like steps to writing general
descriptions. In detailed test cases, the steps describe exactly how to
perform the test. In descriptive test cases, the tester decides at the time
 of the test how to perform the test and what data to use.
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.

Test Case Design

Test Case ID:
It is unique number given to test case in order to be identified.

Test description:
The description if test case you are going to test.

Revision history:
Each test case has to have its revision history in order to know when and by
 whom it is created or modified.

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

Environment:
It tells in which environment you are testing.

Test Setup:
Anything you need to set up outside of your application for example printers,
 network and so on.

Test Execution:
It is detailed description of every step of execution.

Expected Results:
The description of what you expect the function to do.

Actual Results:
pass / failed

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

If failed - put in description of what you've observed





Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
tossy
Groupie
Groupie
Avatar

Joined: 20Aug2008
Online Status: Offline
Posts: 99
Quote tossy Replybullet Posted: 20Jul2009 at 12:57am
As I know test case design varies according to the tester and situation.

IP IP Logged
cool7575
Newbie
Newbie


Joined: 13Sep2007
Online Status: Offline
Posts: 28
Quote cool7575 Replybullet Posted: 30Jul2009 at 3:21am
Good article.

Software Testing

IP IP Logged
JustinH
Newbie
Newbie
Avatar

Joined: 28Jul2009
Location: United States
Online Status: Offline
Posts: 13
Quote JustinH Replybullet Posted: 22Sep2009 at 2:00am
... and don't forget test case generators such as the free one at http://www.hexawise.com

Test case generators have been proven to both (a) save the time spent on documenting the test cases and (b) improve test execution efficiency (e.g., number of defects found per hour).

See, e.g., http://hexawise.wordpress.com/2009/09/18/efficient-and-effective-test-design/

Also see: http://www.combinatorialtesting.com/clear-introductions-1

- Justin

- Justin
___________________________
Founder and CEO of Hexawise
www.hexawise.com
"More coverage. Fewer tests."
IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.297 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting