when doing test cases ...

Hi Ilyse,

(all I write here is no strict rule, but an advice. As we
all -  well, 
most of us - are volunteers for OOo, it is up to everybody
how much time 
he spends working on OOo.)

Ilyse Kazar schrieb:
> ... I notice that there are bugs (iz #'s) associated
with each of the 
> test cases I'm going through today (for base, m180).
> 
> Am  I supposed to visit each bug# in iz to be testing
each issue 
> individually?

In general, it would be enough to follow the test case and
see, if *you* 
find errors. But the issues are a good advice, as they show
the errors, 
that other testers found.
At least, once you found an error, you should look at the
issues. Maybe 
the error is already reported.

> 
> for example, for one test the instructions are to
display the contextual 
> menu for aligning data in a field, and make a
formatting change choice. 
> So I chose "center" and the test passed.
But when I happened to click on 
> one of the iz #s I see that the bug was for
"justified" and "filled" (I 
> have no idea what the difference is!, but that's
besides the point)

Oh, I know this issue  In fact
this is a bug. But 99.9% of our users 
would not use this feature.

> 
> so, IOW, is following the instructions in the TCM
enough?

yes.

> 
> or, am I supposed to visit each of the iz#'s to see
SPECIFICALLY what to 
> test?

The Issues are the results of previous tests, not the
instructions for 
your test. But as said before, they may give hints.


Let me give an example, what some members of the german
qa-team do.
First the test is done following the description.
Afterwards, the issues 
are checked, if they still exist. Then a comment is left in
the comment 
field (e.g. Issue xyz is for japanese localizations only).

This is more work for the tester, but very helpful for the
manager (me 
in this case). But as said, we are all volunteers and I
cannot command 
you to do more work, just to reduce mine (But I'd be very
thankfull for it).


André

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org