Ally's a QA

2007-May-4 - How detail to decribe a test case?

It's a painful work for me to update test cases (the description) after some time. That's because UI is always changing. For example, a test case says "click the Enable button", but once the button has been turned into a checkbox, the case is outdated.

So I think it's a waste of time (and stupid) to describe step by step of a test case.

A test case should only include the testing related things, for example, the input and checkpoints. Never include the details that are not testing related, eg. steps, and UI actions.

Every QA is smart enough to figure out the steps!

2007-May-4 - Untitled Comment

Posted by mferris

you still need to test cases for UI

Permanent Link

2007-May-7 - Depends on who you write them for

Posted by michaeljf

There was already a thread on this in the Functional Testing forum, but it depends on your audience. If your Cases will ONLY EVER be used by people familiar with the product, sure. But if they are used by people seeing it for the first time, you may need some detail in there to get them through it.

Permanent Link

<- Last Page :: Next Page ->