Hi,
it's very good if developers talk about code areas where they changed
things but QA should assure what files have been modified. When speaking
of a child workspace (CWS) then EIS http://eis.services.openoffice.org
is a good tool to identify the source code modules involved. Experienced
QA engineers know their developer's habits and they know where typical
errors are done.
As Thorsten Ziehm already answered within this thread it's nearly
impossible to do a full QA cycle (full regression test) for each issue
that has been fixed. QA should concentrate on testing the areas that
have been changed.
eg.
If a developer changes something within the OLE sources then it's a
defined action to do load/save automation test cases within all
applications.
It's also useful to define default test cases that need to be run every
time a CWS is going to be approved. That's the way Sun's Hamburg QA team
is managing it.
btw. using the VCL testtool is not everything when regarding automated
QA. Writing and running API tests and doing manual QA and testing should
be done as well.
Kind regards, Joost
Zhu Lihua wrote:
Hi,
If a developer modified some core code to fix a bug, it might influence several parts of the software. Will developer tell us tester which parts of the software need a focused testing? or should we start a complete regression testing to find out the new bugs?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
