Hi Stephan,
Stephan Bergmann schrieb:
On 10/10/08 15:02, Thorsten Ziehm wrote:
Here are some misunderstandings. QA isn't QA in software testing.
The developer talked often about code quality and he needs tools to
run, to check if his code break anything. The GUI testing with VCL
TestTool isn't such a tooling. The VCL TestTool check functionality
as a user in an installed Office. These tests need an installed
office and the TestTool as external testing tool. This cannot run
in the development environment and should be started by 'make'.
I know that developers want to start it from the command line. But
therefore you need unit tests, complex tests and perhaps API tests.
These tests work on code base. The test with VCL TestTool are later
in the QA process and it has to done out of the developer environment.
So 'make' isn't a solution for such kind of test scripts.
I have to disagree. Running VCL TestTool tests (in addition to other
tests, like unit tests and complex tests and whatnot tests) from within
a build environment could indeed be useful (e.g., to integrate them in
automatic builds, as Thorsten Behrens already pointed out in a recent
mail). That doing so should technically be possible is demonstrated by
module smoketestoo_native. What probably is a prerequisite for all
this, though, is that the VCL TestTool has to produce stable,
reproducible, unambiguous results (which, as my experience in the past
has been, it does not always do).
You are right in that point, that the developer needs a tool, which show
him easily if his code changes work fine. In first step this could be
done in development environment. But the final approval of the changes
must be outside of the development environment.
Why?
1. You cannot identify dependencies which are working in development
environment only. If you do not have such dependencies (perhaps link
to special libs or something else) the code could break and show an
error in the implementation (tests).
2. Code isn't submitted into the code management system, but it is in
the development environment of the developer. The problem can be
found only, when the code is build and executed outside this
environment.
Both scenarios aren't so rarely.
But as I wrote above. This tooling should also work in the development
environment. But it shouldn't run in this environment only.
We will take care of such requirement.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
