Great news Jim!<br><br>Our focus on improvements in 2.0 clearly had a big impact based on the reaction of the audience at JSF Summit. The flipside is that with many (if not all) of the high profile problems solved or with pending solutions, people have immediately turned towards asking about performance. It will be great to be able to point them at something.<br>
<br>The Seam QA team has used selenium quite extensively and found it reasonably pleasant. Perhaps Jay Balunus can speak more to the experience since he helped get it all setup. They had a talk on a Tellenium at Rich Web, which appears to be a stack on top of Selenium, but I don&#39;t know much about it: <a href="http://code.google.com/p/aost/">http://code.google.com/p/aost/</a><br>
<br>I think OSS is definitely a prerequiste here so that we can all participate in running the tests if we want.<br><br>-Dan<br><br><div class="gmail_quote">On Tue, Dec 8, 2009 at 1:31 PM, Jim Driscoll <span dir="ltr">&lt;<a href="mailto:Jim.Driscoll@sun.com">Jim.Driscoll@sun.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">So, I&#39;ve been thinking about measuring relative performance, and I think that what we may want to do is to try to get JSF into the next specweb standard.  There are currently ASPX, PHP and JSP in the standard. <a href="http://www.spec.org/web2009/" target="_blank">http://www.spec.org/web2009/</a><br>

<br>
We&#39;ll see what Sun&#39;s performance guys say.<br>
<br>
That would allow us to 1) compare JSF implementations for performance (always useful), and 2) compare JSF releases for performance, to guard against performance degradation from spec changes (very, very useful).<br>
<br>
We&#39;ll also want to port over some subset of the tests to something like Wicket.  It also might be fun/interesting to port over some tests to Rails as well.  I expect that Wicket may have some advantage in some cases, since the programmer creates the tree, rather than the framework - but then, I can also write things faster using an assembler, for much the same reason, with some of the same problems.  I also expect that we&#39;ll find a few very obvious places to boost speed - we&#39;ve been mostly striving for correctness in 2.0.<br>

<br>
Ajax tests, otoh, are likely to be much, much harder.  There are commercial products, like the <a href="http://neotys.com" target="_blank">neotys.com</a> one that Ted mentioned, but I don&#39;t have to tell you that my budget for this is $0 - maybe that can change, but I suspect I&#39;ll be writing client scripts and using Selenium.  Ick.<br>

<br>
Anyhow, it&#39;s a long term project, and I wanted to update you on my thinking, and seek feedback.<br><font color="#888888">
<br>
Jim<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>