Hi Dan, We are building a corporate application using the ISIS framework as is (JDO, Wicket viewer) and it is going well.
However the unfinished JUnit wrapper poses a problem for us in the long run. Keen to see it completed (that's a vote fromme). Unfortunately I can't publish the source for this particular application as it is not mine. Maybe port the "Car Serv" application from your book to ISIS ? Regards, David. > With respect to the JUnit viewer, at the moment it focuses on testing the > UI/domain interaction, and just using an in-memory objectstore. > Separately, there is IsisSystemForTest [4], which can be used to bootstrap > an Isis runtime for domain/DB integration (via the JDO objectstore) > What I want to do is to combine these frameworks into a single JUnit > framework, which allows domain/DB integration and optionally allows the > full-stack UI/domain/DB integration too. This is the main reason I > haven't released the JUnit viewer yet since us becoming a TLP. > With respect to the BDD viewer, I think this also needs to work the same > way; and it probably should be made part of the same single framework. So, > then it's one integration testing stack for domain/DB testing, optionally > testing the UI interaction through the existing JUnit viewer stuff or > through the BDD viewer stuff.
