Are you using "mock objects" to get the database (it won't really come from the database when mocking of course) information in your test cases?
On Wed, Dec 22, 2010 at 9:22 AM, lchalupa <[email protected]> wrote: > > Hello: > I am developing a spring/hibernate wicket application where I can configure > the components on each page at runtime. The component configuration specs > are kept in the database. For example the home page has no components in it > when it is created on the file system. When the home page is instantiated, > there is code in the constructor of the page that gets the configuration > spec from the database and builds the components in the page accordingly. > The goal is serve multiple clients with this shared application and maintain > one source tree. > > I'm having trouble figuring out how to use WicketTester in this application. > For example, the startPage method... what state does this method leave the > page in when it has completed it's work? I was planning to use WicketTester > to create the pages I want to test outside of the container. As of now this > is not working. > There are properties in my page objects that are not getting instantiated in > the test environment. > > Does anyone have any advice on how to fix this? > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Testing-Pages-with-WicketTester-tp3160709p3160709.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
