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.

In our Project we have a Test case based on Rational Test Manager (RUP Process).

This test case includes, Description, Preconditions, Steps and expected results for each step and finally a notes section.

I feel having expected results for each step is an over kill in writing a test case and includes lot of redundant steps.

What are the test case templates that everyone else use?

Would this differ for Web, Desktop and Mobile?

share|improve this question

3 Answers 3

I've used Excel for this in the past, it's cell limits were one way to enforce terse descriptions and notes so the cases did not get too big. It allowed us to make one worksheet with the cases and pull them into other sheets for scenarios so we could test the steps in different conditions. It was a little bit to set up but once we learned the system it was fairly easy to do, it also allowed us to summarize results within the Excel document and then roll up the summaries into a higher level document that covered all of the case; the company liked Excel so we used what they wanted.

Expected results we usually kept small when we implemented this, the idea was to only know enough to verify the case, not write down everything about it. Although as Todd says, if you don't find the information pertinent don't add it.

share|improve this answer

In Expected Results I also put any graphical updates the product did to the screen (font color change, etc.)

Whether it's "Notes" or somewhere else I put the reasoning behind the logic. As Ralph van Roosmalen writes in his blog http://softwaredevelopmentisfun.blogspot.com/2011/05/things-tester-can-learn-from-programmer.html:

"A good programmer writes why-do-we-do-this comments. For example in the above code, he describes why a should be less than 1 and why he raises an exception. As tester always try to write why-do-we-do-this comments, in your test scripts and in your automated test scripts. How you test, that is clear, describe why you are testing the software."

share|improve this answer

I'm currently using Quality Center for test case management, and it has a similar structure. I've found that in the expected result section for each step is a good place to write down some items that you would look for outside of the basic 'action completes without error'.

You could mention a few points of other questions to ask while the application is in that state. I think that it is a good template for any platform, but I also don't have a problem with leaving an 'expected result' step blank if I don't believe it would have much value.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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