The RichFaces test project has little bit more then simple mock objects;
it simulates a real web server which works with any JSF implementation,
and has integration with HtmlUnit as well, so it can be used for
functional and compatibility tests. I've been created that project
especially for JSF 2.0 tests ( because there are no mock projects for
JSF 2.0 api yet, and API was changing too often ). But that project
really has no JSF or RichFaces dependencies, therefore it could be used
to test any web framework, including Seam as well.
But using real implementation for simple test seems overloaded,
therefore it makes sense to combine 'staging' server with mock objects
too. Because that test environment has no direct references to
particular framework, we can make an independent test project,
applicable for both RichFaces and Seam.
Because we already have at least two candidates for common libraries (
that are tests and bean validators, the CDK seems as third ), I think we
should create 'common' module that will holds all shared libraries for
Jboss Seam and RichFaces projects.
Pete Muir wrote:
Can we share these mocks like we discussed for graph validation - RF
imports the module from the "Seam" space - but the Seam module doesn't
depend on other Seam code?
On 30 Apr 2009, at 15:13, Jay Balunas wrote:
> You may also want to check out
> Alex Smirnov has been working on this to help with RF 4.0
> development. Perhaps we can collaborate.
> On Wed, Apr 29, 2009 at 11:10 AM, Dan Allen <dan.j.allen(a)gmail.com>
> It's hard to believe that for as long as JSF has been around, the only
> decent repository of mocks for the JSF API comes not from the
> implementation, but rather from all but dead and irrelevant project at
> Apache (Shale). Of course, Seam 2 forged it's own path and has a
> healthy set of mocks, although still somewhat incomplete and vagrant.
> In the Seam 3 spirit of modularity, I would like to migrate the Seam 2
> mocks into a mock module in Seam 3 that provides mock/stub object for
> various Java EE APIs. I plan to categorize them by spec under the
> org.jboss.seam.mock folder
> JSF - org.jboss.seam.mock.faces
> Servlet - org.jboss.seam.mock.servlet
> This module should not depend on any other module so that it is easy
> to reuse, perhaps even outside of the Seam framework. Perhaps
> seam-mock can end up replacing Shale test. Who knows. We'll just let
> it play out. Please contribute your ideas/use cases!
> As for the functionality, my feeling is that the mocks should be
> functional as long as each class behaves like a bean. That means it
> shouldn't parse XML documents or make similar assumptions. But they
> should be easy enough to extend that perhaps you can add that
> functionality in your test case or we can think about providing an
> additional subclass or helper if the need is common (perhaps parsing
> an web.xml document).
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> NOTE: While I make a strong effort to keep up with my email on a daily
> basis, personal or other work matters can sometimes keep me away
> from my email. If you contact me, but don't hear back for more than a
> it is very likely that I am excessively backlogged or the message was
> caught in the spam filters. Please don't hesitate to resend a message if
> you feel that it did not reach my attention.
> seam-dev mailing list
> blog: http://in.relation.to/Bloggers/Jay
> seam-dev mailing list