I think having the build run all test with both infrastructure provides is
a very good idea.
On Tue, 19 Nov 2013 21:17:18 -0200, Chris Poulsen <[email protected]>
wrote:
Hi,
I've just been tracking down a small ajaxformloop javascript error in
5.4,
it turned out that it only happens when using jquery as javascript
infrastructure provider.
While probing around to nail the error I tried the component in the
tapestry-core integration/app1 in both modes (jquery/prototype), seeing
that it only failed with jquery i got curious.
I tried running the core tests with the app1 module in jquery-mode, it
resulted in 21 errors (my ajaxformloop patch applied - don't know if that
would show up as a test failure as well), running the tests with
prototype
completes without any errors.
It would probably be a good thing to run all integration tests in both
modes on a regular basis to get the most out of the test suite.
Also visiting the app1/forminjectordemo in prototype mode results in a
browser console error about scriptaculous needs a newer prototype version
or something like that.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
