http://blogs.steeplesoft.com/2009/03/announcing-facestester/ A brief interlude to share some (hopefully) cogent thoughts Mon, 08 Mar 2010 15:07:05 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://blogs.steeplesoft.com/2009/03/announcing-facestester/comment-page-1/#comment-8459 Kito D. Mann Thu, 26 Mar 2009 04:09:44 +0000 http://blogs.steeplesoft.com/?p=270#comment-8459 Very nice to see... so, what's the source of the mock objects? This has always been a big issue with Shale Test... (i.e. the mock objects are there, but the Shale folks won't work on it or let it move somewhere else.) Very nice to see… so, what’s the source of the mock objects? This has always been a big issue with Shale Test… (i.e. the mock objects are there, but the Shale folks won’t work on it or let it move somewhere else.)

]]> http://blogs.steeplesoft.com/2009/03/announcing-facestester/comment-page-1/#comment-8455 Dan Allen Fri, 06 Mar 2009 21:01:04 +0000 http://blogs.steeplesoft.com/?p=270#comment-8455 As green as it may be, you should do an alpha release so that it is easy for early adopters to try it. As green as it may be, you should do an alpha release so that it is easy for early adopters to try it.

]]> http://blogs.steeplesoft.com/2009/03/announcing-facestester/comment-page-1/#comment-8454 Dan Allen Fri, 06 Mar 2009 20:58:42 +0000 http://blogs.steeplesoft.com/?p=270#comment-8454 Good job. This is a level of granularity that is sorely needed. SeamTest is valuable when you need to perform transactional operations, such as persisting or retrieving an entry, but you are right in that SeamTest is too heavyweight when you are just interested in working on the JSF component tree. I do hope that we can share code, though, because as far as I know, SeamTest cannot build the JSF component tree. I also feel that it personally needs to be redesigned as a control class, like FacesTester, rather than through class extension. Good job. This is a level of granularity that is sorely needed. SeamTest is valuable when you need to perform transactional operations, such as persisting or retrieving an entry, but you are right in that SeamTest is too heavyweight when you are just interested in working on the JSF component tree. I do hope that we can share code, though, because as far as I know, SeamTest cannot build the JSF component tree. I also feel that it personally needs to be redesigned as a control class, like FacesTester, rather than through class extension.

]]>