Hi Brett and all interested in seleniumXml,
As you may have seen, I've introduced last week (rev. 901704) the
ability to take screenshots from a selenium test. This is working fine,
but only on a trigger.The next move would be to take screenshots on an
error.
If anyone has clues to make it h
Erwan,
That sounds great. When you say it works "but only on a trigger" do you
mean you have to make an explicit call like "getScreenShot()"?
It would be a nice feature to get a screen shot on an error as this could be
part of an automated build. This also brings up the whole logging mechanism
Le 25/01/2010 18:11, Brett Palmer a écrit :
Erwan,
That sounds great. When you say it works "but only on a trigger" do you
mean you have to make an explicit call like "getScreenShot()"?
You have to add this command in your seleniumXml script :
captureEntirePageScreenshot
And then it took a s
Let me take a look at your test. It doesn't seem like it would be hard to
add and a good feature. I'll keep you posted on what I find.
Thanks for the good feedback.
Brett
On Mon, Jan 25, 2010 at 10:20 AM, Erwan de FERRIERES <
erwan.de-ferrie...@nereide.biz> wrote:
>
>
> Le 25/01/2010 18:11,
Erwan,
When you use the captureEntirePageScreenshot in your test what is the final
outcome? In other words, does it create a new named
CommEventCreateOpportunity in the directory the test is run. I'm asking
because that's what the Selenium RC API looks like it does.
Brett
On Mon, Jan 25, 2
Brett,
I wanted this to be a sort of prefix for the screenshot name as it is
not automated. Then, in the java code, there is a timestamp added, to be
sure that we have a unique name.
The image is saved in runtime, but this can be changed in the
seleniumXml.properties file. I didn't think of sa
Brett,
I have started some development, the problem was using a
DefaultSelenium, instead of a HttpCommandProcessor.
Changing the class will pilot the selenium server via Http instead of
the default method. Moreover, we have now a result, which can be processed.
I had to change the manner to call
Sounds good. I'm looking forward to seeing it in the trunk when its
available.
Brett
On Thu, Jan 28, 2010 at 2:18 PM, Erwan de FERRIERES <
erwan.de-ferrie...@nereide.biz> wrote:
> Brett,
> I have started some development, the problem was using a DefaultSelenium,
> instead of a HttpCommandProces
Hi Brett,
Saddly I haven't enough time at the moment to continue on the
seleniumXml migration to HttpComandProcessor. I have created a JIRA
issue with what I have already done, if you want to contine you are very
welcome !
https://issues.apache.org/jira/browse/OFBIZ-3438
Cheers,
Le 29/01/2
