Hello,
As a Tapestry user, I use tapestry-test to test my applications and my
widgets libraries to validate migration from tapestry versions. I did
it from tapestry 5.1 to 5.4 quite easily. I would be happy to
integrate new technologies for the tests I will write in the future
but I see
I have a few thoughts but they are conflicting.
1. Anything that makes testing easier would be welcome.
2. It would have to be beyond easy to create new test cases to make me want
to rewrite my old ones.
3. I'm sure (fill in you favorite language here) is great but I'm
mandated (It's more of a
On Tue, Jul 30, 2013 at 11:50 PM, Howard Lewis Ship hls...@gmail.comwrote:
One thing I've been saying in some of the bugs I've been closing is my
desire to get out of the testing side of things. I have no desire to
maintain the existing TestNG, EasyMock, and Selenium support code ... you
may
One reason I haven't contributed much in terms of code for quite some time is
the ever changing
technology stack Tapestry is built with. We have an increasingly complex stack
of bleeding-edge
tools and technologies that I simply lack the time of keeping up with.
I have the feeling that this
On Wed, Jul 31, 2013 at 4:10 PM, Ulrich Stärk u...@spielviel.de wrote:
One reason I haven't contributed much in terms of code for quite some time
is the ever changing
technology stack Tapestry is built with. We have an increasingly complex
stack of bleeding-edge
tools and technologies that I
I have never been able to get any selenium tapestry tests to run on my Mac at
all BTW.
Something has to do with firefiox version or something.
So, even the proverbial 'patch with tests' isn't possible for me.
I really don't mind the bleeding edge technology though.
On Jul 31, 2013, at 9:10
Hi,
Have you considered pure JavaScript based testing ?
It is much faster than WebDriver based and much closer to the real world.
1. Blog -
http://wicketinaction.com/2012/11/javascript-based-functional-testing/
2. Tests -
My 2p.
I have had major headaches in the past maintaining selenium tests. The main
problems are getting selenium to wait until the client is in a certain
state. I found checking for AJAX responses or other custom conditions to be
very flaky. Sometimes the only solution was to Thread.sleep() which
About Geb,
I still have aggravations using Geb, but it is significantly better than
Selenium.
The page and module system is terrific for creating DRY and maintainable
tests.
The wait system addresses your concern; essentially, Geb runs a retry loop
until a condition is met, and fails if the
I'm open to anything and I'll try to look at your links. That being said,
web applications are all about integration, and I just don't have
confidence unless it is tested end-to-end using a real browser.
On Wed, Jul 31, 2013 at 8:21 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
Have you
+1 for Spock and Geb.
I have been using Spock and Geb for some time now. Being both in Groovy saves
you a lot of time.
One of the concerns that I have with Geb is unstable tests which seems to be
related to WebDriver but, for some reason, are more visible with Geb.
BTW Spock extensions are
One thing I've been saying in some of the bugs I've been closing is my
desire to get out of the testing side of things. I have no desire to
maintain the existing TestNG, EasyMock, and Selenium support code ... you
may have noticed that I'm a fan of Spock for unit and mock testing, and Geb
for
12 matches
Mail list logo
