Take the 2-minute tour ×
Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It's 100% free, no registration required.

I would like to know what would be the best format for writing test cases The current format which I am using is as follows: It includes:

  • Objective
  • Input
  • pre conditions
  • process
  • expected result
  • actual result

Please suggest if its ok or can it be improved or please share any other format.

share|improve this question

closed as primarily opinion-based by Kate Paulk, Suchit Parikh, testerab Feb 2 at 15:47

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
I think it would be beneficial if we have more information about your testing activity. What is the purpose of your testing? –  SayusiAndo Jan 23 at 9:29
3  
There is no single best format. This is very specific to your area of testing, your organisational needs, your tooling support and so on. –  desolat Jan 23 at 20:31
    
Agreed. This is just too broad. @ashu, if you can provide some context then people may be able to help more. –  testerab Feb 2 at 15:47
add comment

1 Answer 1

up vote 0 down vote accepted

Test case needs to be linked to User Story/Requirement ID.Linking to Use Case/Scenario is optional.

Usual columns that we used in earlier projects are

User Story ID/Description Test Scenario[optional] Test Case name [starts as validate that....] Pre-requisites Steps Expected results Test Case priority[High/Medium/Low] Test Data[Optional] Post Condition[Optional]

Actual Results[output] form part of Test Execution template. Some more columns of Test Execution Template are; 1.Test cases result [Pass/Fail/Blocked/Out of Scope/Inconclusive] 2.Tester name 3.Defect ID 4.Date of Testing

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.