second try:
if using testtool it will most likely get mixed up even more with the
CVS module testtools (note the s at the end and thanks to whoever picked
this name!)
on the other hand automation is not good because it does not relate to
testtool very well, so I suggest VCLTestTool or vcl-testtool if
lowercase is mandatory which is also the name of the tool.
cheers
Gregor
Stefan Taxhet wrote:
Hi,
so, should we stick with the subcomponent name "automation" (to match
the CVS module name) or would you prefer "testtool"?
Greetings
Stefan
Thorsten Ziehm wrote:
Hi Stefan and all,
It would be a fine gesture of the QA project to welcome a component
with such a close relation to QA and Gregor as owner. I guess 10 out
of 10 people would look in QA if they have a problem with the
testtool...
I do not have a problem with 'TestTool' as sub-component in the QA
component. I wanted to point out only, that until now in this
component things are handled which are hosted by QA members. I
welcome the
TestTool project in QA component.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
