Format for writting test cases

In many examples we see text cases are written simply line-wise on a page, while in some examples it is written in tabular form. can anybody tell me what is actual format for writting test cases. (Give proper details for test cases for simle login form, having fields ([1- user id.], [2. passward ], [3. ok button], [4. cancel button]) you can send the exact details used.

NOTE : [I][This question was asked by sanjayamb][/I]

hello sanjay..

The templates differ company to company and mostly considered the build also... whether it is medium or large size....Mostly so many companies prepare with Excel sheets . The companies who have the license use Test Director and etc., ..... there also we can manupulate the fields according our build needs ...

prasad.gandra

Test Cases can be generalised with the following fields wihich are mandatory:

Test Case Title (Refers to the Functionality of the product being tested)
Test Case version( Required when multiple changes takes place in the product and the Test Case as well)

The above fields are single value field provided one time at the heading of the Test Case.

Fields which can be used in a tabular form for the Test Case are:
1) Step No (Sequence used for no of test steps in the Test Case)
2) Test Step (Actual step to be followed or executed)
3) Expected Result ( Result which is expected as a normal behaviour)
4) Actual Result ( Result which we actually get after we execute the test step)
5) Defect id ( If the Expected and Actual result do not match then we need to log a defect either in a Defect logging tool or by maintaining an Excel sheet of defect incurred. The corresponding id generated for the defect logged should be mentioned in this column so that we can get the exact track of which defect is looged against the said Test Case.)
6) Test Step result ( Whether the step is Passed or Failed is to be mentioned here)

all the fields mentioned are generalised fields. Test Cases can be written either in Excel sheet or in Word ... But they should be written in a Tabular format. It helps out in a better understanding of the Test case.

General method for test case format is tabular method, why , because generally every company use excel sheet for writing test cases.Testcases fields have already been posted by others.

We have the following details in Test Case document::D

Test Case ID, Title, Feature to be tested, Test suit ID, Priority, Test environment (h/w and s/w), Test duration (date and time), Test setup (preconditions for testing), Test Procedure/script, step no*, action*, Input required*, expected*, actual+, result+, defect id+ if any, status

* - before receiving build.
+ - after receiving build and applying test.

For each of the input objects:
Object name, ECP valid and invalid, BVA min and max

It's in tabular form.Stick to that style

hello all!
can u tell me how do we writetestcases for perfomance,load,And stress?
thanx
nancy

Hello Nancy,

the test case template doesnt have much difference between them, but the mode of input values changes.

Under the Performence , 4 concepts should be covered mainly :

1) scalability Testing : To check whether your application allows customer expected load ( no. of users ) or not ?
2) Load Testing : Execute our application under pre-determined level of Resources and Continuous load is called Load testing.
3)Stress testing: -> Execution of our application under predetermined level of Resources and maximum Load is called stress testing.
During this test, testing team estimates Peak load of our application or product.
4)Volume testing : Execution of our application under huge amounts of resources to findout positive movements in performance is called Volume testing.

JUst check it out, how the inputs need to go for all these tests.

Hai,
There is no different format for writing Test cases different type of testing. Only Objective of Testing will be different accordingly the Test Description, input values and Expected results will be changed.

Hai,

Every Test case format will have common fields i.e Testcase Id, Test case name(title),Testtype(Positive/negative), Priority, Module, Functionality, Precondition, Testcase description, Expected result, Actual Result, Remarks, Author, Assigned to etc. Only Objective of testing will be different. That's all

Hi sitnarcha,

Am new member to this forum,i went through your discussions on Test cases and I appreciate your interesting discussions.when i read about on test case document format you mentioned Input Object name as

ECP valid and invalid, BVA min and max

What does this stands for ? Can u explain this?

Thanks and Regards,
Sridevi

ECP - Equivalence Class Partitioning
BVA - Boundary Value Analysis

hi

Test case templates,It may differ company to company.
mostly are using tabular form,it conatins test case id,tiltle,description,excepted result,actual result status(pass/fail)and comments.
In test case format some more fileds are there but many companies are useing only these fileds.

Kishore...

Hi
Do u want test case template or you want test cases for log in details.If you really looking for test case template....
It consists of
Test case id
Test case tiltle,or URL or path for each test case.(In our company we are using this)
Test case desciption,
Preconditon
excepted result
Actual result
status(pass/fail)
and comments.


regrds
Asha

The four basic elements for building a test case are:
1) Input
2) Test Condition
3) System Behaviour
4) Expected Results

You may want to reference the requirement if you are not using a traceability matrix.

The templete differs from company to company. The formate which we use in our company is

Test case id
Test case name
Features to be tested
Test Suite id
Priority
Step no
Description
Expected Result
Actual Result
Result(pass/fail)
defect id
coments

Hi, pfa format for writting test cases. Yes it is very true that it changes company to company but more or less fields do not change. Project name: application prepared by: doc. Version no.: type of testing: functional creation dates: reviewed by: submitted to: sr. No. Test case id test case description expected result actual result test cycle execution date build version result type: +ve, -ve. Defect id use case id if you have still any probem please let me know. Regards, ajay shembekar. Secoe regards, ajay shembekar.

hi!here is my first test case for login screen,i have tried for both positive and negative test cases.All the best!

Hey...
can u please let me know how to post the quirres in this site.
as i am very much new to this site i was not able to find the way to post the querry...

Thanks.

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

Sr no

test case id

test scenario id (1 scenario can have many test cases)

build or version number

test case description

test data for test case

priority

severity

steps

expected result

actual result

status

remark