This is me thinking outloud.
We heart webtest as it works very well. I'm integrating it into a 2nd
project at my company. Let me state a few assumptions:
1) We use a dependency management system (e.g. no jars get checked into
cvs/svn)
2) Webtest belongs in same cvs module as project it is testing
a) This allows our continuous build to detect changes with tests
along with source changes
3) We never use bat or sh scripts. Everything works from ant.
4) Our dependency management creates all of our classpaths nice and tidy
like.
That being said.....webtest works great out of the box. Now I'm trying to
actually "integrate" it in with the project to test and it feels a
little....kludgy. Not bad, just kludgy.
I've added all the jars to my ivy repository. Then i've kind of half way
mimicked the default the source tree that comes with the build.zip but made
it fit in my project.
E.g. we have a top level folder called resources. Now it has a
resources/webtest which contains stuff like the xslt transformer.
I guess the point of this is
1) does anyone else use it like this? or am i just picky?
2) maybe a section on the website could be made to house a best practices
integration section? I'm more than willing to write stuff up, I just like
to have input from others...
Thoughts?
--
View this message in context:
http://www.nabble.com/WebTest---integration---best-practices-tp15818597p15818597.html
Sent from the WebTest mailing list archive at Nabble.com.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
