Hi Rüdiger,
Rüdiger Timm schrieb:
Ause just informed me about another solution that might remove the
need to have the test run on every CWS i.e. we wouldn't need to have
the tests mandatory. His idea is to run the tests on the Master
Workspace prior to announcing the CWS as "ready for CWS use". If a
test fails then this would result in a P1 issue that has to be fixed
before the MWS can be used by everyone. Very similar to how we handle
it for the Smoketest on the MWS nowadays.
...
Does that make sense?
Are you really asking for my opinion? ;-)
From my point of view this does not make sense at all. It is never a
good idea to shift testing from childworkspaces to master builds. We
would spend quite some time with P1 issues which should have been
detected on the responsible CWS beforehand.
If we would expect to encounter regressions quite often then this model
is indeed not worth thinking about. So far I do agree. But what if we
could expect such regression only every 2nd or 3rd milestone build?
Isn't it an improvement to the current state if we find such problems
early on the MWS and if we can offer developers a means to at least
optionally do more regression testing?
This whole discussion is about testing CWSs before integration to prevent regressions instead of
detection regressions afterwards, isn't it?
Not necessarily. Indeed the approach mentioned in the Wiki page is to do
tests on every CWS to prevent regressions to get into the MWS in the
first place. Just as we have it for the Smoketest nowadays. But if many
people see new mandatory tests as an unnecessary hurdle for developers,
then we should at least think about other ways to do more regression
testing. Even if my proposed way above should not be a good one...
BTW, what you describe is quite different to current Smoketest handling
in that doing Smoketest is mandatory on every CWS.
That's why I wrote "Very similar to how we handle it for the Smoketest
_on the MWS_ nowadays".
Rüdiger
Regards,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
