Interested to Buy Any Domain ? << Click Here >> for more details...
which test case format ur company following
- 10 Answers
- 15024 Views
- CTS, Param Software, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
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
| Is This Answer Correct ? | 6 Yes | 0 No |
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
| Is This Answer Correct ? | 5 Yes | 3 No |
Answer / madhu
Testcase format is :
Testcase ID:
Testcase Name:
Test case summary:
Preconditions:
Steps:
Actual result:
Expected result:
Postconditions:
| Is This Answer Correct ? | 2 Yes | 0 No |
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.
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / dilsha
Req no,
Testcase Id,
test case description,
expected output,
actual output,
result(pass/fail),
seviority,
priority.
| Is This Answer Correct ? | 1 Yes | 0 No |
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
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
| Is This Answer Correct ? | 0 Yes | 0 No |
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
| Is This Answer Correct ? | 1 Yes | 2 No |
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
| Is This Answer Correct ? | 0 Yes | 2 No |
what is cmmlevel each and everystage i want to complete details please any one mail me i want to complete details
What is meant by Test Script. Example and Explanation on Test Script?Please Answer
How to do cards Testing? And give sample test cases please? And tell me about vision plus card?
Why most of the software company preferred manual testing even though many automation testing tools are present in the market.
How to prepare web applications use case document.can you send the some sample use case document for web application Project?
What is the type of the testing to check the availability of a website 24 * 7?
6. what is the purpose of using automation tool qtp? and why we are using framework.
Differentiate Defect age and Build interval.
what are the risks and contingencies u had in ur project?
Testing mainly in Verification or Validation ?
What exactly is quality control? Is it similar to quality assurance?
Whenever developer will recieved the defect from the tester,then he will go thru the defect whether it is acceptable or not?for that he will execute that application again,while executing if he did not found any such type of defect(what we are rise the defect above),then he will send that defect to the corresponding tester with status of 'reject',as a tester what we can do?(here writing the reproduce steps and attached screen shots has been done by tester while sending the defect to the developer, no need to send reproduced steps and screen shots again)
Automation Testing 
