Hi!
Beginning with the mileston DEV300m22 the modul "testautomation" will be
part of the CWS process [1] and you will be able to add it to a CWS.
The test script writers [2] will fix their test cases in CWSes like the
software engineers doing it all the time.
Why?
The QA Automation hosted their own versioning system since +10 years and
made the same things Rlease Engineering (RE) is doing for software code.
In the last time it got harder to have software- and test code in sync
and there were only historical reasons why the software code has been
managed on its own.
What?
What will be changed in the software engineers workflow? It will be
possible to change the test script code at the same time as the software
code will be changed. It is possible that 'long running' CWS'es can holf
their own test case repository which will be added with the integration
of the CWS.
When?
When should the modul 'testautomation' be added to a CWS? Everytime you
change user interaction behaviour (focus, windows handling, ...) or the
UI (user interface; dialogs, buttons, windows, ...) and it would be
great to give the test script writers the chance to adopt their test
cases to the new behaviour.
Advantages?
- A CWS always has a matching set of VCL TestTool test cases
- Test Automators have no overlayed/additional release engineering
work to do anymore
- testers and software developers can write issues if a test case
has to be adopted to a new behaviour
Disadvantages?
- Test Automators have to use a CWS to fix their test cases (it
was easier to check them in top level:)
Next?
QUASTe [3], VCL TestTool control file (.testtoolrc) have to be
enhanced/modified to the new environment. We will also try to create a
CWS matching TestTool control file in the build process to reduce the
manual work on settings etc.
Links:
[1] "Test Code on The Way Into The Childworkspace Process"
http://blogs.sun.com/GullFOSS/entry/test_code_on_it_s
[2] Responsibnle Test Automators
http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationResp.html
[3] Quality Assurance Statuspage
http://wiki.services.openoffice.org/wiki/QUASTe
Contact:
mailto:[EMAIL PROTECTED]
Thanks!
Many thanks to Joerg Jahnke for supporting the idea in Release
Engineering and Development, Marc Neumann who implemented the process in
the test automation group, Helge Delfs and Thorsten Bosbach who are
adopting the reporting part of the TestTool environment - and the test
automators [1] from Sun who changed their tests and -cases to a agreed
new structure [1] in a real short time.
Yours,
Joerg (Jogi) Sievers
--
Sun Microsystems GmbH Joerg Sievers
Nagelsweg 55 Quality Assurance Engineer
20097 Hamburg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
