You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Mark <ma...@xeric.net> on 2011/04/25 18:45:54 UTC
testng.xml and selenium
Selenium in tapestry-test seems to have problems with Firefox 4 on OS X.
I'm trying to use Google chrome instead.
The documentation seems to imply that we can set
tapestry.browser-start-command in the testng.xml file to use a different
browser for selenium tests. However, the testng.xml file below still
launches firefox.
Am I missing something in how this should work?
Mark
src/test/conf/testng.xml:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="quickstart Application Test Suite" annotations="1.5">
<test name="Integration Tests" enabled="true">
<parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
<parameter name="tapestry.browser-start-command" value="*googlechrome"/>
<packages>
<package name="com.example.appname"/>
</packages>
<classes>
<class name="org.apache.tapestry5.test.SeleniumLauncher"/>
</classes>
</test>
</suite>
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
On Mon, Jul 18, 2011 at 4:53 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> Howard said:
> My experience is that using the old Selenium APIs with WebDriver 2.0
> is about 100% slower (i.e., execution takes twice as long).
I was able to duplicate this. I made some changes to SeleniumBaseTest
to use WebDriverBackedSelenium instead of DefaultSelenium. The
tapestry-core tests take 14 minutes on a machine where using 2.3.1's
native selenium calls (which is what the code in trunk is doing now)
only take about 7.5.
However, if you use HtmlUnit instead of Firefox, it only takes 1
minute and 20 seconds!
DefaultSelenium (using 2.3.1) - This is what is currently being used
in trunk. It runs about as fast as selenium1 and lets you use current
versions of FF and Chrome. Maximum compatibility with the older
Selenium API. There doesn't appear to be a way to use HtmlUnit with
this.
WebDriverBackedSelenium - Lets you use current browsers, plus
HtmlUnit. Can switch back and forth between Selenium and WebDriver Api
so all the existing tests would be compatible with it. Reasonable
compatibility with older Selenium API. (It looks like tapestry-core
has 6 tests that would need to be modified.) It is about twice as slow
as using Default Selenium. This is basically a stop gap measure to
help people migrate and not something that should be used if it can be
avoided.
WebDriver - Supports most modern browsers and HtmlUnit. Completely
different API. Should be significantly faster than
WebDriverBackedSelenium and potentially faster than DefaultSelenium.
> Kalle said:
> Well, they could just use an older version. But for Tapestry, it'd be
> very valuable if we could retrofit the SeleniumTestCase to use
> WebDriver api so we wouldn't need to scrap or rewrite all the existing
> tests.
I have a version of SeleniumTestCase as you described that I'd be
happy to clean up and contribute, but it is slow with FF. What is in
trunk right now gives the maximum performance in UI based browsers
without rewriting tests. I also have a partially working
WebDriverTestCase that works like SeleniumTestCase, but uses the
WebDriver api.
If there is interest, I'd think I can implement the following:
SeleniumTestCase - Basically what is in trunk now, but possibly
extracting the interface out of it.
WebDriverBackedSeleniumTestCase - Existing tests could be switched to
extend this and they would still run although slower than when
extending SeleniumTestCase. This would allow individually switching
unit test by unit test to the WebDriver api without breaking the
entire build. It would also allow running HtmlUnit tests by specifying
it in testng. As far as I know, doing this with HtmlUnit is the
fastest way to run the tests without moving away from the Selenium
API.
WebDriverTestCase - Once a WebDriverBackedSeleniumTestCase was
switched over to use the WebDriver api, it could be set to extend
WebDriverTestCase to get the speed increases of using native
WebDriver.
Now if the plan is to throw out SeleniumTestCase and switch all the
tests to Geb, this probably doesn't make sense. If the plan is to
provide some level of support for Geb, but keep the existing tests on
SeleniumTestCase, then maybe it makes sense to just create the
WebDriverTestCase for people wanting to use java and the WebDriver
api.
If any of what I've described sounds useful, let me know and I'll
submit a patch for consideration.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Chris Poulsen <ma...@nesluop.dk>.
Hi,
I have been playing some more with selenium v2.0.0 after the maven artifacts
was released. It haven't been too bad, the new WebDriver API is really nice
and the WebDriverBackedSelenium is a decent replacement for selenium1, but I
think there are a couple of minor kinks that the selenium team has to look
at before its really ready for some serious business.
For instance it seems that selenium2 has problems with clicking a link that
contains a ":" (component event) thing in the "DynamicTests" - the "click"
part seems to work, but detecting when the page has loaded screws up - doing
a "get" on the same url as the link uses works, so its probably just a minor
issue. I want to discuss this issue with the selenium guys, but haven't had
the time yet ;)
As for performance: Running 1300+ of the tapestry-core tests takes around
12-15 minutes on my windows7 laptop (running from my 5400rpm drive, not the
ssd) IIRC. (1000 of the tests being non-selenium tests and they does not
take much of the time). I can't remember how fast selenium1 was on the
tapestry tests as it has been ages since I've had firefox3 installed.
To be honest the most annoying thing about the automated tests isn't that
they run slow, its the lack of the possibility to specify which tests you
want to run from the command line IMO. I have to hack around in testng.xml
to minimize the scope when debugging the test-cases as I haven't found any
way to get the gradle -Dtest.single=xxx stuff working. Its a total waste of
time/a risk of introducing errors having to hack things like testng.xml to
simply get that single interesting test class to run.
I have a feeling that the webapp integration tests possibly should go into
separate source sets and the testng.xml may be dumped in favor of relying on
gradles automatic test detection, but my gradle-fu isn't really strong
enough to test this thesis out quickly. But I think this segmentation of the
integration applications (which is done in testgn.xml today) will making
with the -Dtest.single (and the other built-in gradle stuff) play much
nicer.
I think I'm pretty close to having the core test-suite running to completion
(without having to rewrite insane amounts of test-code) - I can give it a go
when i get home from work today.
My personal opinion on a selenium switch is that is has to be done as
selenium1 requires ancient browsers. But backwards compatibility should be a
priority (as a complete rewrite of the current tests probably will not bring
much extra value except for possibly increased test performance) - I think a
better test segmentation would go a long way to address the performance
issue. Also there are probably many applications out there with
comprehensive test-suites based on the current SeleniumTestcase (selenium v1
api) that would be stuck with the old selenium crap or forced to rewrite
everything. (A documented upgrade path to selenium v2, mentioning the most
common patterns would probably go a long way towards making this relatively
painless ;)
Btw. the possibility of starting the integration test apps using the
JettyRunner from ones IDE should probably be mentioned somewhere, it is a
nice feature! (alternatively it would be really nice to be able to run the
test-apps from command line if possible).
If someone knows the command line magic to run a single test / a group of
specific tests please enlighten me! ;)
--
Chris
On Mon, Jul 18, 2011 at 11:53 PM, Howard Lewis Ship <hl...@gmail.com>wrote:
> My experience is that using the old Selenium APIs with WebDriver 2.0
> is about 100% slower (i.e., execution takes twice as long).
>
> On Mon, Jul 18, 2011 at 1:40 PM, Mark <ma...@xeric.net> wrote:
> > It looks like Selenium 2.0 can run using WebDriver where it directly
> > works with the browser or emulating the older Selenium RC approach.
> > Is WebDriver slow or is it when you try to run 2.0 using the older
> > style tests? I thought part of the point of WebDriver was to be
> > faster.
> >
> > Mark
> >
> > On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com>
> wrote:
> >> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
> >> been having a lot of trouble since Selenium 2.0 changes things; just
> >> swapping out the new code takes a huge hit on performance. I might
> >> take a go at this, but I'd rather start thinking in terms of
> >> deprecating the selenium support inside tapestry-test and seeing about
> >> adopting Geb as a better solution that embraces Selenium 2.0.
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
>
> Well, I evaluated your patch and running time seems to be on the same
> ball park on Windows (7). Tests finished in 6:24 on my laptop, I'm
> getting 4 failures though (the treetest and a few other ajax tests).
> Makes sense to me to upgrade to Selenium 2.
>
> I had a few failures, but they also failed when running with Selenium 1 on
Firefox 3.6, so I didn't look into them.
Mark
Re: testng.xml and selenium
Posted by Kalle Korhonen <ka...@gmail.com>.
On Tue, Aug 9, 2011 at 11:58 AM, Mark <ma...@xeric.net> wrote:
> I attached the patch to:
> https://issues.apache.org/jira/browse/TAP5-1599
> Just in case anyone wants to try it out.
> Howard said that he saw a significant slowdown, but that didn't happen in my
> tests on LInux. Perhaps it is slower on OS X or Windows.
Well, I evaluated your patch and running time seems to be on the same
ball park on Windows (7). Tests finished in 6:24 on my laptop, I'm
getting 4 failures though (the treetest and a few other ajax tests).
Makes sense to me to upgrade to Selenium 2.
Kalle
>
>
>> HtmlUnit-based functional tests simplify the testing environment and
>> running them within the IDE, and also because they run much faster
>> than the Selenium (1) tests. Using the WebDriver could improve
>> execution speed and Selenium 2 also allows using HtmlUnit as the
>> WebDriver (although it's somewhat questionable what the extra
>> abstraction layers buy you in that case). It would be an interesting
>> exercise to rewrite some tests to use the WebDriver and compare
>> execution times of different drivers, namely against HtmlUnit.
>>
>>
> I think there should be a way to specify what WebDriver you want to use from
> testng.xml or something. If that is the case, it might be possible to test
> the bulk of the tests in HtmlUnit while running the tests that are looking
> for finer points of the GUI or JS implementations in several other browsers.
>
> I'm hoping there will be enough interest to either get this update included
> or at least see if we can recreate and identify what slow down issues Howard
> was running into.
>
> Mark
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
I attached the patch to:
https://issues.apache.org/jira/browse/TAP5-1599
Just in case anyone wants to try it out.
Howard said that he saw a significant slowdown, but that didn't happen in my
tests on LInux. Perhaps it is slower on OS X or Windows.
> HtmlUnit-based functional tests simplify the testing environment and
> running them within the IDE, and also because they run much faster
> than the Selenium (1) tests. Using the WebDriver could improve
> execution speed and Selenium 2 also allows using HtmlUnit as the
> WebDriver (although it's somewhat questionable what the extra
> abstraction layers buy you in that case). It would be an interesting
> exercise to rewrite some tests to use the WebDriver and compare
> execution times of different drivers, namely against HtmlUnit.
>
>
I think there should be a way to specify what WebDriver you want to use from
testng.xml or something. If that is the case, it might be possible to test
the bulk of the tests in HtmlUnit while running the tests that are looking
for finer points of the GUI or JS implementations in several other browsers.
I'm hoping there will be enough interest to either get this update included
or at least see if we can recreate and identify what slow down issues Howard
was running into.
Mark
Re: testng.xml and selenium
Posted by Kalle Korhonen <ka...@gmail.com>.
On Thu, Aug 11, 2011 at 7:25 PM, Mark <ma...@xeric.net> wrote:
> On Thu, Aug 11, 2011 at 7:57 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>> And I wonder if it wouldn't make sense to scrap SeleniumTestCase and
>> all that, and just have people do something sensible, like use Geb.
>
> Geb looks interesting. Do you have any public code that is using it?
> I'm curious how you'd handle the setup for Jetty, etc.
We (at Tynamo.org) have been successfully using HtmlUnit-based
integration tests running in an embedded Jetty. Setting up Jetty is
fairly simple and we keep it in a static property for the duration of
the tests, see http://svn.codehaus.org/tynamo/trunk/tapestry-model/tapestry-model-test/src/main/java/org/tynamo/test/AbstractContainerTest.java.
Obviously something similar could be paired up with
Geb/WebDriver-based tests as well.
> I'd think SeleniumTestCase would need to stick around particularly for
> people who have a very large number of tests already that depend on
> it.
Well, they could just use an older version. But for Tapestry, it'd be
very valuable if we could retrofit the SeleniumTestCase to use
WebDriver api so we wouldn't need to scrap or rewrite all the existing
tests.
Kalle
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
On Thu, Aug 11, 2011 at 7:57 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> And I wonder if it wouldn't make sense to scrap SeleniumTestCase and
> all that, and just have people do something sensible, like use Geb.
Geb looks interesting. Do you have any public code that is using it?
I'm curious how you'd handle the setup for Jetty, etc.
I'd think SeleniumTestCase would need to stick around particularly for
people who have a very large number of tests already that depend on
it.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Thu, Aug 11, 2011 at 5:53 PM, Mark <ma...@xeric.net> wrote:
> By the way, the current patch will only switch to the newer version of
> selenium. It does not use WebDriver which is what would be necessary
> to use HtmlUnit.
> For that to work, we need to replace the old setup in SeleniumTestCase:
>
> final Selenium selenium = new DefaultSelenium(commandProcessor);
>
> With something like:
>
> final WebDriver driver = new FirefoxDriver();
> final Selenium selenium = new WebDriverBackedSelenium(driver, baseURL);
>
> It would probably make sense to set things up so testng.xml can
> specify FirefoxDriver, HtmlUnitDriver, etc.
>
> This should let us run all the tests without an issue in theory, but
> in practice there may be a few that will need to be tweaked as
> WebDriverBackedSelenium emulates DefaultSelenium, but not perfectly.
>
> Once you have an instance of WebDriverBackedSelenium, you can get the
> WebDriver to use that API using:
> WebDriver driver = ((WrapsDriver) selenium).getWrappedDriver();
>
> I've been working on a patch for SeleniumTestCase that will do that
> but I'm running into problems getting selenium to start without
> conflicting with the existing code. I wonder if it wouldn't make more
> sense to do something like WebDriverTestCase.
And I wonder if it wouldn't make sense to scrap SeleniumTestCase and
all that, and just have people do something sensible, like use Geb.
>
> Mark
>
> On Tue, Aug 9, 2011 at 12:43 PM, Kalle Korhonen
> <ka...@gmail.com> wrote:
>>
>> Mark, this is very useful. I continue to be a firm believer of
>> htmlunit (see e.g.
>> http://docs.codehaus.org/display/TYNAMO/2010/07/30/) because
>> HtmlUnit-based functional tests simplify the testing environment and
>> running them within the IDE, and also because they run much faster
>> than the Selenium (1) tests. Using the WebDriver could improve
>> execution speed and Selenium 2 also allows using HtmlUnit as the
>> WebDriver (although it's somewhat questionable what the extra
>> abstraction layers buy you in that case). It would be an interesting
>> exercise to rewrite some tests to use the WebDriver and compare
>> execution times of different drivers, namely against HtmlUnit.
>>
>> > I've attached a patch in case anyone wants to test it out. I filed a JIRA
>> > issue TAP5-1599, but for some reason I can't seem to upload an attachment to
>> > JIRA.
>>
>> Is the patch really big? There may be a file size limit.
>>
>> Kalle
>>
>>
>> > On Mon, Aug 8, 2011 at 5:48 PM, Mark <ma...@xeric.net> wrote:
>> >> I ran some tests on Ubuntu Linux using Firefox 3.6. To run Selenium
>> >> 2, I changed the dependency in tapestry-test and added a method that
>> >> was required by the new interface. If there are two test times
>> >> listed, I ran the test twice.
>> >>
>> >> Here are the results:
>> >>
>> >> 5.2.6 Selenium 1 & Maven
>> >> 6 min 14 sec
>> >>
>> >> 5.3 with Selenium 1 & Gradle
>> >> 7 min 5 sec
>> >> 7 min 14 sec
>> >>
>> >> 5.3 Selenium 2.3 & Gradle
>> >> 7 min 26 sec
>> >> 8 min 1 sec
>> >>
>> >> So in my tested configuration, a switch to Selenium 2.3 doesn't add
>> >> any significant amount of time to the build as long as you stay on the
>> >> browser that today we are forced to use. It might be slower on newer
>> >> browsers, but that isn't a fair comparison because we can't use them
>> >> right now anyway.
>> >>
>> >>
>> >> Mark
>> >>
>> >> On Mon, Jul 18, 2011 at 4:53 PM, Howard Lewis Ship <hl...@gmail.com>
>> >> wrote:
>> >>> My experience is that using the old Selenium APIs with WebDriver 2.0
>> >>> is about 100% slower (i.e., execution takes twice as long).
>> >>>
>> >>> On Mon, Jul 18, 2011 at 1:40 PM, Mark <ma...@xeric.net> wrote:
>> >>>> It looks like Selenium 2.0 can run using WebDriver where it directly
>> >>>> works with the browser or emulating the older Selenium RC approach.
>> >>>> Is WebDriver slow or is it when you try to run 2.0 using the older
>> >>>> style tests? I thought part of the point of WebDriver was to be
>> >>>> faster.
>> >>>>
>> >>>> Mark
>> >>>>
>> >>>> On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com>
>> >>>> wrote:
>> >>>>> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
>> >>>>> been having a lot of trouble since Selenium 2.0 changes things; just
>> >>>>> swapping out the new code takes a huge hit on performance. I might
>> >>>>> take a go at this, but I'd rather start thinking in terms of
>> >>>>> deprecating the selenium support inside tapestry-test and seeing about
>> >>>>> adopting Geb as a better solution that embraces Selenium 2.0.
>> >>>>>
>> >>>>
>> >>>> ---------------------------------------------------------------------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> >>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Howard M. Lewis Ship
>> >>>
>> >>> Creator of Apache Tapestry
>> >>>
>> >>> The source for Tapestry training, mentoring and support. Contact me to
>> >>> learn how I can get you up and productive in Tapestry fast!
>> >>>
>> >>> (971) 678-5210
>> >>> http://howardlewisship.com
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> >>> For additional commands, e-mail: dev-help@tapestry.apache.org
>> >>>
>> >>>
>> >>
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> > For additional commands, e-mail: dev-help@tapestry.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
By the way, the current patch will only switch to the newer version of
selenium. It does not use WebDriver which is what would be necessary
to use HtmlUnit.
For that to work, we need to replace the old setup in SeleniumTestCase:
final Selenium selenium = new DefaultSelenium(commandProcessor);
With something like:
final WebDriver driver = new FirefoxDriver();
final Selenium selenium = new WebDriverBackedSelenium(driver, baseURL);
It would probably make sense to set things up so testng.xml can
specify FirefoxDriver, HtmlUnitDriver, etc.
This should let us run all the tests without an issue in theory, but
in practice there may be a few that will need to be tweaked as
WebDriverBackedSelenium emulates DefaultSelenium, but not perfectly.
Once you have an instance of WebDriverBackedSelenium, you can get the
WebDriver to use that API using:
WebDriver driver = ((WrapsDriver) selenium).getWrappedDriver();
I've been working on a patch for SeleniumTestCase that will do that
but I'm running into problems getting selenium to start without
conflicting with the existing code. I wonder if it wouldn't make more
sense to do something like WebDriverTestCase.
Mark
On Tue, Aug 9, 2011 at 12:43 PM, Kalle Korhonen
<ka...@gmail.com> wrote:
>
> Mark, this is very useful. I continue to be a firm believer of
> htmlunit (see e.g.
> http://docs.codehaus.org/display/TYNAMO/2010/07/30/) because
> HtmlUnit-based functional tests simplify the testing environment and
> running them within the IDE, and also because they run much faster
> than the Selenium (1) tests. Using the WebDriver could improve
> execution speed and Selenium 2 also allows using HtmlUnit as the
> WebDriver (although it's somewhat questionable what the extra
> abstraction layers buy you in that case). It would be an interesting
> exercise to rewrite some tests to use the WebDriver and compare
> execution times of different drivers, namely against HtmlUnit.
>
> > I've attached a patch in case anyone wants to test it out. I filed a JIRA
> > issue TAP5-1599, but for some reason I can't seem to upload an attachment to
> > JIRA.
>
> Is the patch really big? There may be a file size limit.
>
> Kalle
>
>
> > On Mon, Aug 8, 2011 at 5:48 PM, Mark <ma...@xeric.net> wrote:
> >> I ran some tests on Ubuntu Linux using Firefox 3.6. To run Selenium
> >> 2, I changed the dependency in tapestry-test and added a method that
> >> was required by the new interface. If there are two test times
> >> listed, I ran the test twice.
> >>
> >> Here are the results:
> >>
> >> 5.2.6 Selenium 1 & Maven
> >> 6 min 14 sec
> >>
> >> 5.3 with Selenium 1 & Gradle
> >> 7 min 5 sec
> >> 7 min 14 sec
> >>
> >> 5.3 Selenium 2.3 & Gradle
> >> 7 min 26 sec
> >> 8 min 1 sec
> >>
> >> So in my tested configuration, a switch to Selenium 2.3 doesn't add
> >> any significant amount of time to the build as long as you stay on the
> >> browser that today we are forced to use. It might be slower on newer
> >> browsers, but that isn't a fair comparison because we can't use them
> >> right now anyway.
> >>
> >>
> >> Mark
> >>
> >> On Mon, Jul 18, 2011 at 4:53 PM, Howard Lewis Ship <hl...@gmail.com>
> >> wrote:
> >>> My experience is that using the old Selenium APIs with WebDriver 2.0
> >>> is about 100% slower (i.e., execution takes twice as long).
> >>>
> >>> On Mon, Jul 18, 2011 at 1:40 PM, Mark <ma...@xeric.net> wrote:
> >>>> It looks like Selenium 2.0 can run using WebDriver where it directly
> >>>> works with the browser or emulating the older Selenium RC approach.
> >>>> Is WebDriver slow or is it when you try to run 2.0 using the older
> >>>> style tests? I thought part of the point of WebDriver was to be
> >>>> faster.
> >>>>
> >>>> Mark
> >>>>
> >>>> On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com>
> >>>> wrote:
> >>>>> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
> >>>>> been having a lot of trouble since Selenium 2.0 changes things; just
> >>>>> swapping out the new code takes a huge hit on performance. I might
> >>>>> take a go at this, but I'd rather start thinking in terms of
> >>>>> deprecating the selenium support inside tapestry-test and seeing about
> >>>>> adopting Geb as a better solution that embraces Selenium 2.0.
> >>>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Howard M. Lewis Ship
> >>>
> >>> Creator of Apache Tapestry
> >>>
> >>> The source for Tapestry training, mentoring and support. Contact me to
> >>> learn how I can get you up and productive in Tapestry fast!
> >>>
> >>> (971) 678-5210
> >>> http://howardlewisship.com
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>>
> >>>
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Kalle Korhonen <ka...@gmail.com>.
On Tue, Aug 9, 2011 at 6:52 AM, Mark <ma...@xeric.net> wrote:
> I went ahead and reran the tapestry-core tests using Selenium 2.3.1, but
> this time with Firefox 5. At least on my install of ubuntu it is
> faster--not slower than Selenium 1 with FF 3.6. This is using Selenium
> 2.3.1 as a drop in replacement for Selenium 1. If we want even faster test
> times, we might be able to get it by rewriting a few of the longer running
> tests using the WebDriver API.
Mark, this is very useful. I continue to be a firm believer of
htmlunit (see e.g.
http://docs.codehaus.org/display/TYNAMO/2010/07/30/) because
HtmlUnit-based functional tests simplify the testing environment and
running them within the IDE, and also because they run much faster
than the Selenium (1) tests. Using the WebDriver could improve
execution speed and Selenium 2 also allows using HtmlUnit as the
WebDriver (although it's somewhat questionable what the extra
abstraction layers buy you in that case). It would be an interesting
exercise to rewrite some tests to use the WebDriver and compare
execution times of different drivers, namely against HtmlUnit.
> I've attached a patch in case anyone wants to test it out. I filed a JIRA
> issue TAP5-1599, but for some reason I can't seem to upload an attachment to
> JIRA.
Is the patch really big? There may be a file size limit.
Kalle
> On Mon, Aug 8, 2011 at 5:48 PM, Mark <ma...@xeric.net> wrote:
>> I ran some tests on Ubuntu Linux using Firefox 3.6. To run Selenium
>> 2, I changed the dependency in tapestry-test and added a method that
>> was required by the new interface. If there are two test times
>> listed, I ran the test twice.
>>
>> Here are the results:
>>
>> 5.2.6 Selenium 1 & Maven
>> 6 min 14 sec
>>
>> 5.3 with Selenium 1 & Gradle
>> 7 min 5 sec
>> 7 min 14 sec
>>
>> 5.3 Selenium 2.3 & Gradle
>> 7 min 26 sec
>> 8 min 1 sec
>>
>> So in my tested configuration, a switch to Selenium 2.3 doesn't add
>> any significant amount of time to the build as long as you stay on the
>> browser that today we are forced to use. It might be slower on newer
>> browsers, but that isn't a fair comparison because we can't use them
>> right now anyway.
>>
>>
>> Mark
>>
>> On Mon, Jul 18, 2011 at 4:53 PM, Howard Lewis Ship <hl...@gmail.com>
>> wrote:
>>> My experience is that using the old Selenium APIs with WebDriver 2.0
>>> is about 100% slower (i.e., execution takes twice as long).
>>>
>>> On Mon, Jul 18, 2011 at 1:40 PM, Mark <ma...@xeric.net> wrote:
>>>> It looks like Selenium 2.0 can run using WebDriver where it directly
>>>> works with the browser or emulating the older Selenium RC approach.
>>>> Is WebDriver slow or is it when you try to run 2.0 using the older
>>>> style tests? I thought part of the point of WebDriver was to be
>>>> faster.
>>>>
>>>> Mark
>>>>
>>>> On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com>
>>>> wrote:
>>>>> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
>>>>> been having a lot of trouble since Selenium 2.0 changes things; just
>>>>> swapping out the new code takes a huge hit on performance. I might
>>>>> take a go at this, but I'd rather start thinking in terms of
>>>>> deprecating the selenium support inside tapestry-test and seeing about
>>>>> adopting Geb as a better solution that embraces Selenium 2.0.
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Howard M. Lewis Ship
>>>
>>> Creator of Apache Tapestry
>>>
>>> The source for Tapestry training, mentoring and support. Contact me to
>>> learn how I can get you up and productive in Tapestry fast!
>>>
>>> (971) 678-5210
>>> http://howardlewisship.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
I went ahead and reran the tapestry-core tests using Selenium 2.3.1, but
this time with Firefox 5. At least on my install of ubuntu it is
faster--not slower than Selenium 1 with FF 3.6. This is using Selenium
2.3.1 as a drop in replacement for Selenium 1. If we want even faster test
times, we might be able to get it by rewriting a few of the longer running
tests using the WebDriver API.
I've attached a patch in case anyone wants to test it out. I filed a JIRA
issue TAP5-1599 <https://issues.apache.org/jira/browse/TAP5-1599>, but for
some reason I can't seem to upload an attachment to JIRA.
Firefox 5:
5.3 Selenium 2 & Gradle
6:47
6:42
Using Firefox 3.6:
5.2.6 Selenium 1 & Maven
6:14
5.3 with Selenium 1 & Gradle
7:05
7:14
5.3 Selenium 2 & Gradle
7:26
8:01
Mark
On Mon, Aug 8, 2011 at 5:48 PM, Mark <ma...@xeric.net> wrote:
> I ran some tests on Ubuntu Linux using Firefox 3.6. To run Selenium
> 2, I changed the dependency in tapestry-test and added a method that
> was required by the new interface. If there are two test times
> listed, I ran the test twice.
>
> Here are the results:
>
> 5.2.6 Selenium 1 & Maven
> 6 min 14 sec
>
> 5.3 with Selenium 1 & Gradle
> 7 min 5 sec
> 7 min 14 sec
>
> 5.3 Selenium 2.3 & Gradle
> 7 min 26 sec
> 8 min 1 sec
>
> So in my tested configuration, a switch to Selenium 2.3 doesn't add
> any significant amount of time to the build as long as you stay on the
> browser that today we are forced to use. It might be slower on newer
> browsers, but that isn't a fair comparison because we can't use them
> right now anyway.
>
>
> Mark
>
> On Mon, Jul 18, 2011 at 4:53 PM, Howard Lewis Ship <hl...@gmail.com>
wrote:
>> My experience is that using the old Selenium APIs with WebDriver 2.0
>> is about 100% slower (i.e., execution takes twice as long).
>>
>> On Mon, Jul 18, 2011 at 1:40 PM, Mark <ma...@xeric.net> wrote:
>>> It looks like Selenium 2.0 can run using WebDriver where it directly
>>> works with the browser or emulating the older Selenium RC approach.
>>> Is WebDriver slow or is it when you try to run 2.0 using the older
>>> style tests? I thought part of the point of WebDriver was to be
>>> faster.
>>>
>>> Mark
>>>
>>> On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com>
wrote:
>>>> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
>>>> been having a lot of trouble since Selenium 2.0 changes things; just
>>>> swapping out the new code takes a huge hit on performance. I might
>>>> take a go at this, but I'd rather start thinking in terms of
>>>> deprecating the selenium support inside tapestry-test and seeing about
>>>> adopting Geb as a better solution that embraces Selenium 2.0.
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
I ran some tests on Ubuntu Linux using Firefox 3.6. To run Selenium
2, I changed the dependency in tapestry-test and added a method that
was required by the new interface. If there are two test times
listed, I ran the test twice.
Here are the results:
5.2.6 Selenium 1 & Maven
6 min 14 sec
5.3 with Selenium 1 & Gradle
7 min 5 sec
7 min 14 sec
5.3 Selenium 2.3 & Gradle
7 min 26 sec
8 min 1 sec
So in my tested configuration, a switch to Selenium 2.3 doesn't add
any significant amount of time to the build as long as you stay on the
browser that today we are forced to use. It might be slower on newer
browsers, but that isn't a fair comparison because we can't use them
right now anyway.
Mark
On Mon, Jul 18, 2011 at 4:53 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> My experience is that using the old Selenium APIs with WebDriver 2.0
> is about 100% slower (i.e., execution takes twice as long).
>
> On Mon, Jul 18, 2011 at 1:40 PM, Mark <ma...@xeric.net> wrote:
>> It looks like Selenium 2.0 can run using WebDriver where it directly
>> works with the browser or emulating the older Selenium RC approach.
>> Is WebDriver slow or is it when you try to run 2.0 using the older
>> style tests? I thought part of the point of WebDriver was to be
>> faster.
>>
>> Mark
>>
>> On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>>> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
>>> been having a lot of trouble since Selenium 2.0 changes things; just
>>> swapping out the new code takes a huge hit on performance. I might
>>> take a go at this, but I'd rather start thinking in terms of
>>> deprecating the selenium support inside tapestry-test and seeing about
>>> adopting Geb as a better solution that embraces Selenium 2.0.
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Howard Lewis Ship <hl...@gmail.com>.
My experience is that using the old Selenium APIs with WebDriver 2.0
is about 100% slower (i.e., execution takes twice as long).
On Mon, Jul 18, 2011 at 1:40 PM, Mark <ma...@xeric.net> wrote:
> It looks like Selenium 2.0 can run using WebDriver where it directly
> works with the browser or emulating the older Selenium RC approach.
> Is WebDriver slow or is it when you try to run 2.0 using the older
> style tests? I thought part of the point of WebDriver was to be
> faster.
>
> Mark
>
> On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
>> been having a lot of trouble since Selenium 2.0 changes things; just
>> swapping out the new code takes a huge hit on performance. I might
>> take a go at this, but I'd rather start thinking in terms of
>> deprecating the selenium support inside tapestry-test and seeing about
>> adopting Geb as a better solution that embraces Selenium 2.0.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
It looks like Selenium 2.0 can run using WebDriver where it directly
works with the browser or emulating the older Selenium RC approach.
Is WebDriver slow or is it when you try to run 2.0 using the older
style tests? I thought part of the point of WebDriver was to be
faster.
Mark
On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
> been having a lot of trouble since Selenium 2.0 changes things; just
> swapping out the new code takes a huge hit on performance. I might
> take a go at this, but I'd rather start thinking in terms of
> deprecating the selenium support inside tapestry-test and seeing about
> adopting Geb as a better solution that embraces Selenium 2.0.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Tom van Dijk <to...@tvandijk.nl>.
I'm noticing the impact on performance right now yes. I'm using the
approach of Chris Poulsen (30th of June) so I don't need to hack
selenium 1.0.3 but it's dreadfully slow. I may just as well go make
dinner instead of just running for coffee which is the usual
"compiling...." activity. (insert appropriate xkcd link here)
On 07/18/2011 08:47 PM, Howard Lewis Ship wrote:
> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
> been having a lot of trouble since Selenium 2.0 changes things; just
> swapping out the new code takes a huge hit on performance. I might
> take a go at this, but I'd rather start thinking in terms of
> deprecating the selenium support inside tapestry-test and seeing about
> adopting Geb as a better solution that embraces Selenium 2.0.
>
> On Mon, Jul 18, 2011 at 11:11 AM, Tom van Dijk<to...@tvandijk.nl> wrote:
>> I was wondering when tapestry-test will indeed switch to Selenium 2.0
>>
>> The problem is still here.
>>
>>
>> On 04/25/2011 07:18 PM, Mark wrote:
>>> Thanks Alex. I've seen this issue and I'm assuming it will be fixed when
>>> tapestry-test switches to the 2.0 version of Selenium. But if I should be
>>> able to just switch to Google Chrome by changing the setting in testng.xml
>>> I'd rather just do that so I'm not relying on a modified version of the
>>> selenium jar.
>>>
>>> Do you know if the line
>>> <parameter name="tapestry.browser-start-command" value="*googlechrome"/>
>>> in testng.xml switch it over to using Chrome instead of Firefox?
>>>
>>> Mark
>>>
>>> On Mon, Apr 25, 2011 at 12:05 PM, Alex Kotchnev<ak...@gmail.com>
>>> wrote:
>>>
>>>> This is likely to be a problem w/ Selenium RC itself - I know that for
>>>> a totally unrelated project I had to edit the files in selenium RC jar
>>>> to make it support firefox 4.0 - http://www.qaautomation.net/?p=245
>>>>
>>>> Cheers,
>>>>
>>>> Alex K
>>>>
>>>> On Mon, Apr 25, 2011 at 12:59 PM, Mark<ma...@xeric.net> wrote:
>>>>> I've tried it with 5.2.4, 5.2.5 and 5.3.0-SNAPSHOT. It tries to use
>>>> Firefox
>>>>> 4 and hangs.
>>>>> <parameter name="tapestry.browser-start-
>>>>> command" value="*googlechrome"/>
>>>>> Doesn't seem to change anything and neither does:
>>>>>
>>>>> <parameter name="tapestry.browser-start-
>>>>> command" value="*safari"/>
>>>>>
>>>>> Mark
>>>>>
>>>>> On Mon, Apr 25, 2011 at 11:47 AM, Howard Lewis Ship<hlship@gmail.com
>>>>> wrote:
>>>>>
>>>>>> What version of Tapestry? This was in flux in 5.1 and 5.2.
>>>>>>
>>>>>> On Mon, Apr 25, 2011 at 9:45 AM, Mark<ma...@xeric.net> wrote:
>>>>>>> Selenium in tapestry-test seems to have problems with Firefox 4 on OS
>>>> X.
>>>>>>> I'm trying to use Google chrome instead.
>>>>>>>
>>>>>>> The documentation seems to imply that we can set
>>>>>>> tapestry.browser-start-command in the testng.xml file to use a
>>>> different
>>>>>>> browser for selenium tests. However, the testng.xml file below still
>>>>>>> launches firefox.
>>>>>>>
>>>>>>> Am I missing something in how this should work?
>>>>>>>
>>>>>>> Mark
>>>>>>>
>>>>>>> src/test/conf/testng.xml:
>>>>>>>
>>>>>>> <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
>>>>>>> <suite name="quickstart Application Test Suite" annotations="1.5">
>>>>>>> <test name="Integration Tests" enabled="true">
>>>>>>> <parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
>>>>>>> <parameter name="tapestry.browser-start-command"
>>>>>> value="*googlechrome"/>
>>>>>>> <packages>
>>>>>>> <package name="com.example.appname"/>
>>>>>>> </packages>
>>>>>>> <classes>
>>>>>>> <class name="org.apache.tapestry5.test.SeleniumLauncher"/>
>>>>>>> </classes>
>>>>>>> </test>
>>>>>>> </suite>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Howard M. Lewis Ship
>>>>>>
>>>>>> Creator of Apache Tapestry
>>>>>>
>>>>>> The source for Tapestry training, mentoring and support. Contact me to
>>>>>> learn how I can get you up and productive in Tapestry fast!
>>>>>>
>>>>>> (971) 678-5210
>>>>>> http://howardlewisship.com
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Howard Lewis Ship <hl...@gmail.com>.
I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've
been having a lot of trouble since Selenium 2.0 changes things; just
swapping out the new code takes a huge hit on performance. I might
take a go at this, but I'd rather start thinking in terms of
deprecating the selenium support inside tapestry-test and seeing about
adopting Geb as a better solution that embraces Selenium 2.0.
On Mon, Jul 18, 2011 at 11:11 AM, Tom van Dijk <to...@tvandijk.nl> wrote:
> I was wondering when tapestry-test will indeed switch to Selenium 2.0
>
> The problem is still here.
>
>
> On 04/25/2011 07:18 PM, Mark wrote:
>>
>> Thanks Alex. I've seen this issue and I'm assuming it will be fixed when
>> tapestry-test switches to the 2.0 version of Selenium. But if I should be
>> able to just switch to Google Chrome by changing the setting in testng.xml
>> I'd rather just do that so I'm not relying on a modified version of the
>> selenium jar.
>>
>> Do you know if the line
>> <parameter name="tapestry.browser-start-command" value="*googlechrome"/>
>> in testng.xml switch it over to using Chrome instead of Firefox?
>>
>> Mark
>>
>> On Mon, Apr 25, 2011 at 12:05 PM, Alex Kotchnev<ak...@gmail.com>
>> wrote:
>>
>>> This is likely to be a problem w/ Selenium RC itself - I know that for
>>> a totally unrelated project I had to edit the files in selenium RC jar
>>> to make it support firefox 4.0 - http://www.qaautomation.net/?p=245
>>>
>>> Cheers,
>>>
>>> Alex K
>>>
>>> On Mon, Apr 25, 2011 at 12:59 PM, Mark<ma...@xeric.net> wrote:
>>>>
>>>> I've tried it with 5.2.4, 5.2.5 and 5.3.0-SNAPSHOT. It tries to use
>>>
>>> Firefox
>>>>
>>>> 4 and hangs.
>>>> <parameter name="tapestry.browser-start-
>>>> command" value="*googlechrome"/>
>>>> Doesn't seem to change anything and neither does:
>>>>
>>>> <parameter name="tapestry.browser-start-
>>>> command" value="*safari"/>
>>>>
>>>> Mark
>>>>
>>>> On Mon, Apr 25, 2011 at 11:47 AM, Howard Lewis Ship<hlship@gmail.com
>>>> wrote:
>>>>
>>>>> What version of Tapestry? This was in flux in 5.1 and 5.2.
>>>>>
>>>>> On Mon, Apr 25, 2011 at 9:45 AM, Mark<ma...@xeric.net> wrote:
>>>>>>
>>>>>> Selenium in tapestry-test seems to have problems with Firefox 4 on OS
>>>
>>> X.
>>>>>>
>>>>>> I'm trying to use Google chrome instead.
>>>>>>
>>>>>> The documentation seems to imply that we can set
>>>>>> tapestry.browser-start-command in the testng.xml file to use a
>>>
>>> different
>>>>>>
>>>>>> browser for selenium tests. However, the testng.xml file below still
>>>>>> launches firefox.
>>>>>>
>>>>>> Am I missing something in how this should work?
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>> src/test/conf/testng.xml:
>>>>>>
>>>>>> <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
>>>>>> <suite name="quickstart Application Test Suite" annotations="1.5">
>>>>>> <test name="Integration Tests" enabled="true">
>>>>>> <parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
>>>>>> <parameter name="tapestry.browser-start-command"
>>>>>
>>>>> value="*googlechrome"/>
>>>>>>
>>>>>> <packages>
>>>>>> <package name="com.example.appname"/>
>>>>>> </packages>
>>>>>> <classes>
>>>>>> <class name="org.apache.tapestry5.test.SeleniumLauncher"/>
>>>>>> </classes>
>>>>>> </test>
>>>>>> </suite>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Howard M. Lewis Ship
>>>>>
>>>>> Creator of Apache Tapestry
>>>>>
>>>>> The source for Tapestry training, mentoring and support. Contact me to
>>>>> learn how I can get you up and productive in Tapestry fast!
>>>>>
>>>>> (971) 678-5210
>>>>> http://howardlewisship.com
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Tom van Dijk <to...@tvandijk.nl>.
I was wondering when tapestry-test will indeed switch to Selenium 2.0
The problem is still here.
On 04/25/2011 07:18 PM, Mark wrote:
> Thanks Alex. I've seen this issue and I'm assuming it will be fixed when
> tapestry-test switches to the 2.0 version of Selenium. But if I should be
> able to just switch to Google Chrome by changing the setting in testng.xml
> I'd rather just do that so I'm not relying on a modified version of the
> selenium jar.
>
> Do you know if the line
> <parameter name="tapestry.browser-start-command" value="*googlechrome"/>
> in testng.xml switch it over to using Chrome instead of Firefox?
>
> Mark
>
> On Mon, Apr 25, 2011 at 12:05 PM, Alex Kotchnev<ak...@gmail.com> wrote:
>
>> This is likely to be a problem w/ Selenium RC itself - I know that for
>> a totally unrelated project I had to edit the files in selenium RC jar
>> to make it support firefox 4.0 - http://www.qaautomation.net/?p=245
>>
>> Cheers,
>>
>> Alex K
>>
>> On Mon, Apr 25, 2011 at 12:59 PM, Mark<ma...@xeric.net> wrote:
>>> I've tried it with 5.2.4, 5.2.5 and 5.3.0-SNAPSHOT. It tries to use
>> Firefox
>>> 4 and hangs.
>>> <parameter name="tapestry.browser-start-
>>> command" value="*googlechrome"/>
>>> Doesn't seem to change anything and neither does:
>>>
>>> <parameter name="tapestry.browser-start-
>>> command" value="*safari"/>
>>>
>>> Mark
>>>
>>> On Mon, Apr 25, 2011 at 11:47 AM, Howard Lewis Ship<hlship@gmail.com
>>> wrote:
>>>
>>>> What version of Tapestry? This was in flux in 5.1 and 5.2.
>>>>
>>>> On Mon, Apr 25, 2011 at 9:45 AM, Mark<ma...@xeric.net> wrote:
>>>>> Selenium in tapestry-test seems to have problems with Firefox 4 on OS
>> X.
>>>>> I'm trying to use Google chrome instead.
>>>>>
>>>>> The documentation seems to imply that we can set
>>>>> tapestry.browser-start-command in the testng.xml file to use a
>> different
>>>>> browser for selenium tests. However, the testng.xml file below still
>>>>> launches firefox.
>>>>>
>>>>> Am I missing something in how this should work?
>>>>>
>>>>> Mark
>>>>>
>>>>> src/test/conf/testng.xml:
>>>>>
>>>>> <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
>>>>> <suite name="quickstart Application Test Suite" annotations="1.5">
>>>>> <test name="Integration Tests" enabled="true">
>>>>> <parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
>>>>> <parameter name="tapestry.browser-start-command"
>>>> value="*googlechrome"/>
>>>>> <packages>
>>>>> <package name="com.example.appname"/>
>>>>> </packages>
>>>>> <classes>
>>>>> <class name="org.apache.tapestry5.test.SeleniumLauncher"/>
>>>>> </classes>
>>>>> </test>
>>>>> </suite>
>>>>>
>>>>
>>>>
>>>> --
>>>> Howard M. Lewis Ship
>>>>
>>>> Creator of Apache Tapestry
>>>>
>>>> The source for Tapestry training, mentoring and support. Contact me to
>>>> learn how I can get you up and productive in Tapestry fast!
>>>>
>>>> (971) 678-5210
>>>> http://howardlewisship.com
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
Thanks Alex. I've seen this issue and I'm assuming it will be fixed when
tapestry-test switches to the 2.0 version of Selenium. But if I should be
able to just switch to Google Chrome by changing the setting in testng.xml
I'd rather just do that so I'm not relying on a modified version of the
selenium jar.
Do you know if the line
<parameter name="tapestry.browser-start-command" value="*googlechrome"/>
in testng.xml switch it over to using Chrome instead of Firefox?
Mark
On Mon, Apr 25, 2011 at 12:05 PM, Alex Kotchnev <ak...@gmail.com> wrote:
> This is likely to be a problem w/ Selenium RC itself - I know that for
> a totally unrelated project I had to edit the files in selenium RC jar
> to make it support firefox 4.0 - http://www.qaautomation.net/?p=245
>
> Cheers,
>
> Alex K
>
> On Mon, Apr 25, 2011 at 12:59 PM, Mark <ma...@xeric.net> wrote:
> > I've tried it with 5.2.4, 5.2.5 and 5.3.0-SNAPSHOT. It tries to use
> Firefox
> > 4 and hangs.
> > <parameter name="tapestry.browser-start-
> > command" value="*googlechrome"/>
> > Doesn't seem to change anything and neither does:
> >
> > <parameter name="tapestry.browser-start-
> > command" value="*safari"/>
> >
> > Mark
> >
> > On Mon, Apr 25, 2011 at 11:47 AM, Howard Lewis Ship <hlship@gmail.com
> >wrote:
> >
> >> What version of Tapestry? This was in flux in 5.1 and 5.2.
> >>
> >> On Mon, Apr 25, 2011 at 9:45 AM, Mark <ma...@xeric.net> wrote:
> >> > Selenium in tapestry-test seems to have problems with Firefox 4 on OS
> X.
> >> > I'm trying to use Google chrome instead.
> >> >
> >> > The documentation seems to imply that we can set
> >> > tapestry.browser-start-command in the testng.xml file to use a
> different
> >> > browser for selenium tests. However, the testng.xml file below still
> >> > launches firefox.
> >> >
> >> > Am I missing something in how this should work?
> >> >
> >> > Mark
> >> >
> >> > src/test/conf/testng.xml:
> >> >
> >> > <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
> >> > <suite name="quickstart Application Test Suite" annotations="1.5">
> >> > <test name="Integration Tests" enabled="true">
> >> > <parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
> >> > <parameter name="tapestry.browser-start-command"
> >> value="*googlechrome"/>
> >> > <packages>
> >> > <package name="com.example.appname"/>
> >> > </packages>
> >> > <classes>
> >> > <class name="org.apache.tapestry5.test.SeleniumLauncher"/>
> >> > </classes>
> >> > </test>
> >> > </suite>
> >> >
> >>
> >>
> >>
> >> --
> >> Howard M. Lewis Ship
> >>
> >> Creator of Apache Tapestry
> >>
> >> The source for Tapestry training, mentoring and support. Contact me to
> >> learn how I can get you up and productive in Tapestry fast!
> >>
> >> (971) 678-5210
> >> http://howardlewisship.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: testng.xml and selenium
Posted by Alex Kotchnev <ak...@gmail.com>.
This is likely to be a problem w/ Selenium RC itself - I know that for
a totally unrelated project I had to edit the files in selenium RC jar
to make it support firefox 4.0 - http://www.qaautomation.net/?p=245
Cheers,
Alex K
On Mon, Apr 25, 2011 at 12:59 PM, Mark <ma...@xeric.net> wrote:
> I've tried it with 5.2.4, 5.2.5 and 5.3.0-SNAPSHOT. It tries to use Firefox
> 4 and hangs.
> <parameter name="tapestry.browser-start-
> command" value="*googlechrome"/>
> Doesn't seem to change anything and neither does:
>
> <parameter name="tapestry.browser-start-
> command" value="*safari"/>
>
> Mark
>
> On Mon, Apr 25, 2011 at 11:47 AM, Howard Lewis Ship <hl...@gmail.com>wrote:
>
>> What version of Tapestry? This was in flux in 5.1 and 5.2.
>>
>> On Mon, Apr 25, 2011 at 9:45 AM, Mark <ma...@xeric.net> wrote:
>> > Selenium in tapestry-test seems to have problems with Firefox 4 on OS X.
>> > I'm trying to use Google chrome instead.
>> >
>> > The documentation seems to imply that we can set
>> > tapestry.browser-start-command in the testng.xml file to use a different
>> > browser for selenium tests. However, the testng.xml file below still
>> > launches firefox.
>> >
>> > Am I missing something in how this should work?
>> >
>> > Mark
>> >
>> > src/test/conf/testng.xml:
>> >
>> > <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
>> > <suite name="quickstart Application Test Suite" annotations="1.5">
>> > <test name="Integration Tests" enabled="true">
>> > <parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
>> > <parameter name="tapestry.browser-start-command"
>> value="*googlechrome"/>
>> > <packages>
>> > <package name="com.example.appname"/>
>> > </packages>
>> > <classes>
>> > <class name="org.apache.tapestry5.test.SeleniumLauncher"/>
>> > </classes>
>> > </test>
>> > </suite>
>> >
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: testng.xml and selenium
Posted by Mark <ma...@xeric.net>.
I've tried it with 5.2.4, 5.2.5 and 5.3.0-SNAPSHOT. It tries to use Firefox
4 and hangs.
<parameter name="tapestry.browser-start-
command" value="*googlechrome"/>
Doesn't seem to change anything and neither does:
<parameter name="tapestry.browser-start-
command" value="*safari"/>
Mark
On Mon, Apr 25, 2011 at 11:47 AM, Howard Lewis Ship <hl...@gmail.com>wrote:
> What version of Tapestry? This was in flux in 5.1 and 5.2.
>
> On Mon, Apr 25, 2011 at 9:45 AM, Mark <ma...@xeric.net> wrote:
> > Selenium in tapestry-test seems to have problems with Firefox 4 on OS X.
> > I'm trying to use Google chrome instead.
> >
> > The documentation seems to imply that we can set
> > tapestry.browser-start-command in the testng.xml file to use a different
> > browser for selenium tests. However, the testng.xml file below still
> > launches firefox.
> >
> > Am I missing something in how this should work?
> >
> > Mark
> >
> > src/test/conf/testng.xml:
> >
> > <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
> > <suite name="quickstart Application Test Suite" annotations="1.5">
> > <test name="Integration Tests" enabled="true">
> > <parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
> > <parameter name="tapestry.browser-start-command"
> value="*googlechrome"/>
> > <packages>
> > <package name="com.example.appname"/>
> > </packages>
> > <classes>
> > <class name="org.apache.tapestry5.test.SeleniumLauncher"/>
> > </classes>
> > </test>
> > </suite>
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: testng.xml and selenium
Posted by Howard Lewis Ship <hl...@gmail.com>.
What version of Tapestry? This was in flux in 5.1 and 5.2.
On Mon, Apr 25, 2011 at 9:45 AM, Mark <ma...@xeric.net> wrote:
> Selenium in tapestry-test seems to have problems with Firefox 4 on OS X.
> I'm trying to use Google chrome instead.
>
> The documentation seems to imply that we can set
> tapestry.browser-start-command in the testng.xml file to use a different
> browser for selenium tests. However, the testng.xml file below still
> launches firefox.
>
> Am I missing something in how this should work?
>
> Mark
>
> src/test/conf/testng.xml:
>
> <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
> <suite name="quickstart Application Test Suite" annotations="1.5">
> <test name="Integration Tests" enabled="true">
> <parameter name="tapestry.web-app-folder" value="src/main/webapp"/>
> <parameter name="tapestry.browser-start-command" value="*googlechrome"/>
> <packages>
> <package name="com.example.appname"/>
> </packages>
> <classes>
> <class name="org.apache.tapestry5.test.SeleniumLauncher"/>
> </classes>
> </test>
> </suite>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org