I think the idea is great. I'm facing exactly the issue as I'm trying to
implement continuous delivery. There are few GUI tests using geb, and they
will run on different test environment. And I think a smoke test against
PRODUCTION environment is also useful.
I found a workaround for this issue:
in GebConfig.groovy, we can put our logic directly where baseUrl is
defined. example:
baseUrl =
System.getenv().containsKey('CI')?"http://testenvironmentforCI:9090/appContext":";
http://testenvironmentforCI:9090/appContext";
On Monday, 15 June 2015 17:35:28 UTC+2, dean.delponte wrote:
>
> I'm utilizing the example project at
> https://github.com/geb/geb-example-cucumber-jvm to run Cucumber with Geb.
>
> The baseUrl changes depending on if I'm testing code that's in
> development, staging or production.
>
> What's the recommended way for changing the baseUrl at runtime?
>
> Can a parameter simply be passed in via the command line?
>
> Thanks!
>
> - Dean
>
--
You received this message because you are subscribed to the Google Groups "Geb
User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/geb-user/57f79c53-a8ce-4f27-9df4-c1661435063a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
