We recently had a few browser specific issues, http://issues.apache.org/jira/browse/TAPESTRY-1141 (already fixed) http://issues.apache.org/jira/browse/TAPESTRY-1129 (same as an old tacos bug, i.e. fix is already known)
Now, i wouldn't like closing them without some sort of browser specific testing (since the issues are such).... In tacos we had added several selenium based tests that we would manually run in every major browser now and then. Even though they weren't integrated in the build process, i really enjoyed (and still do ) the confidence they provide. Now i've seen a bit of Howard's code that interacts with selenium programatically and: - Can we use a similar approach? - Are those tests integrated with maven? - Who actually runs them? (a browser? rhino?) - Any other approach? -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
