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 < [email protected]> wrote: > 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 the way of executing a command which now > using doCommand(String command, String[] args), so all the methods will be > modified. The visible part remains unchanged. > This permits me now to log a successful command, and then (just starting) > making screenshots. > > You will maybe find the first implementation tomorrow, if hopefully I find > time to push it to the trunk. > > Cheers, > > > Le 26/01/2010 22:19, Erwan de FERRIERES a écrit : > > 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 saving it to the same >> folder as the test. >> >> HTH, >> >> Le 26/01/2010 19:25, Brett Palmer a écrit : >> >>> 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. >>> >>> <captureEntirePageScreenshot value="CommEventCreateOpportunity"/> >>> >>> >>> Brett >>> >>> On Mon, Jan 25, 2010 at 10:20 AM, Erwan de FERRIERES< >>> [email protected]> wrote: >>> >>> >>>> >>>> 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 screenshot which is saved in runtime. >>>> If you look at the CommEventCreateOpportunity_testsuite.xml, you will >>>> see >>>> the command. >>>> >>>> The problem is I don't know how to handle seleniumXml errors, and then >>>> trigger a screenshot... >>>> >>>> >>>> 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 >>>>> in SeleniumXml. Since it runs outside of the container it doesn't have >>>>> access to the logging features of ofbiz. This would have to be setup >>>>> separately. >>>>> >>>>> >>>>> ../.. >>>>> >>>> >>>> >>>> -- >>>> Erwan de FERRIERES >>>> www.nereide.biz >>>> >>>> >>> >> > -- > Erwan de FERRIERES > www.nereide.biz >
