Hi Marc,
Many thanks for hinting me on your contributions, this sounds very
much what I was looking for. Hopefully your patch (or at least the
concept of grouping tests) gets accepted and into the webtest plug-in,
its very elegant then to support testing the different environment
scenarios.
Thanks for your help,
Niko
Am 03.04.2008 um 13:40 schrieb [EMAIL PROTECTED]:
Hi Niko,
> Another question is (for may be including in the documentation),
how to
> define more than one test suites (beside the standard
> webtest/tests/TestSuite.groovy) and how to invoke them.
just search for "Any public interest in separating tests by
groups?" in the "grails user" mailing list.
There is a patch which may solve your problem.
I hope, it will be applied to a coming grails version.
Best regards
Marc Pompl
"Niko Schmuck" <[EMAIL PROTECTED]>
Gesendet von: [EMAIL PROTECTED]
03.04.2008 12:20
Bitte antworten an
[email protected]
An
Dierk König <[EMAIL PROTECTED]>
Kopie
[email protected]
Thema
RE: [Webtest] Canoo + Grails
Hi Dierk, and all,
webtest embedded into the grails development process is absolutely
great
to use. Thanks very much for your groovy-fication!
The only thing I wonder is, how one would get out the webtest step
properties into the groovy script for further processing. I am sure
there
is a groovy way to interact between webtest properties and groovy
variables, but cannot find it.
Another question is (for may be including in the documentation), how
to
define more than one test suites (beside the standard
webtest/tests/TestSuite.groovy) and how to invoke them.
Cheers,
Niko
On Wed, April 2, 2008 4:05 pm, Dierk König wrote:
> Hi David,
>
> The documentation of general Groovy usage with WebTest is
> under http://webtest.canoo.com/webtest/manual/groovyTesting.html
> which in turns points to
> http://grails.codehaus.org/Functional+Testing
> for the Grais specifics.
>
> Could you give a list of topics that are not covered by these
> pages?
>
> much appreciated
> Dierk
>
> | -----Original Message-----
> | From: [EMAIL PROTECTED]
> | [mailto:[EMAIL PROTECTED] On Behalf Of
> | [EMAIL PROTECTED]
> | Sent: Mittwoch, 2. April 2008 14:39
> | To: [EMAIL PROTECTED]
> | Subject: Re: [Webtest] Canoo + Grails
> |
> |
> | Marc, thank you for the response - got it working
> | beautifully. I've noticed that while the Canoo documentation
> | is fairly thorough with the exception of the Grails portion
> | and even Grails skips around the functional testing portion as
well.
> |
> | 1. Are there any sites or guides that give a good overview of
> | custom functional testing for Webtests in Grails?
> | 2. This is just to confirm something: the XML patterns for
> | specifying the tests are not available with the Grails plugin
> | - correct? If I create my tests within the XML using
> | definitions and entity replacements - I would then need to
> | change those tests to use the method described below?
> |
> |
> |
> |
> | Marc Guillemot <[EMAIL PROTECTED]>
> | Sent by: [EMAIL PROTECTED]
> |
> | 04/02/2008 05:34 AM
> | Please respond to
> | [EMAIL PROTECTED]
> |
> | To
> | [EMAIL PROTECTED]
> | cc
> | Subject
> | Re: [Webtest] Canoo + Grails
> |
> |
> |
> |
> |
> |
> | Hi,
> |
> | the mailing list is fully correct.
> |
> | In Grails you can just extract common step sequences in
> | utility methods like
> |
> | // Utility.groovy
> | class Utility
> | {
> | doLogin(ant)
> | {
> | ant.group(description: 'perform login')
> | {
> | invoke "http://...";
> | }
> | }
> | }
> |
> | // SomeTest.groovy
> | import static Utility.*
> | ...
> | webtest('some test')
> | {
> | doLogin(ant)
> | ...
> | }
> |
> | (my mailer still doesn't compile, syntax error are possible ;-))
> |
> | When you're utility methods are located directly in your
> | class (or in some parent class), you don't need to pass ant
> | as parameter.
> |
> | Cheers,
> | Marc.
> | --
> | Blog: http://mguillem.wordpress.com
> |
> |
> | [EMAIL PROTECTED] wrote:
> | >
> | > I have Grails running with Canoo Webtest plugin installed.
> | Life is great
> | > except my tests feel very repetitive. When I used Canoo Webtests
> | > stand-alone, I used a lot of in-line parsing with the entity
and put
> | > common tests in areas available to all. I know a lot of
> | work was going
> | > on in the background to make those pieces available. Is
> | there a similar
> | > process for the plugin for Grails? Is there a different way
> | to include
> | > common tests?
> | >
> | > This may not the best forum to address the question, if
> | it's not please
> | > let me know. There's not a whole lot of information that
> | discusses this
> | > that i could find. I would love to be proven wrong -
> | especially if you
> | > have the documentation available :)
