Moving Forward with Automated Acceptance Testing, Page 2
Your new page name, TestSample, follows the wiki convention of page naming. The basic rule is that a wiki page name starts with an uppercase letter, and at least one other letter in the word is also uppercase. However, the page name cannot contain two consecutive uppercase letters. Wiki page names can contain numbers. There are likely more rules; the easiest way to figure them out is to just try various name combinations. You'll refer to a valid wiki page name as a wiki word.
The question mark next to the text TestSample says two things: First, TestSample is a valid wiki word. Second, FitNesse can't find a page named TestSample. That's because you haven't created it yet.
To create the page, click the question mark next to TestSample. This opens a new page with no content, offering a fresh and clean edit box for typing. Enter some simple text (see Figure 4) and press Save. Your resulting page appears in Figure 5.
Figure 4: Editing a new page.
Figure 5: The new page
Note a couple things about your new page. The left-hand buttons now contain a Test button. Also, the address for the page, http://localhost:8083/TestSample, is basically the server plus your page name.
Click the FitNesse gauge icon in the upper-left corner of your new TestSample page. You also might have clicked the link marked .FrontPage at the bottom of the page. Either click takes you back to the FitNesse welcome page, which you'll also refer to as the FrontPage. Your browser now recognizes the TestSample wiki word as an existing page (see Figure 6). You can click on the link to return to the TestSample page.
Figure 6: FitNesse found your new page.
At this point, you have enough information create and edit new pages. You're going to go off now and experiment with FitNesse, adding a few new pages. You're also going to read the FitNesse user's guide because you found a link to it from the FrontPage. In the user's guide, you expect to find information on how to spruce up the look and feel of your pages. You'll make sure you're comfortable with a few basics, such as making text bold or italic.
At this point, if you're not already using a wiki, you now have a tool that can provide your team with great value. You can use the wiki as a very dynamic place to add content. You can post ad hoc project documents to the wiki, use it as a repository for frequently asked questions, add workstation setup procedures, or even list favorite places to eat around the office. The beauty of a wiki is that anyone can easily edit the content without having to deal with the tedium of HTML and deployment issues.
Next, you'll create and test a simple application.
About the AuthorJeff Langr is a veteran software developer with a score and more years of experience. He's authored two books and dozens of published articles on software development, including Agile Java: Crafting Code With Test-Driven Development (Prentice Hall) in 2005. You can find out more about Jeff at his site, http://langrsoft.com, or you can contact him directly at email@example.com.
Page 2 of 2