Hi Jogi,
is there a way to have the meeting one or better two hours earlier?
We're trying to form a TT team in Beijing. At the current dating nobody
from here will be able to join now and for the future, because we go
home by shuttle buses, and people have to leave latest at 11:15 MESZ. I
also recommend to fix dates in UTC.
Best regards from Beijing
Peter
Joerg Sievers wrote:
Moin[1] testers!
Most of the testers here in the mailing list may be know me and what I
do for OOo at Sun Microsystems but sometimes it makes sense to re-write
it after so many years.... and I think the time is right...
I work as a software test automator for Sun since 10 years next february
and I technically lead the project inside Sun since some years. Also I
am the CWS (=child workspace) gatekeeper which is a monitoring role.
I have to keep an eye on some CWS that the policies and rules have been
followed. If not I have to reject the CWS back to the QA and developers.
Also I work with colleagues from development and user experience on
software specification related issues.
The Sun automated GUI testing team (aka "Automation") meets in a
14-days-intervall to discuss project related issues. To get more
transparency for you we decided to release this outcome of our last
meeting in this mailing list. See the following points we discussed and
agreed to get you involved in what we are doing:
1. Communication transparency
Helge in his role as OOo Automation team lead made a proposal to start a
better communication to the community of what the Sun's Automation team
is doing. We need a more transparent way of communication and so we
agreed to use the IRC more frequently to get/stay in contact with the
community members who are interested in software test automation. This
is a first step and will probably replace our weekly face-to-face
meetings on monday.
First meeting will be next monday, 11h MESZ, #qa.openoffice.org @
irc.freenode.net
Participate if you're interested in QA automation......
2. Extension testing
We talked yesterday about introducing the automated GUI test cases in
CVS for extensions which will be done in a seperate directory called
qa/qatesttool/extensions
so we won't mix it with the "basic office test-environment" we use to
test ports or releases. Under this new directory you will find also
.../win (=window declaration files) and .../sid (=slot id declaration)
which have to added by each test (*.bas) which want to test the extension.
If you have any questions, suggestions, concerns or want also to join
our work, let us know next monday or here in the mailing list.
Cu,
Jogi
http://qa.openoffice.org/qatesttool
http://wiki.services.openoffice.org/wiki/User:Jsi
[1] 'Moin' is not German, it's 'low German' (better: plattdüütsch)
http://en.wikipedia.org/wiki/Low_German and can be used all day
and night to say "Hej" (Sweden) or "Hi" (you all know) :-)
--
Peter Junge
Program Manager and Senior Engineer Open Source Technology
北京红旗中文贰仟软件技术有限公司
Beijing Redflag Chinese 2000 Software Co., Ltd.
Building No.2, Block A, Huilongsen, 18 Xihuan South Street
Beijing Economic-Technological Development Area
Beijing, P.R.China
Tel：+86-10-51570010 ext.6212
http://www.ch2000.com.cn
http://www.ch2000.com.cn/english/index.htm
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
