Bernd Eilers schrieb:
Hi there!
By request from the QA-Automation-Team the Automation-CAT0 tests in
EIS are now mandatory. They must always be started on Windows and
Linux and their state should be green before the CWS gets approved by
QA or nominated.
the wording is a bit unfortunate, the release team still accepts cws
with no CAT0 test passed. The release team supports the efforts of the
QA automation team that CAT0 test are required for those cws, where
changes requires the adoption of the test suite and regressions can be
detected. For changes outside this scope (also described in Mathias blog
<http://blogs.sun.com/GullFOSS/entry/about_contributing> other ways of
approving the cws might be more appropriate than the CAT0 tests.
so please make use of the automated tests wherever there are useful, but
please also use tools like the buildbots, code or peer review etc In the
end the QA representative is responsible independent from how QA
actually has been done.
Martin
.
If those tests have not been run yet and other tests did deliver an OK
status or where not mandatory to be execute the CWS will get the
incomplete overall status.
If you rerun individual automation tests make sure to review the
result in QUASTE afterwards, QUASTE will then deliver the new
calculated result status over all tests to EIS.
Kind Regards,
Bernd Eilers
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
