Sorry, I'm a little late on this thread. Is the logging problem related to SeleniumXml or another Selenium sub-probject?
I believe the problem with SeleniumXml is that it run outside of the ofbiz container and doesn't have access to the log4j settings, etc that are available in the ofbiz container. A patch could be added to configure Seleniumxml to use the same log4j settings setup in the framework. Then the errors could be found in the same logs files as the other tests. is this what developers are asking for? Brett On Mon, Dec 6, 2010 at 3:15 PM, BJ Freeman <bjf...@free-man.net> wrote: > thanks for the the clarification. > No problem running tests from build. > the problem is the errors at this time, can not be reported in the logs, > only visually > to log errors will take some work in selenium. > > > ========================= > BJ Freeman > Strategic Power Office with Supplier Automation < > http://www.businessesnetwork.com/automation/viewforum.php?f=52> > Specialtymarket.com <http://www.specialtymarket.com/> > Systems Integrator-- Glad to Assist > > Chat Y! messenger: bjfr33man > > > Adam Heath sent the following on 12/6/2010 11:48 AM: > > On 12/06/2010 12:30 PM, BJ Freeman wrote: >> >>> The problem that Adam addressed was how to build these tests from the >>> build.xml, not run them. >>> That to me, is attainable, in the future but requires a lot more coding >>> work. >>> >> >> That wasn't what I said. I want to be able to run a selenium test from >> build.xml. I don't care how the test was created. But if the test has >> been added to trunk, I want a very simple command to run, that then >> tells me if it passes or not. >> >> If it requires setting up an external process, then the 'simple' tag >> doesn't apply. If it isn't simple, then it won't be run, and then errors >> would creep in. >> >> >
