Answer / meenakshi

Hi,

in our company we follow test case format as:

1. Test case ID
2. Bug Id
3. Status
4. Priority
5. Severity
6. Title
7. Steps to Perform
8. Expected Results
9. Actual Result
10. Comments

if i am wrong pl. tell me

Answer / rao

All most all the companies are following IEEE Standard
format for their different documents during Test life cycle.

Document Standard
--------- ---------
Testcase IEEE 829
TestPlan IEEE 829

But none of the companies are follwing the complete formate
of the Tesecase or TestPlan.Simply they are customizing the
format as per thier needs.

In our company we are follwing below format.

1.Testcase ID
2.Priority
3.Type of TC(+ve,-ve,etc...)
4.Description of the testcase
5.Steps to execute
6.Expected result
7.Pass/Fail criteria
8.Bug Number
9.Executor

Answer / madhu

Testcase format is :
Testcase ID:
Testcase Name:
Test case summary:
Preconditions:
Steps:
Actual result:
Expected result:
Postconditions:

Answer / raj.thakur21

Ofcourse, their are some IEEE std's for testcases,
testplans.

1)Some companies follows,can manage.

2)But it's impossible for small scale companies to follow
them.So they have their own std's.

If you compare them, they are almost same with little
modification...

So, you can talk about the Format's you have studied during
college day's or what you had in you previous organization.

Answer / dilsha

Req no,
Testcase Id,
test case description,
expected output,
actual output,
result(pass/fail),
seviority,
priority.

Answer / uma

1. Test Case name
2. Test Case ID.
3. Test Use case.
4. Test Pre-conditions.
5. Test Scenario(module).
6. Test input data.
7. Test Description(steps).
8. Manual/Automated.
9. Expected Results.
10. Actual Results.
11. Results.
12. Tester name.
13. Remarks.

Answer / aparna

1.Test_ID
2.Module
3.Sub Category of module
4.Check Items
5.Test Description
6.Test Step
7.Expected Result
8.Actual Result
9.Status
10.Comment

Answer / madhavi

SNO
DESCRIPTION(verify +ve and _ve statements)
INPUT DATA values(max, min if u go for bva)
ACTION means mouse click or click on tab
EXPECTED DATA
ACTUAL DATA
RESULTS
TEST CASEID

Answer / rao

Meenakshi,

Are the following details required in Testcase format?

I dont think so.....Of course bug ID is o.k,but rest of the
fields are not required..because these fields will make
your testcase too longer..


3. Status
4. Priority
5. Severity

Answer / kalyan

hi to all,


In our company we are following format

1.Testcase ID
2.Type of Testcase
3.Testcase Description
4.Expected Results
5.Status

who will collect requirements from client

7 Answers  

how to do cookies testing in realtime through manual testing? pls give some realtime example?

0 Answers  

What is reference matrix or tracability matrix?

9 Answers   TCS,

Difference between re testing and regression testing, smoke and sanity testing

9 Answers   Mphasis, Wipro,

Requirement is given : 1) The Login screen should require with 2 fields "Login" & "Password" 2) After successful login Success Message will display. 3) For Invalid login Error Message will display. 4) "Login" & "Password" both fields are case insensitive. 5) The Application should be Dialog application. What are the test cases for above requirements?

4 Answers  

any one plz send me test cases on fan,pen,glass,cell phone,mouse and printingpage

1 Answers   SQS,

what is crud testing ?

1 Answers   Crea,

While Testing the Web application & Desktop Application What Difference did u find ? Tell me in details.

1 Answers  

What r the Macros?

1 Answers  

3. How would u test and automate Windows Auto-Update featur

1 Answers  

what are the exact testing types you involved when testing the webapplication testing and clent server application testing?have u find differene interms of testig?

3 Answers   HCL,

What is smoke testing and when it wil be done?

7 Answers