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

if a problem on client side is restarting of PC then what are u going to do and say me the methods to solve the problem?

3 Answers   Mantra Group,

why is testing necessary , explain with some examples?

6 Answers   Accenture,

You have been given 2 projects to test, what are the key factors you consider when prioritizing you work load?

1 Answers  

how will you test transfer funds module...explain in detail

0 Answers   Tarang,

how u do database testing

4 Answers   Polaris,

what is difference between Sanity testing and Smoke testing?

15 Answers   IBM,

What is the Driver in Integration Testing..Anybody can explain it.....Thanks in advance.....

3 Answers   Siemens,

Is Anyone attended the manual testing interview with capgemini in recent past. please let me know the type of questions they can ask. Thanks

0 Answers  

Can any one explain the all types of testing in detail with aim of the testing,purpose,Person Doing,entry criteria,exit criteria,Documents required.....its very helpful for me..if possible send it to my mail id varalaruu@gmail.com

0 Answers  

What is the testing that a tester performs at the end of unit testing?

2 Answers  

What is non-compliance testing?

1 Answers  

What is Traceability Matrix? How will you exactly map it and in which stage will you prepare that?

1 Answers   IBM,