+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 really easy and fun to write!. regarding Ulrich's point. I agree that Tapestry stack keeps changing and it is not easy to cope up with it. Actually, that is a great thing if you have time to learn. You get free examples in the clearest of codes from Howard!! On the flip side, if you don't have time, you lag behind and can't contribute much to the project. That is one reason my blog has dried out as I couldn't get time to experiment with Tapestry 5.4. Thankfully, we have started migrating our libraries to Tapestry 5.4. I am now looking into the new source and it looks like an exciting next few weeks. regards Taha On 31-Jul-2013, at 7:54 PM, Massimo Lusetti <mluse...@gmail.com> wrote: > 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 simply lack the time of keeping up with. >> >> I have the feeling that this might be a turn-down for other potential >> contributors as well. I won't >> be against it but don't be surprised about continously declining >> contributor activity. >> >> >> > One the other side I've always taken the "stack of bleeding-edge tools and > technologies" used inside Tapestry as a reason to learn cool new stuff and > ideas. > > BTW Spock and Geb doesn't seem so new in the market, well newer then TestNG > and EasyMock yes. > > I can buy your point of view from a "enterprise business" point of view but > I think we talking about a slow scrap with a deprecation cycle instead of > simply throw away in the trash. > > -- > Massimo Lusetti --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
