Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
Do you agree to make regression testing with the testttol BEFORE you
(the developer) give your work to the QA to get CWSes faster integrated?
You won't have to maintain the testing code neither do you have to learn
the script language or debugging the test code....
Hmm? Do you suggest that I, as the developer, just start the test, and
in case something goes wrong you, as the QA person, are responsible for
finding out *what* goes wrong, and stripping down the test case to a
short reproducible one? If so, what would we gain? If not, then I don't
understand what you say.
bingo!
QA =! Test Automator
Joerg is saying that we want to create a test framework where you can be
sure in 99% that the tests will be okay if you have not introduced a
regression.
If you fix e.g. a dialog in Tools / Options and there a test fails you
can ring up the test automator that you would introduce a defect if
nobody will change also the test case.
If a defect is detected which is not from your changes you also have to
inform a test automator that he has to fix the buggy test code.
But, we have these tests already and they run automatically and they are
reporting 0 defects already if the application is fine - see OOF MASTER:
It is using fully the whole category 1. test cases and the version is
nearly tested fully automated. Nobody started here an installation!
Nobody started a testtool! It's running on it's own and the result is
'determenstic'.
THE DIFFERENCE: THEY (the test automators) DO IT IN THE MASTER WORKSPACE
and Joerg Jahnke saying: "Do it in the CWS and introduce only regression
free and defect free test code from a CWS into a MWS and we will have
more fun." Nothing more.
The benefit:
- Creating CWSes on approved software and test code
- The time of CWSes in QA will be down because the tests will approve
that the KNOWN functionality is OK and the QA engineer can work
to verify the issues/new functionaility
- new features will be introduced with automated test code changes to
the existing test code and maybe also new functional tests will be
written in-time
- .... see Joerg's Wiki page
We do not change the testtool, not the method, nit the collection of
tests (okay, we use less on every CWS to be sure that we are able to
manage them) not your workflow, we just change the time when we start
such tests.
Cu,
Jogi
http://qa.openoffice.org/qatesttool
http://wiki.services.openoffice.org/wiki/User:Jsi
--
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]
