Hi Siefried,
I understand that you want to move it out of the normal execution order
of webtest.xml but why don't you want to use webtest.xml for things like
report generation?
Cheers,
Marc.
Siegfried Goeschl a écrit :
Hi Marc,
some functionality is moved out from webtest.xml
+) test setup can be tied to the Maven build life cycle
+) reporting is entirely done with then Maven build life cycle
A bonus of using a M2 plugin is that managing the Canoo WebTest
dependencies is done using Maven
Cheers,
Siegfried Goeschl
Marc Guillemot wrote:
Hi Siegfried,
the question was not concerning the samples but about using
webtest.xml for all the things that have to be done before running the
tests (task definitions for instance) and once the test are run (like
generating reports).
Cheers,
Marc.
Siegfried Goeschl a écrit :
Hi Marc,
I'm pretty much sure Felipe writes about the M2 plugin - ./src/it5
actually runs the "offical" Canoo WebTest samples
Cheers,
Siegfried Goeschl
Marc Guillemot wrote:
Why doesn't the Maven Plugin use WebTest's webtest.xml?
Cheers,
Marc.
[email protected] a écrit :
The missed detail about splitting the tests in several files was the
definition of the webtest taskdef:
<taskdef resource="webtestTaskdefs.properties" />
Including this in the test files I can use an ant file to link to all
the tests:
<project name="Canoo Webtest Sample" basedir="." default="all">
<target name="all">
<ant antfile="pageEmbedderWebTest.xml" />
<ant antfile="pdfWatermarkWebTest.xml" />
</target>
</project>
And the test:
<?xml version="1.0"?>
<!DOCTYPE project SYSTEM "../resources/dtd/Project.dtd">
<project default="test">
<taskdef resource="webtestTaskdefs.properties" />
….
Now it works…
And I can have 1 webtest per page in the project….
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
