Martin Grigorov wrote:
I'm using quite successfully WebDriver (a.k.a. Selenium 2).
We have also used WebDriver in our current project and i am quite
satisfied with the results.
I have also written with my colleagues a small framework that makes
easier to integrate webdriver to wicket with bdd way. If someone is
interested, plz check this => http://www.jdave.org/bdd-wicket/
MSi
El lun, 11-05-2009 a las 04:35 -0700, Douglas Ferguson escribió:
On a side note, does Selenium even work with wicket?
Douglas
-----Original Message-----
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Monday, May 11, 2009 12:13 AM
To: users@wicket.apache.org
Subject: Re: 60% waste
unit testing is about testing small isolated bits of functionality in isolation
lets say that you want to test foo(p) { return a(b(c(p))); }
what martin is trying to do is to test that foo(q) yields the desired
value w, what he should do instead is
test a() in isolation to make sure it works
test b() in isolation to make sure it works
test c() in isolation to make sure it works
test that foo() calls a,b,c.
if all small tests above pass you are guaranteed that foo() works.
-igor
On Sun, May 10, 2009 at 9:55 PM, Marko Sibakov <marko.siba...@ri.fi> wrote:
Ben Tilford wrote:
Have you looked at selenium? Your not really "unit" testing here.
Hi Ben,
What do you mean "Your not really "unit" testing here." ?
MSi
On Sat, May 9, 2009 at 7:41 AM, Marko Sibakov <marko.siba...@ri.fi> wrote:
Like Martijn said i also strongly recommend to take a look at the
jdave-wicket's selectors (http://www.jdave.org/).
examples =>
http://svn.laughingpanda.org/svn/jdave/trunk/jdave-wicket/src/test/jdave/wicket/PageWithItemsSpec.java
with form tester it goes like this =>
form = wicket.newFormTester(selectFirst(Form.class,
"form").from(panel).getPageRelativePath());
form.setValue("name", "wicket");
form.setValue("address", "jdave");
form.submit();
MSi
Martijn Dashorst wrote:
See jdave-wicket for better test support. Slated to come to you in
Wicket
1.5
Martijn
On Fri, May 8, 2009 at 5:48 PM, Martin Makundi
<martin.maku...@koodaripalvelut.com> wrote:
Hi!
I use TDD: I spend 60% of my time type-checking and path-checking my
wicketTests and components.
I always have the wrong path and I must prinDocument and iterate to
get it right....
Anybody have the same experience?
How about introducing type-safety and path-safety/identity into
component hierarchies?
Can this be done?
**
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
