[
http://jira.codehaus.org/browse/MSELENIUM-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182681#action_182681
]
Jason R Briggs commented on MSELENIUM-53:
-----------------------------------------
Forgot to mention, I'm triggering the test as follows:
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>selenium-maven-plugin</artifactId>
<configuration>
<browser>*firefox</browser>
<startURL>http://localhost:8080/</startURL>
<port>5555</port>
</configuration>
<executions>
<execution>
<id>mytest</id>
<phase>test</phase>
<goals>
<goal>selenese</goal>
</goals>
<configuration>
<suite>target/classes/mytest-suite.html</suite>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
> selenium variables don't apear to work when run from maven
> ----------------------------------------------------------
>
> Key: MSELENIUM-53
> URL: http://jira.codehaus.org/browse/MSELENIUM-53
> Project: Maven 2.x Selenium Plugin
> Issue Type: Bug
> Components: selenese
> Reporter: Jason R Briggs
> Assignee: Jason Dillon
>
> I've run into a problem with a test that works fine from the browser, but
> fails when run from maven. In a setup test, I use storeText to set some
> variables. For example:
> <tr>
> <td>store</td>
> <td>mytest.log</td>
> <td>logname</td>
> </tr>
> Later on I use the variables in another test:
> <tr>
> <td>type</td>
> <td>logname</td>
> <td>${logname}</td>
> </tr>
> If I run this within the browser, the variable value is used correctly. If I
> run from maven, the value is typed as ${logname} (i.e. not parsed at all).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
