[jboss-cvs] jboss-seam/doc/reference/en/modules ...

[Gavin King]

  User: gavin   
  Date: 06/10/26 10:01:40

  Modified:    doc/reference/en/modules  testing.xml
  Log:
  update
  
  Revision  Changes    Path
  1.9       +8 -7      jboss-seam/doc/reference/en/modules/testing.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: testing.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/testing.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -b -r1.8 -r1.9
  --- testing.xml	12 Jul 2006 23:14:33 -0000	1.8
  +++ testing.xml	26 Oct 2006 14:01:40 -0000	1.9
  @@ -189,7 +189,7 @@
      public void testRegister() throws Exception
      {
               
  -      new Script() {
  +      new FacesRequest() {
   
            @Override
            protected void updateModelValues() throws Exception
  @@ -206,7 +206,7 @@
            {
               Register register = (Register) Component.getInstance("register", true);
               String outcome = register.register();
  -            assert "success".equals( outcome );
  +            assert "success".equals(outcome);
            }
   
            @Override
  @@ -230,11 +230,12 @@
           <para>
               Notice that we've extended <literal>SeamTest</literal>, which provides a 
               Seam environment for our components, and written our test script as an 
  -            anonymous class that extends <literal>SeamTest.Script</literal>, which 
  -            provides an emulated JSF request lifecycle. We've written our code in 
  -            methods which are named for the various JSF phases, to emulate the calls 
  -            that JSF would make to our components. Then we've thrown in various 
  -            assertions.
  +            anonymous class that extends <literal>SeamTest.FacesRequest</literal>, 
  +            which provides an emulated JSF request lifecycle. (There is also a
  +            <literal>SeamTest.NonFacesRequest</literal> for testing GET requests.)
  +            We've written our code in methods which are named for the various JSF 
  +            phases, to emulate the calls that JSF would make to our components. Then 
  +            we've thrown in various assertions.
           </para>
           
           <para>