Howdy. I was asked to post a message here to kick off a discussion of
test script coordination. I'm volunteering to help with them because a)
it's simple, and b) I'm simple.
I know shell, as you can see from the add-modelines script I just
submitted, and I'm told that StarBASIC is "as easy", and that's what
(some? all?) of the test scripts are written in. So add me to the list
of folks on the "testscripts" team, please.
What I'd like to see is some way to coordinate work surrounding the test
scripts:
* A wiki page with best practices, local custom, etc.
* A status board (what is failing where, and what test scripts are born
bad and need some discipline)
* A list of info about the team of folks on the "test scripts" team (is
this QA?), who is active and who is inactive.
* Pretty graphs and charts. Freenode IRC bot for queries?
* Some statistics. (Maybe use R?)
* A section of bugzilla (or whatever bug tracker we're using) for
[testscript]-ers.
Have fun,
Jesse Adelman
Bold and Busted LLC
San Francisco, CA
http://www.boldandbusted.com/
Context
- [Libreoffice] [testscripts] Guidance and project management · someone
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.