[Webtest] possible renaming/refactoring

[Paul King]

Dierk Koenig wrote:
> Hi Paul,
> 
> Yes, names are a little bit confusing here.
> 
> Actually, I thought of a renaming such that
> <testSpec ...
> could be
> <webtest ...
> (and having both mappings in the taskdef for backward compatibility).
> 
> Your suggested renamings are ok for me. Thanks for asking.
> 
> I even feel that TestSpec could be changed to a more expressive name.
> What is a TestSpec about:
> - holding configuration and steps
> - open a user session
> - stop executing further steps, when a step fails

Well, if we are going to rename testSpec to webtest, then perhaps I 
should rename WebTest -> WebTestSpec. etc.

That would get rid of the current junit conflicting name but leave 
either testSpec or webtest as sensible ant task names. (And we can 
rename later or not.)

Anyone not happy with this?

The naming is interesting. The ant purists prefer to think of every ant 
build file as a (declarative) build specification not a build script. I 
had always presumed the original authors of webtest had that in mind 
when they chose testSpec.

Cheers, Paul.

>>I would like to suggest a possible renaming/refactoring of a small 
>>handful of classes. It will make no functional change to the codebase. 
>>What do others think?
>>
>>Rename engine.WebTest -> engine.TestSpec
>>Move/rename self.WebTestTest -> engine.TestSpecTest
>>Rename ant.TestSpecificationTask -> ant.TestSpecTask
>>Rename ant.TestSpecificationTaskTest -> ant.TestSpecTaskTest
>>
>>This will remove the WebTest name which is confusing given the
>>JUnit naming conventions and also align the name with the testSpec ant 
>>task which is really just a "wrapper" for the test specification.