New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fluentlenium requires some config #230
Comments
There are two things. First we should be able to specify the 'browser' we want to use. This should be done using Then, in the case of the main Wisdom build, just writing in the documentation that Firefox must be in the path. |
well, for those cases, i tend to write enforcer rules which message do not leave any confusion to mind ... As an example, to make sure Visual C++ is declared as a variable, I have the following rule
Could it be possible to have a comparable enforcer rule which would check that firefox.exe is on path and, if not, fail the build with the clearest message ? |
Is there a way to check if a program is in path without writing your own rule ? (we can still write one, that's not the issue, just don't want to reinvent the wheel). |
On 17/06/2014 14:18, Clement Escoffier wrote:
In fact, the best way would be to use a beanshell rule ... Nicolas Delsaux |
Can you try to add https://gist.github.com/cescoffier/48b3a48ab1a14c196289 to your pom file ? |
On 17/06/2014 15:41, Clement Escoffier wrote:
Nicolas Delsaux |
Yes it is planned, was just a first attempt (My beanshell skills are let’s say… inexistent). On 17 juin 2014 at 16:14:30, Nicolas Delsaux (notifications@github.com) wrote: On 17/06/2014 15:41, Clement Escoffier wrote:
Nicolas Delsaux |
On 17/06/2014 16:15, Clement Escoffier wrote:
|
Code approved by Mathilde ! Signed-off-by: Clement Escoffier <clement.escoffier@gmail.com>
…efox.exe in my PATH (instead of %FIREFOX_HOME%), the enforcer rule is not satisfied and the build fail - without any output, but this is another issue.
Seems like it do not work if I put specifically the firefox.exe on my path. I have a pull request ready for that. |
Fixes a subpart of #230 : if I put %FIREFOX_HOME%\firefox.exe in my PATH...
It seems a valid firefox is required on path ...
I guess a maven enforcer rule could do the job ...
The text was updated successfully, but these errors were encountered: