how to write test case ?

after get requirement tester should start, write a test case. but i am
confuse about testcase format, i usually wrote test case like this
format-

but some body called them use case. need your help and a format how can i write test case.

thanks :)

0 members like this

▶ Reply to This

Replies to This Discussion

Permalink Reply by Siddiq on November 11, 2010 at 4:35pm

Indeed is a test Case, who said you it's a USE Case?

▶ Reply

Permalink Reply by parvesh kumar on November 11, 2010 at 4:51pm

Hi frnd
Check this Test case format

Test Case: API 1.0 Customer Module

Work Stream: Test script created by: Parvesh kumar Test script creation date:
Test script reviewed by: Test script review date:
Use case Test script executed by: Test script execution date:
Test script execution verified by: Test script execution verification date:

Test Case No. Description Steps to execute the Test script (M) Expected Results (M) Actual Results (M) Test Results Pass/Fail (M) Testing Pre-requisities Qualification of tests (M) Program Tested (O) Remarks (O)

▶ Reply

Permalink Reply by Mark Crowther on November 11, 2010 at 4:52pm

In one way it is closer to a Use Case as it describes a series of actions that a user can perform, we might tend to think of Use Cases being expressed with UML but that needn't be the case.

In another way the example you've given is a very traditional looking test case/set of test cases. However, if you look over the above and consider 'what is actually being TESTED'? it might suggest why it's not really giving us test cases and looks more like we're checking Use Cases.

The above are not really testing anything but they are checking a collection of functionality and charactersitics of the items in a very safe way. To turn these into tests you'd need to go outside of the Use Cases that are describing that basic functioanlity and characteristics. To do that you can apply some exploratory testing and your favourite test heuristics.

For example...

What is the font style and size, does it vary if you zoom in and out, does it all fit if you zoom in a lot, what if you don't click yes or no, is the pop-up modal or can it be dismissed by clicking the window 'x' or just clicking another window, what if it's open and I log out (assuming I can get focus on another window), what if I just kill the browser / app and then re-open - if I'm now logged out but the report abuse window is open can I submit it even where I should be logged in? Is the window reached by a URL (in Firefox - right click, page info and get the URL) and can I got to it directly? If so can I write a script to spam the reporting abuse? (Yes, in Selenium IDE that's easy)

That's more like testing, the rest could certainly be seen as checking Use Cases.

Mark.

▶ Reply

Permalink Reply by Dr M V Ananathakrishnan on November 11, 2010 at 7:55pm

http://www.softwaretestinghelp.com/how-to-write-effective-test-case...
www.ebookpdf.net/___sample-software-test-cases-pdf_ebook_.html

ALB

Dr Ananthakrishnan

▶ Reply

Permalink Reply by pawan kumar on November 11, 2010 at 9:19pm

In my company we follow the following format for writing a test case:
1.Test Case Title
2.Description of the test cases in 1 or 2 lines
3.Pre-condition(if required for particular functionality)
4.steps for the test case.
5.Expected result.

Type of test case: UI test case or functional test case etc.

▶ Reply

Permalink Reply by visa on November 11, 2010 at 9:41pm

writing of test cases format will be
Firswt will explain about businesscase:
Business case :Business case will contain many number of testcases
Test case : Testcase should specify the test case id Test case name,precondition,expected results,Test data
------------------------------------------------------------------------------------------------------
TestCase precondition Expected Result Test data Test case id
Name

-------------------------------------------------------------------------------------------------------