Hi André,
You're missing the point here because for bug fixes we have the
developer and a responsible QA representative working on the child
workspace that is used to integrate the bugfix.
No, I'm not missing thiat point - but this is diferent from my point.
The QA rep for a CWS comes into play, when the developer has done his
job (at least this is what is communicated at the wiki).
A QA representative can start earlier (see below)
But the preparation of the CWS (which bugfixes should go in) is unclear
and seems mainly be the task of the developer. I think, QA team can
help a lot here.
This can be checked even before a CWS is set to "Ready for QA":
A bugfix CWS should ideally focus on bugfixes within one separate area
of code. Developers often tend to collect issues that are fixed within
different modules and to put the bugfixes into one CWS. This makes the
QA work a bit harder because in this case you are forced to check
different areas of the functionality within one CWS build. The danger is
that you may overlook regressions within the other modules. In this case
I would ask the developer if he/she could move this one bugfix to
another CWS just to assure a smoother integration after this CWS has
been set to "Approved by QA". Sometimes it's necessary to have different
modules but it's always useful to discuss it with the developer.
The QA representative should check if the target of the issues is
compatible to the target set within the CWS.
The issues within the CWS should be testable.
You can ask the developer about details of what areas have to be
tested/QAed. Unfortunately some patches delivered did not contain any
information about the areas that have changed within the code and in
such cases we got regressions.
I agree here and would see such a focused and commented list as
starting point for some focused bug fixing efforts. I'd really love
to work on something like this - as long as it is somehow within
my experience and developers would join.
Would you like to help Jaqueline with collecting issues regarding "mail
merge" and "numbering" in Writer like we already discussed at the QA
weekend in Essen ?
As said - if we have the commitment from development, that there
will be a joint effort to fix those bugs - yes.
If this works well (and I really expect this), I'd suggest to do this
more often and for other topics as well.
fine :)
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
