May be also write a line about when filling an issue about a bug
found, developers are not connected to the TCM, so you need to
describe all the steps to reproduce the bug and not point them to the
test number, they won't understand what you're talking about.
Kind regards
Sophie
My way of providing this information was to locate it in TCM, i.e. in
the failed entry. There's a text box when everything can be put down -
both the expedcted results from the test designer ("1 - pass, 2 OK, 3 -
not OK ....") with "how / why its not OK" information added at such
points. Assumption of course is, developers would have access to those
test case instances (maybe a URL to them in the issue?). If not, well,
then testers should write in the textbox for their own record PLUS copy
it all into the issue they are opening so that developers would
see/grasp what its all about.
I have been following this same approach for all cases (i.e. including
passes), just the normal / expected due dilligence attitude.
Regards
smo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
