Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_4.gdoc URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_4.gdoc?rev=1551048&r1=1551047&r2=1551048&view=diff ============================================================================== --- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_4.gdoc (original) +++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_4.gdoc Sun Dec 15 20:24:13 2013 @@ -2,7 +2,7 @@ With a component-oriented framework we can test our pages and components as we use to do with any other Java entity. Wicket offers a complete support for writing testing code, offering built-in tools to test nearly all the elements that build up our applications (pages, containers, links, behaviors, etc...). -The main entity discussed in this chapter has been class WicketTester which can be used to write unit tests and acceptance tests for our application, but we have also seen how to test forms with FormTester and how to inspect markup with TagTester. +The main entity discussed in this chapter has been class @WicketTester@ which can be used to write unit tests and acceptance tests for our application, but we have also seen how to test forms with @FormTester@ and how to inspect markup with @TagTester@. In addition to learning how to use the utility classes provided by Wicket for testing, we have also experienced the innovative approach of Wicket to web testing that allows to test components in isolation without the need of running our tests with a web server and depending only on JUnit as testing framework.
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter22/chapter22_8.gdoc URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter22/chapter22_8.gdoc?rev=1551048&r1=1551047&r2=1551048&view=diff ============================================================================== --- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter22/chapter22_8.gdoc (original) +++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter22/chapter22_8.gdoc Sun Dec 15 20:24:13 2013 @@ -1,6 +1,6 @@ -Always try to pass models on to the parent component. By that, you ensure that at the end of every request the method @IModel.detach()@ gets called. This method is responsible for a data cleanup. Another example: you have implemented your own model which persists the data in the @detach()@ method. So the call of @detach()@ is neccessary for that your data gets persisted. You can see an exemplary passing to the super constructor here: +Always try to pass models on to the parent component. By that, you ensure that at the end of every request the method @IModel.detach()@ gets called. This method is responsible for a data cleanup. Another example: you have implemented your own model which persists the data in the @detach()@ method. So the call of @detach()@ is necessary for that your data gets persisted. You can see an exemplary passing to the super constructor here: *Listing 11:*
