[seam-dev] the parody of mocks in JSF
Alexandr Smirnov
asmirnov at exadel.com
Tue May 5 19:22:33 EDT 2009
Ok, do you start that project ? RichFaces uses Shale mocks now, but I
wish to replace that with something more convenient. I can help with
development and contribute existing test classes from richfaces to the
new mocks project.
Dan Allen wrote:
> On Tue, May 5, 2009 at 1:09 PM, Alexandr Smirnov <asmirnov at exadel.com
> <mailto:asmirnov at exadel.com>> wrote:
>
> 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.
>
>
> Frankly, to me, that's what Seam is...our common module. I don't want to
> introduce some new, generic name. Seam is the JBoss middleware module
> set. It's no longer a container of any sort. Web Beans is now the core
> programming model and RichFaces is the UI component set and programming
> model. So by depending on Seam, you are doing nothing more than
> depending on a common module in JBoss. Hence the reason I want seam-mock.
>
> There are many needs for testing. I want to focus specifically in this
> module on completely standalone beans. No server logic. No real web
> calls or anything of the sort (*maybe* XML parsing in specialized
> subclasses). It is for unit testing, or as close to unit testing as you
> can get, with servlets and JSF APIs. We can of course have other
> modules. But this is the super lean one.
>
> ...and yes, let's be sure to leverage all prior work...and work together ;)
>
> Cheers,
>
> -Dan
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://in.relation.to/Bloggers/Dan
>
> 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 week,
> 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.
More information about the seam-dev
mailing list