Hi Marcus,
Yep, I guess this setup won't fit all projects. I also use selenium for
other purposes (testing of AJAX components in varous browsers), but for a
MVC framework I guess canoo fits perfectly.
Feel free to reuse the setup,
2010/10/1 M.C.S. <[email protected]>
> Hi Remi,
>
> this sounds like a good solution. As we do use AJAX in our Stripes apps, we
> are using Selenium to test our apps. But for sure, canoo is a better
> solution for this use case.
> Maybe I will "steal" your testing practices for future non-ajax projects
> :-)
>
> Greetings,
> Marcus
>
> Am 01.10.2010 10:41, schrieb VANKEISBELCK Remi:
>
> Hi folks,
>
> I think Stripes lacks some webtests to ensure it behaves as we want in a
> web container. We have unit tests and mock roundtrip, but still, many parts
> are not tested (taglib).
>
> Bugzooky is supposed to show most of the major features, and it will evolve
> as Stripes evolves, so testing against it seems reasonable. Next step is to
> create dedicated apps/pages to test each feature in isolation, and for each
> filed bug !
>
> In order for us to write those tests, I've created a dedicated module
> (named 'webtests') under the parent. It configures everything so that we can
> write tests easily, and run them against the stripes-examples war. It's
> included in the maven build, and activated only with the profile 'webtests'
> (i.e. it won't fire for now if you only do mvn clean install in the top
> level folder). We'll decide later on if we want to include this in the
> continuous build...
>
> There are many technologies that allow to do webtests. I've chosen canoo,
> because :
> * I've already used it and it took me 10 minutes to setup everything
> * It doesn't depend on a browser, it's headless
> * It integrates nicely to the build along with cargo
> * It produces very high quality reports
> * Writing tests with it is really easy, in Groovy, like this :
>
> https://stripes.svn.sourceforge.net/svnroot/stripes/branches/1.5.x/webtests/src/test/groovy/net/sourceforge/stripes/webtests/calc/CalcTest.groovy
>
> As we don't need to test JavaScript (we only test the MVC features, not an
> AJAX framework), canoo is the best option IMHO.
>
> For the moment I have created only one very basic test for the calc
> example. I'll do Bugzooky next.
>
> Cheers
>
> Remi
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.http://p.sf.net/sfu/novell-sfdev2dev
>
>
> _______________________________________________
> Stripes-development mailing
> [email protected]https://lists.sourceforge.net/lists/listinfo/stripes-development
>
>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Stripes-development mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stripes-development
>
>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
