[Webtest] possible renaming/refactoring

[Dierk Koenig]

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

I wish my english would be better to find a name for such a beast.

cheers
Mittie

> -----Original Message-----
> From: webtest-admin@lists.canoo.com
> [mailto:webtest-admin@lists.canoo.com]On Behalf Of Paul King
> Sent: Dienstag, 4. Januar 2005 9:05
> To: webtest@gate2.canoo.com
> Subject: [Webtest] possible renaming/refactoring
> 
> 
> 
> 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.
> 
> I am happy to do the work but want other people to be happy with the 
> idea before starting.
> 
> Cheers, Paul.
> 
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest
>