new T5 project - can't find TML file
I'm starting a new T5 project, and am having some difficulty. For example, if I put my tml files alongside my java classes (com.mycompany.myproj.pages), when I startup my app, and navigate to a page, tapestry tells me that it cannot find the template file. If I then move the template file into my web dir, it can find it and everything seems to work. I don't want to put my template files in my web dir. Why is this not working for me?
testing Tapestry applications (in general)
We have been struggling (in my opinion) with a strategy to properly and completely test our web application (developed using Tapestry). We have some unit tests, but they are all centered on the code closer to the model. We have very few, if any, view and controller tests. We made some attempts in the past to write selenium tests, but for whatever reason, that did not catch on. We have also attempted to use WebDriver along with Geb, but continued to run into reliability issues with WebDriver and were frustrated with the inability of the WebDriver developers to settle on an API. Geb has some nice features to it, though. We very much would like to start writing view and controller tests. I was wondering what other Tapestry users are doing, as far as testing is concerned. What problems have you run into? What tools or approaches have you found that work especially well?
Re: testing Tapestry applications (in general)
I've found HTMLUnit, in the past to be utterly awful. At least with our web app (lots of ajax) HTMLUnit struggled and I ran into a lot of bugs. On Fri, Nov 4, 2011 at 9:18 AM, Kalle Korhonen kalle.o.korho...@gmail.comwrote: Your mileage may vary but for my perspective, see http://docs.codehaus.org/display/TYNAMO/2010/07/30/Full+web+integration+testing+in+a+single+JVM . For service level tests, I tend to use Mockito a lot. Kalle On Fri, Nov 4, 2011 at 7:01 AM, Markus Johnston tapes...@garstasio.com wrote: We have been struggling (in my opinion) with a strategy to properly and completely test our web application (developed using Tapestry). We have some unit tests, but they are all centered on the code closer to the model. We have very few, if any, view and controller tests. We made some attempts in the past to write selenium tests, but for whatever reason, that did not catch on. We have also attempted to use WebDriver along with Geb, but continued to run into reliability issues with WebDriver and were frustrated with the inability of the WebDriver developers to settle on an API. Geb has some nice features to it, though. We very much would like to start writing view and controller tests. I was wondering what other Tapestry users are doing, as far as testing is concerned. What problems have you run into? What tools or approaches have you found that work especially well? - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: testing Tapestry applications (in general)
Thanks for the info. I'll probably check out newer versions of HTMLUnit then, to see if it is an option for us. On Fri, Nov 4, 2011 at 12:48 PM, Kalle Korhonen kalle.o.korho...@gmail.comwrote: On Fri, Nov 4, 2011 at 10:25 AM, Markus Johnston tapes...@garstasio.com wrote: I've found HTMLUnit, in the past to be utterly awful. At least with our web app (lots of ajax) HTMLUnit struggled and I ran into a lot of bugs. Yeah, I've heard that a few times and my own experience in the past was also that HTMLUnit couldn't cope with the bigger Javascript stacks, however the newer versions (2.8, 2.9) manage to run current versions of Prototype, jQuery in my apps just fine. Kalle On Fri, Nov 4, 2011 at 9:18 AM, Kalle Korhonen kalle.o.korho...@gmail.comwrote: Your mileage may vary but for my perspective, see http://docs.codehaus.org/display/TYNAMO/2010/07/30/Full+web+integration+testing+in+a+single+JVM . For service level tests, I tend to use Mockito a lot. Kalle On Fri, Nov 4, 2011 at 7:01 AM, Markus Johnston tapes...@garstasio.com wrote: We have been struggling (in my opinion) with a strategy to properly and completely test our web application (developed using Tapestry). We have some unit tests, but they are all centered on the code closer to the model. We have very few, if any, view and controller tests. We made some attempts in the past to write selenium tests, but for whatever reason, that did not catch on. We have also attempted to use WebDriver along with Geb, but continued to run into reliability issues with WebDriver and were frustrated with the inability of the WebDriver developers to settle on an API. Geb has some nice features to it, though. We very much would like to start writing view and controller tests. I was wondering what other Tapestry users are doing, as far as testing is concerned. What problems have you run into? What tools or approaches have you found that work especially well? - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
