Revision: 664
http://svn.sourceforge.net/jwebunit/?rev=664&view=rev
Author: henryju
Date: 2007-01-27 11:12:06 -0800 (Sat, 27 Jan 2007)
Log Message:
-----------
Update documentation.
Modified Paths:
--------------
branches/1.x/jwebunit-htmlunit-plugin/src/site/xdoc/index.xml
branches/1.x/src/site/fml/faq.fml
branches/1.x/src/site/site.xml
branches/1.x/src/site/xdoc/building-maven.xml
branches/1.x/src/site/xdoc/installation.xml
branches/1.x/src/site/xdoc/quickstart.xml
Added Paths:
-----------
branches/1.x/src/site/xdoc/articles.xml
Modified: branches/1.x/jwebunit-htmlunit-plugin/src/site/xdoc/index.xml
===================================================================
--- branches/1.x/jwebunit-htmlunit-plugin/src/site/xdoc/index.xml
2007-01-22 15:49:52 UTC (rev 663)
+++ branches/1.x/jwebunit-htmlunit-plugin/src/site/xdoc/index.xml
2007-01-27 19:12:06 UTC (rev 664)
@@ -2,7 +2,7 @@
<document>
<properties>
<author email="dashorst.at.users.sourceforge.net">Martijn
Dashorst</author>
- <title>jWebUnit</title>
+ <title>JWebUnit</title>
</properties>
<meta name="keyword" content="jwebunit, java, junit, htmlunit, jacobie,
httpunit, integration, test, automated, html, webtest"/>
<head>
@@ -11,15 +11,15 @@
<body>
<section name="HtmlUnit plugin">
<p>
- The following sample testcases illustrate the conciseness of jWebUnit
versus HtmlUnit
+ The following sample testcases illustrate the conciseness of JWebUnit
versus HtmlUnit
and JUnit alone. The tests perform a google search
for the HtmlUnit home page, navigate to that page from Google, and
validate that
there is a link to the user manual on the HtmlUnit home page. The
code in the
- first column is pure HtmlUnit / JUnit, while the second column uses
the jWebUnit framework.
+ first column is pure HtmlUnit / JUnit, while the second column uses
the JWebUnit framework.
</p>
<p>
<table cellspacing="2" border="0">
-<tr><th>JUnit/HtmlUnit Test</th><th>jWebUnit Test</th></tr>
+<tr><th>JUnit/HtmlUnit Test</th><th>JWebUnit Test</th></tr>
<tr>
<td valign="top" nowrap="nowrap">
<source>
@@ -67,7 +67,7 @@
public void testSearch() throws Exception {
beginAt("/");
- setFormElement("q", "htmlunit");
+ setTextField("q", "htmlunit");
submit("btnG");
clickLinkWithText("HtmlUnit");
assertTitleEquals("htmlunit - Welcome to HtmlUnit");
@@ -90,7 +90,7 @@
<dependency>
<groupId>net.sourceforge.jwebunit</groupId>
<artifactId>jwebunit-htmlunit-plugin</artifactId>
- <version>1.3-SNAPSHOT</version>
+ <version>1.4-rc3</version>
</dependency>
...
</dependencies>
Modified: branches/1.x/src/site/fml/faq.fml
===================================================================
--- branches/1.x/src/site/fml/faq.fml 2007-01-22 15:49:52 UTC (rev 663)
+++ branches/1.x/src/site/fml/faq.fml 2007-01-27 19:12:06 UTC (rev 664)
@@ -1,42 +1,38 @@
<?xml version="1.0" encoding="UTF-8"?>
<faqs title="Frequently Asked Questions">
- <part id="general">
- <title>General</title>
+ <part id="JavaScript">
+ <title>JavaScript</title>
- <faq id="whats-foo">
+ <faq id="javascript-support">
<question>
- What is Foo?
+ What about JWebUnit support of JavaScript?
</question>
<answer>
- <p>some markup goes here</p>
-
- <source>some source code</source>
-
- <p>some markup goes here</p>
+ <p>JWebUnit uses a testing engine to manipulate DOM and JavaScript.
That's why
+JavaScript support depend on the testing engine. In the past, JWebUnit was
based on HttpUnit.
+JavaScript support of HttpUnit is very poor.<br/>
+Now, JWebUnit main testing engine is HtmlUnit. HtmlUnit understanding of
JavaScript is quite good.</p>
</answer>
</faq>
- <faq id="whats-bar">
+ <faq id="javascript-errors">
<question>
- What is Bar?
+ What can I do when JavaScript errors are thrown with JWebUnit (and
HtmlUnit testing engine), but not in my browser?
</question>
<answer>
- <p>some markup goes here</p>
+ <p>First, check if your JavaScript is not browser specific. When
possible, try to write a minimal test case that reproduce your error, and
submit it to the HtmlUnit team to help them to improve HtmlUnit.<br/>
+Finally, you can temporary disable JavaScript in your test:</p>
+ <source>public void testFoo() {
+ beginAt("blabla");
+ ...
+ setScriptingEnabled(false);
+ ...//Problematic code
+ setScriptingEnabled(true);
+ ...
+}</source>
</answer>
</faq>
</part>
- <part id="install">
- <title>Installation</title>
-
- <faq id="how-install">
- <question>
- How do I install Foo?
- </question>
- <answer>
- <p>some markup goes here</p>
- </answer>
- </faq>
- </part>
</faqs>
\ No newline at end of file
Modified: branches/1.x/src/site/site.xml
===================================================================
--- branches/1.x/src/site/site.xml 2007-01-22 15:49:52 UTC (rev 663)
+++ branches/1.x/src/site/site.xml 2007-01-27 19:12:06 UTC (rev 664)
@@ -29,6 +29,8 @@
</links>
<menu name="JWebUnit">
<item name="Home" href="/index.html" />
+ </menu>
+ <menu name="User documentation">
<item name="Installation" href="/installation.html"
collapse="true">
</item>
@@ -51,18 +53,23 @@
<item name="Using Property Files"
href="#Using Property Files to Validate Content" />
</item>
+ <item name="Articles" href="/articles.html" />
+ <item name="FAQ" href="/faq.html" />
</menu>
- <menu name="Building JWebUnit">
- <item name="With Maven" href="/building-maven.html"
- collapse="true">
- <item name="Installing Maven"
- href="#Installing Maven" />
- <item name="Using Maven"
- href="#Using Maven" />
- <item name="Building jWebUnit"
- href="#Building jWebUnit" />
- <item name="Building an assembly"
- href="#Building an assembly" />
+ <menu name="Developper documentation">
+ <item name="Building JWebUnit with Maven 2"
+ href="/building-maven.html" collapse="true">
+ <item name="Installing Maven" href="#Installing Maven" />
+ <item name="Using Maven" href="#Using Maven" />
+ <item name="Installing not released or snapshot plugins"
+ href="#Installing not released or snapshot plugins" />
+ <item name="Building JWebUnit"
+ href="#Building JWebUnit" />
+ <item name="Building Sourceforge upload bundle"
+ href="#Building Sourceforge upload bundle" />
+ <item name="Building JWebUnit Web site and reports"
+ href="#Building JWebUnit Web site and reports" />
+
</item>
</menu>
<menu name="Sourceforge">
Added: branches/1.x/src/site/xdoc/articles.xml
===================================================================
--- branches/1.x/src/site/xdoc/articles.xml (rev 0)
+++ branches/1.x/src/site/xdoc/articles.xml 2007-01-27 19:12:06 UTC (rev
664)
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<document>
+ <properties>
+ <author>Julien Henry</author>
+ <title>Articles</title>
+ </properties>
+<body class="default">
+<section name="Articles about JWebUnit">
+ <p>Some articles from Johannes Brodwall</p>
+ <a
href="http://www.brodwall.com/johannes/blog/2006/12/10/in-process-web-integration-tests-with-jetty-and-jwebunit/";>http://www.brodwall.com/johannes/blog/2006/12/10/in-process-web-integration-tests-with-jetty-and-jwebunit/</a>
+ <a
href="http://www.brodwall.com/johannes/blog/2007/01/20/article-ready-for-edit-embedded-web-integration-testing-with-jetty/";>http://www.brodwall.com/johannes/blog/2007/01/20/article-ready-for-edit-embedded-web-integration-testing-with-jetty/</a>
+</section>
+</body>
+</document>
\ No newline at end of file
Modified: branches/1.x/src/site/xdoc/building-maven.xml
===================================================================
--- branches/1.x/src/site/xdoc/building-maven.xml 2007-01-22 15:49:52 UTC
(rev 663)
+++ branches/1.x/src/site/xdoc/building-maven.xml 2007-01-27 19:12:06 UTC
(rev 664)
@@ -1,176 +1,189 @@
<?xml version="1.0"?>
<document>
- <properties>
- <author>Julien Henry</author>
- <title>Building jWebunit</title>
- </properties>
-<body class="default">
-<section name="Building jWebUnit with Maven 2">
- <p>
- Maven is, just like ant, a build tool. However, where you have
to tell ant what it
- needs to do and how, you only have to tell Maven what you need,
if you adhere to the
- Maven standards.
- </p>
- <p>
- In order to use Maven to build jWebUnit, you need to have Maven
2 installed. This should
- not be any more difficult than installing ant. We've included a
best practise installation
- and configuration for Maven.
- </p>
-<subsection name="Installing Maven">
- <p>
- First you need to download the latest Maven 2, which currently
is <a href="http://maven.apache.org";><tt>Maven-2.0.4</tt></a>,
- make sure you download the binary archive (maven-2.0.4-bin.zip).
- </p>
- <p>
- Installing Maven should be easy: unzip the file to any
directory you like, let's say:
- <source>C:\maven-2.0.4</source>
- </p>
- <p>
- Next you need to do 2 things:
- <ul>
- <li>add an environment variable MAVEN_HOME which points
to the install directory of Maven, i.e. C:\maven-2.0.4</li>
- <li>add <tt>%MAVEN_HOME%\bin</tt> to your path (using
the variable you can switch more easily when a new version arrives)</li>
- </ul>
- </p>
-</subsection>
-<subsection name="Using Maven">
- <p>
- Maven defines several goals, for
- creating and building your application. A goal is similar to an
Ant-task. For
- instance: to compile the java sources one could do:
- <source>mvn compile</source>
- Also, a goal can depend on other goals: the <tt>package</tt>
goal depends on
- running the unit tests and compilation of the code.
- </p>
- <p>
- See the <a href="http://maven.apache.org";>Maven site</a> for
more information
- on the different goals and plugins that are available.
- </p>
-</subsection>
-<subsection name="Building jWebUnit">
- <p>
- Building jWebUnit merely consist of running Maven:
- <source>mvn package</source>
- If you build jWebUnit and you configured Maven as described
- earlier, you will see the following text:
-<source><![CDATA[
-$ mvn package
-[INFO] Scanning for projects...
-[INFO] Reactor build order:
-[INFO] jWebUnit
-[INFO] Core - API
-[INFO] Commons Tests
-[INFO] HtmlUnit Plugin
-[INFO]
----------------------------------------------------------------------------
-[INFO] Building jWebUnit
-[INFO] task-segment: [package]
-[INFO]
----------------------------------------------------------------------------
-[INFO] [site:attach-descriptor]
-[INFO]
----------------------------------------------------------------------------
-[INFO] Building Core - API
-[INFO] task-segment: [package]
-[INFO]
----------------------------------------------------------------------------
-[INFO] [resources:resources]
-[INFO] Using default encoding to copy filtered resources.
-[INFO] [compiler:compile]
-Compiling 14 source files to
/home/julien/jwebunit-1.x/jwebunit-core/target/classes
-[INFO] [resources:testResources]
-[INFO] Using default encoding to copy filtered resources.
-[INFO] [compiler:testCompile]
-Compiling 1 source file to
/home/julien/jwebunit-1.x/jwebunit-core/target/test-classes
-[INFO] [surefire:test]
-[INFO] Surefire report directory:
/home/julien/jwebunit-1.x/jwebunit-core/target/surefire-reports
-
--------------------------------------------------------
- T E S T S
--------------------------------------------------------
-Running net.sourceforge.jwebunit.TableTest
-Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 sec
-
-Results :
-Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
-
-[INFO] [jar:jar]
-[INFO] Building jar:
/home/julien/jwebunit-1.x/jwebunit-core/target/jwebunit-core-1.3.jar
-[INFO]
----------------------------------------------------------------------------
-[INFO] Building Commons Tests
-[INFO] task-segment: [package]
-[INFO]
----------------------------------------------------------------------------
-[INFO] [resources:resources]
-[INFO] Using default encoding to copy filtered resources.
-[INFO] [compiler:compile]
-Compiling 23 source files to
/home/julien/jwebunit-1.x/jwebunit-commons-tests/target/classes
-[INFO] [resources:testResources]
-[INFO] Using default encoding to copy filtered resources.
-[INFO] [compiler:testCompile]
-Compiling 1 source file to
/home/julien/jwebunit-1.x/jwebunit-commons-tests/target/test-classes
-[INFO] [surefire:test]
-[INFO] Surefire report directory:
/home/julien/jwebunit-1.x/jwebunit-commons-tests/target/surefire-reports
-
--------------------------------------------------------
- T E S T S
--------------------------------------------------------
-Running net.sourceforge.jwebunit.tests.util.reflect.MethodInvokerTest
-Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.077 sec
-
-Results :
-Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
-
-[INFO] [jar:jar]
-[INFO] Building jar:
/home/julien/jwebunit-1.x/jwebunit-commons-tests/target/jwebunit-commons-tests-1.3.jar
-[INFO]
----------------------------------------------------------------------------
-[INFO] Building HtmlUnit Plugin
-[INFO] task-segment: [package]
-[INFO]
----------------------------------------------------------------------------
-[INFO] [resources:resources]
-[INFO] Using default encoding to copy filtered resources.
-[INFO] [compiler:compile]
-Compiling 1 source file to
/home/julien/jwebunit-1.x/jwebunit-htmlunit-plugin/target/classes
-[INFO] [resources:testResources]
-[INFO] Using default encoding to copy filtered resources.
-[INFO] [compiler:testCompile]
-Compiling 1 source file to
/home/julien/jwebunit-1.x/jwebunit-htmlunit-plugin/target/test-classes
-[INFO] [surefire:test]
-[INFO] Surefire report directory:
/home/julien/jwebunit-1.x/jwebunit-htmlunit-plugin/target/surefire-reports
-
--------------------------------------------------------
- T E S T S
--------------------------------------------------------
-Running net.sourceforge.jwebunit.htmlunit.JWebUnitTest
-:INFO: Logging to STDERR via org.mortbay.log.StdErrLog
-:INFO: jetty 6.0.0beta16
-:INFO: Extract
jar:file:/home/julien/jwebunit-1.x/jwebunit-commons-tests/target/jwebunit-commons-tests-1.3.jar!/testcases/
to /tmp/Jetty__jwebunit/webapp
-:INFO: NO JSP Support for /jwebunit, did not find
org.apache.jasper.servlet.JspServlet
-:INFO: Started SocketConnector @ 0.0.0.0:8082
-Tests run: 162, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.877 sec
-
-Results :
-Tests run: 162, Failures: 0, Errors: 0, Skipped: 0
-
-[INFO] [jar:jar]
-[INFO] Building jar:
/home/julien/jwebunit-1.x/jwebunit-htmlunit-plugin/target/jwebunit-htmlunit-plugin-1.3.jar
-[INFO]
-[INFO]
-[INFO] ------------------------------------------------------------------------
-[INFO] Reactor Summary:
-[INFO] ------------------------------------------------------------------------
-[INFO] jWebUnit .............................................. SUCCESS [2.922s]
-[INFO] Core - API ............................................ SUCCESS [5.128s]
-[INFO] Commons Tests ......................................... SUCCESS [3.416s]
-[INFO] HtmlUnit Plugin ....................................... SUCCESS
[12.735s]
-[INFO] ------------------------------------------------------------------------
-[INFO] ------------------------------------------------------------------------
-[INFO] BUILD SUCCESSFUL
-[INFO] ------------------------------------------------------------------------
-[INFO] Total time: 24 seconds
-[INFO] Finished at: Fri Jul 28 20:28:48 CEST 2006
-[INFO] Final Memory: 8M/19M
-[INFO] ------------------------------------------------------------------------
-]]></source></p>
- <p>
- You now have successfully built jWebUnit 1.3. The files are in
target/ folder.
- </p>
-</subsection>
-</section>
-</body>
+ <properties>
+ <author>Julien Henry</author>
+ <title>Building JWebUnit</title>
+ </properties>
+ <body class="default">
+ <section name="Building JWebUnit with Maven 2">
+ <p>
+ Maven is, just like ant, a build tool. However, where
+ you have to tell ant what it needs to do and how, you
+ only have to tell Maven what you need, if you adhere to
+ the Maven standards.
+ </p>
+ <p>
+ In order to use Maven to build JWebUnit, you need to
+ have Maven 2 installed. This should not be any more
+ difficult than installing ant. We've included a best
+ practise installation and configuration for Maven.
+ </p>
+ <subsection name="Installing Maven">
+ <p>
+ First you need to download the latest Maven 2, which
+ currently is
+ <a href="http://maven.apache.org";>
+ <tt>Maven-2.0.4</tt>
+ </a>
+ , make sure you download the binary archive
+ (maven-2.0.4-bin.zip).
+ </p>
+ <p>
+ Installing Maven should be easy: unzip the file to
+ any directory you like, let's say:
+ <source>C:\maven-2.0.4</source>
+ </p>
+ <p>
+ Next you need to do 2 things:
+ <ul>
+ <li>
+ add an environment variable MAVEN_HOME which
+ points to the install directory of Maven,
+ i.e. C:\maven-2.0.4
+ </li>
+ <li>
+ add
+ <tt>%MAVEN_HOME%\bin</tt>
+ to your path (using the variable you can
+ switch more easily when a new version
+ arrives)
+ </li>
+ </ul>
+ </p>
+ </subsection>
+ <subsection name="Using Maven">
+ <p>
+ Maven defines several goals, for creating and
+ building your application. A goal is similar to an
+ Ant-task. For instance: to compile the java sources
+ one could do:
+ <source>mvn compile</source>
+ Also, a goal can depend on other goals: the
+ <tt>package</tt>
+ goal depends on running the unit tests and
+ compilation of the code.
+ </p>
+ <p>
+ See the
+ <a href="http://maven.apache.org";>Maven site</a>
+ for more information on the different goals and
+ plugins that are available.
+ </p>
+ </subsection>
+ <subsection
+ name="Installing not released or snapshot plugins">
+ <p>
+ JWebUnit needs some bleeding edge Maven plugins to
+ build properly.
+ </p>
+ <ul>
+ <li>
+ exec-maven-plugin-1.1-SNAPSHOT from
+ <a
+ href="http://snapshots.repository.codehaus.org/";>
+ Codehaus Snapshot Repository
+ </a>
+ </li>
+ <li>
+ javacc-maven-plugin build from SVN + patch for
+ this
+ <a
+ href="http://jira.codehaus.org/browse/MJAVACC-20";>
+ issue
+ </a>
+ </li>
+ <li>
+ [cosmetic] maven-javadoc-plugin from SVN + 2
+ patches.
+ <a
+
href="http://jira.codehaus.org/browse/MJAVADOC-105";>
+ issue 1
+ </a>
+ ,
+ <a
+
href="http://jira.codehaus.org/browse/MJAVADOC-104";>
+ issue 2
+ </a>
+ </li>
+ <li>
+ [only required to build SF packages]
+ maven-assembly-plugin-2.2-SNAPSHOT from
+ <a
+
href="http://people.apache.org/maven-snapshot-repository//";>
+ Maven Snapshot Repository
+ </a>
+ </li>
+ </ul>
+ <p>
+ I'm affraid as long these patchs are not applied and
+ plugins are not released, JWebUnit builds are not
+ reproductible. You can vote for these issues or spam
+ the Maven mailing list to help. ;)
+ </p>
+ <p>
+ Installation of javacc-maven-plugin:
+ <br />
+ You need at least jdk1.5 !!!
+ </p>
+ <source>
+$ svn co
+https://svn.codehaus.org/mojo/trunk/mojo/javacc-maven-plugin/
+$ cd javacc-maven-plugin $ patch -p0 < maven-javacc.patch patching file
+src/main/java/org/codehaus/mojo/javacc/JavaCCMojo.java
+$ mvn clean install
+ </source>
+ <p>
+ Installation of exec-maven-plugin-1.1-SNAPSHOT
+ <br />
+ Alternativly, you can add Codehaus Snapshot
+ Repository to your settings.xml, but it may mess
+ your repository by downloading and using not
+ intended SNAPSHOTS. That's why I suggest you install
+ manually the required SNAPSHOT.
+ </p>
+ <source>
+$ svn co
+https://svn.codehaus.org/mojo/trunk/mojo/exec-maven-plugin/
+$ cd exec-maven-plugin $ mvn clean install
+ </source>
+ <p>
+ Installation of maven-assembly-plugin-2.2-SNAPSHOT
+ <br />
+ You have to add Maven Snapshot Repository to your
+ settings.xml, but it could mess your repository by
+ downloading and using not intended SNAPSHOTS.
+ </p>
+ </subsection>
+ <subsection name="Building JWebUnit">
+ <p>
+ Building JWebUnit merely consist of running Maven:
+ <source>mvn install</source>
+ </p>
+ <p>
+ You now have successfully built JWebUnit. The files
+ are in your private repository.
+ </p>
+ </subsection>
+ <subsection name="Building Sourceforge upload bundle">
+ <p>
+ For those who don't want to use Maven, we have to
+ provide a zip with all required files.
+ <source>mvn package assembly:assembly</source>
+ </p>
+ <p>The files are in target directory.</p>
+ </subsection>
+ <subsection name="Building JWebUnit Web site and reports">
+ <p>
+ Due to findbugs memory usage, following parameter is required:
+ <source>export MAVEN_OPTS=-Xmx384M</source>
+ Now you should be able to generate site:
+ <source>mvn site:site</source>
+ </p>
+ <p>The files are in target/site directory of each module.<br/>
+ If you want to test the final assembled site, just hit:</p>
+ <source>mvn site:stage -DstagingDirectory=C:\fullsite</source>
+ <p>You can of course customize the destination folder of the
assembled site.</p>
+ </subsection>
+ </section>
+ </body>
</document>
\ No newline at end of file
Modified: branches/1.x/src/site/xdoc/installation.xml
===================================================================
--- branches/1.x/src/site/xdoc/installation.xml 2007-01-22 15:49:52 UTC (rev
663)
+++ branches/1.x/src/site/xdoc/installation.xml 2007-01-27 19:12:06 UTC (rev
664)
@@ -5,7 +5,7 @@
<title>Installation</title>
</properties>
<body class="default">
-<section name="jWebUnit Installation">
+<section name="JWebUnit Installation">
<subsection name="Using Maven">
<p>
If your project use Maven 2, it's very simple. Just add
the plugin you want as dependency:
@@ -17,12 +17,12 @@
<groupId>com.compagny.myproject</groupId>
<artifactId>myproject</artifactId>
<version>0.0.1</version>
- <description>A wonderful project using jWebUnit</description>
+ <description>A wonderful project using JWebUnit</description>
<dependencies>
<dependency>
<groupId>net.sourceforge.jwebunit</groupId>
<artifactId>jwebunit-htmlunit-plugin</artifactId>
- <version>1.3</version>
+ <version>1.4-rc3</version>
<scope>test</scope>
</dependency>
</dependencies>
@@ -32,7 +32,7 @@
<subsection name="Download">
<p>
If you don't want to use Maven, you can download files
manually.
- First download latest stable version of jWebUnit from
the <a href="http://sourceforge.net/projects/jwebunit/files";>files area</a>
+ First download latest stable version of JWebUnit from
the <a href="http://sourceforge.net/projects/jwebunit/files";>files area</a>
and expand to a local directory.
</p>
</subsection>
@@ -54,7 +54,7 @@
<p>
If you don't want to migrate to Maven,
make sure you add the jwebunit-htmlunit-plugin-1.3.jar,
jwebunit-core-1.3.jar and all HtmlUnit dependencies
-(these files are in lib/ folder of the jWebUnit package) to your classpath in
your IDE.
+(these files are in lib/ folder of the JWebUnit package) to your classpath in
your IDE.
</p>
</subsection>
</section>
Modified: branches/1.x/src/site/xdoc/quickstart.xml
===================================================================
--- branches/1.x/src/site/xdoc/quickstart.xml 2007-01-22 15:49:52 UTC (rev
663)
+++ branches/1.x/src/site/xdoc/quickstart.xml 2007-01-27 19:12:06 UTC (rev
664)
@@ -5,11 +5,11 @@
<title>Quick Start</title>
</properties>
<body class="default">
-<section name="jWebUnit Quickstart">
+<section name="JWebUnit Quickstart">
<p>
The QuickStart contains sample code and guidance to get you started with
JWebUnit. To see all
of the methods available, consult the a <a
href="apidocs/index.html">Javadocs</a> - particularly
- the WebTester class for full documentation.
+ the WebTestCase class for full documentation.
</p>
<subsection name="Creating a TestCase">
<p>
@@ -44,7 +44,7 @@
</subsection>
<subsection name="Selecting the plugin you want to use">
<p>
- jWebUnit can use different plugins to execute the tests you write. Only
one line makes the difference:
+ JWebUnit can use different plugins to execute the tests you write. Only
one line makes the difference:
<source>
import net.sourceforge.jwebunit.WebTestCase;
import net.sourceforge.jwebunit.TestingEngineRegistry;
@@ -121,8 +121,8 @@
assertFormPresent("expectedFormName");
assertFormElementPresent("field1");
assertFormElementEquals("field2", "field2_defaultValue");
- setFormElement("field1", "value1");
- setFormElement("fieldn", "valuen");
+ setTextField("field1", "value1");
+ setTextField("fieldn", "valuen");
submit();
}
</source>
@@ -133,11 +133,11 @@
assertFormPresent("expectedFormName");
assertSubmitButtonPresent("Add");
assertSubmitButtonPresent("Modify");
- setFormElement("field1", "value1");
+ setTextFieldElement("field1", "value1");
submit("Modify");
}
</source>
- For pages with more than one form, jWebUnit will establish which form is
being worked with implicitly
+ For pages with more than one form, JWebUnit will establish which form is
being worked with implicitly
from the form elements checked or set. You can also set the form
explicitly by form id or name:
<source>
public void testBottomFormSubmission() {
@@ -207,7 +207,7 @@
<subsection name="Validating Page Content">
<p>
- Once you have navigated to the page you wish to test, you can call the
assertions provided by jWebUnit to
+ Once you have navigated to the page you wish to test, you can call the
assertions provided by JWebUnit to
verify it's correctness.
</p>
<pre>
@@ -226,7 +226,7 @@
<subsection name="Validating Table Content">
<p>
- A number of assertions are provided by jWebUnit to validate the contents
of tables on a page.
+ A number of assertions are provided by JWebUnit to validate the contents
of tables on a page.
You can simply check for the presence of text within a table, or check
layout of all or a portion
of the table. HttpUnit is used to purge empty rows and columns from the
actual table before comparison,
so you may leave spacer cells and rows out of your check.
@@ -287,7 +287,7 @@
<subsection name="Using Element IDs to Validate Content">
<p>
- jWebUnit allows you to check for the presence of any html element by
its id, or for text in an element.
+ JWebUnit allows you to check for the presence of any html element by
its id, or for text in an element.
This can be a useful trick to check for the presence of some logical
part of the page.
Even in the case of free floating text, a span element can be used to
surround the text
and give it a logical id:
@@ -313,7 +313,7 @@
Another useful testing trick is to use property files for your
expected values rather than hard-coded strings.
This is especially useful if your application uses property
files as a source for static text and
messages. The same files can be used to provide the expected
values for the tests.<p>
- For convenience, most of the jWebUnit assertions that take
strings for the expected have an equivalent assertion that will
+ For convenience, most of the JWebUnit assertions that take
strings for the expected have an equivalent assertion that will
take a property file key. You can use the TestContext to set
the bundle to be used as well as the
Locale (default is Locale.getDefault()).
</p>
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
JWebUnit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development
