xcfit 0.9.0 → 1.0.0

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/PlainTextTable/properties.xml

@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<properties>
-<Edit>true</Edit>
-<Files>true</Files>
-<Properties>true</Properties>
-<RecentChanges>true</RecentChanges>
-<Refactor>true</Refactor>
-<Search>true</Search>
-<Versions>true</Versions>
-<WhereUsed>true</WhereUsed>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/TodaysDate/content.txt

@@ -1,12 +0,0 @@
-To diplay todays date:
-
-|!c '''Markup Text'''|!c '''Displayed as'''|
-|!style_code(!-Today is !today.-!)|Today is !today.|
-|!style_code(!-XML is !today -xml.-!)|XML is !today -xml.|
-|!style_code[!-Right now it is !today -t.-!]|Right now it is !today -t.|
-|!style_code[!-Tomorrow is !today +1.-!]|Tomorrow is !today +1.|
-|!style_code[!-Last week was !today -7.-!]|Last week was !today -7.|
-|!style_code[!-The month is !today (MMM).-!]|The month is !today (MMM).|
-
-As you can see, you can add or subtract days.  You can include the time with -t.  And you can use your own format for the time.  (See !style_code(!-SimpleDataFormat-!) for the syntax.)
-

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/TodaysDate/properties.xml

@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<properties>
-<Files/>
-<RecentChanges/>
-<Search/>
-<Static/>
-<WhereUsed/>
-<saveId>1237147701126</saveId>
-<ticketId>-776073001262686991</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/content.txt

@@ -1,34 +0,0 @@
-!1 Wiki Markup Language Reference
-The !-FitNesse-! markup language is straightforward to learn, and powerful enough to enable you to create richly-formatted and customized wiki pages. Below is a reference of so-called "widgets" for formatting text and accomplishing other things on wiki pages.
-
-| !c '''Markup Syntax''' |
-| [[Italics][>MarkupItalics]] | ''Setting a word or phrase in italics.'' |
-| [[Bold][>MarkupBold]] | ''Setting a word or phrase in bold.'' |
-| [[Strike][>MarkupStrike]] | ''Putting a strike through a word or phrase.'' |
-| [[Style][>MarkupStyle]] | ''Setting the style of some text.'' |
-| [[Cross Reference][>MarkupCrossReference]] | ''Add a cross reference to another page.'' |
-| [[Headers][>MarkupHeaders]] | ''Setting a line as a title or section header.'' |
-| [[Centering][>MarkupCenter]] | ''Centering a line.'' |
-| [[Notes][>MarkupNote]] | ''Making a note.'' |
-| [[Horizontal Rules][>MarkupHorizontalRule]] | ''Drawing a horizontal separator.'' |
-| [[Images][>MarkupPicture]] | ''Placing a picture or image.'' |
-| [[External links][>MarkupExternalLink]] | ''Creating a hyperlink to an external webpage.'' |
-| [[Links Within Pages][>LinksWithinPages]] | ''Creating links to anchors within the same page.'' |
-| [[Wiki page links][>MarkupInternalLink]] | ''Creating a hyperlink to an internal wiki page.'' |
-| [[Alias links][>MarkupAliasLink]] | ''Turning reqular words or images into links'' |
-| [[Lists][>MarkupLists]] | ''Creating bullet lists and numbered lists'' |
-| [[Literal Text][>MarkupLiteralText]] | ''Preventing text from being interpreted.'' |
-| [[Preformatted text][>MarkupPreformatted]] | ''Setting text as preformatted monofont'' |
-| [[Comments][>MarkupComments]] | ''Putting comments in markup text.'' |
-| [[Variables][>MarkupVariables]] | ''Defining and expressing variables'' |
-| [[Classpaths][>MarkupPath]] | ''Marking a line as a directory path.'' |
-| [[Tables][>MarkupTable]] | ''Creating tables.'' |
-| [[Hash Tables][>MarkupHashTable]] | ''Creating lookup tables.'' |
-| [[Plain Text Tables][>PlainTextTable]] | ''Creating tables from plain text without vertical strokes'' |
-| [[Collapsable Sections][>MarkupCollapsableSection]] | ''Making a section of content collapsable and expandable'' |
-| [[Table of Contents][>MarkupContents]] | ''Generate a table of contents for a SubWiki.'' |
-| [[Including][>MarkupPageInclude]] | ''Pulling the content from one page into another.'' |
-| [[Help][>MarkupHelp]] | ''Displaying the help property for the page.'' |
-| [[Last Modification Time][>LastModificationTime]] | ''Showing the time that a page was last modified.'' |
-| [[Today's Date][>TodaysDate]] | ''Showing todays date in various formats and styles.'' |
-| [[Nesting][>MarkupNesting]] | ''Nesting markup within other markup elements.'' |

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/properties.xml

@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<properties>
-<Files/>
-<Normal/>
-<RecentChanges/>
-<Search/>
-<Static/>
-<WhereUsed/>
-<saveId>1237146606658</saveId>
-<ticketId>-1006255556384496467</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/PageFooter/content.txt

@@ -1 +0,0 @@
-!include -seamless <UserGuide.PageFooter

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/PageFooter/properties.xml

@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Edit>true</Edit>
-	<Files>true</Files>
-	<Properties>true</Properties>
-	<RecentChanges>true</RecentChanges>
-	<Refactor>true</Refactor>
-	<Search>true</Search>
-	<Versions>true</Versions>
-	<WhereUsed>true</WhereUsed>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/PageHeader/properties.xml

@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Edit>true</Edit>
-	<Files>true</Files>
-	<Properties>true</Properties>
-	<RecentChanges>true</RecentChanges>
-	<Refactor>true</Refactor>
-	<Search>true</Search>
-	<Versions>true</Versions>
-	<WhereUsed>true</WhereUsed>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/PageProperties/content.txt

@@ -1,36 +0,0 @@
-FitNesse pages can have attributes that alter the way the pages are displayed, and how they behave.  These can be enabled or disabled for a page by hitting the Properties menu item.
-
-!3 Page Type
- * '''Static''': This is just a content page.
- * '''Test''': This property instructs ''!-FitNesse-!'' to treat the page as a fitnesse test page:
-   * It enables the '''Test''' button, which submits the page to Fit to process all of the page's test tables.
-   * Pages with the Test property enabled will have the '''!-SetUp-!''' and '''!-TearDown-!''' text applied to them. See<UserGuide.AcceptanceTests.SpecialPages.
-     * !-SetUp-! will be prepended to the page, just after the !-PageHeader-! (if any).
-     * !-TearDown-! will be appended to the page, just before the !-PageFooter-! page (if any).
-   * Pages with this property will be included in ''test suite runs''.
- * '''Suite''': Pages with this property are test suites. All sub pages are considered part of the suite. Any sub page with the '''Test'''property set is considered a test within the suite.
-   * The '''Test Suite''' button is enabled by this property.
-   * A ''test suite run'' is activated by hitting the '''Test Suite''' button. All tests within the suite are run and their results reported.
-
-!3  
-!4 Implicit Page Attributes
-
- * Pages that begin or end with '''"Test"''' or '''"Example"''' will automatically have the '''Test''' property set.
- * Pages that begin or end with '''"Suite"''' or end with "'''Examples'''" will automatically have the '''Suite''' property set.
- * Once these pages are created, you can set or clear these properties as usual.
-
-!3 Actions
- * '''Edit''':  When set, this property causes the '''Edit''' button to be displayed.  This is a poor man's read-only switch.  If you clear this checkbox then users will not have a convenient way to edit the page.  Of course they can always edit it by typing the ''page?edit'' URL -- but we don't have to tell them how to do that, do we?--
- * '''Search''':  This property enables or disables the '''Search''' button.  There's no real good reason to disable this button, but we put the ability in just for symmetry.
- * '''Versions''': Enables the '''Versions''' button.  Hitting this button brings up a list of old versions of the page.  If this property is not set, then the button will not be displayed, but versions will still be tracked.
- * '''Properties''': Enables the '''Properties''' button.  Hitting this button brings up a pages that allows you to edit all page properties mentioned here.  If you disable this property users will not have a convenient way to change the properties of a page.  (Of course they can always use the ''page?properties'' URL.)
-
-!3 Navigation
-The following entries are shown in the Tools menu, if enabled
-
- * Recent Changes: links to the .RecentChanges page
- * Files: links to the http://files/ section
- * Search: opens an advanced search dialog.
-
-!3 Security
-The permissions for the page can be changed to read, write and test.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/PageProperties/properties.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Files/>
-	<Help>Change page specific properties</Help>
-	<RecentChanges/>
-	<WhereUsed/>
-	<saveId>1238171805702</saveId>
-	<ticketId>8555069348586341028</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/RefactoringWikiPages/content.txt

@@ -1,5 +0,0 @@
-The '''Refactor''' button on each page allows you to delete or rename that page in the wiki.
-
- * '''Delete''' - If you delete a page, all references to that page will become dead.  You'll see them with '''[?]''' following them.
- * '''Rename''' - If you rename a page, all references to that page will be renamed.
- * '''Move''' - If you move a page, it will be moved with all it's children.  Any references to it or its children will be appropriately modified.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/RefactoringWikiPages/properties.xml

@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Files/>
-	<RecentChanges/>
-	<WhereUsed/>
-	<saveId>1213643693631</saveId>
-	<ticketId>1221131539155543533</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/RootPage/content.txt

@@ -1 +0,0 @@
-To access the root of the whole !-FitNesse-! wiki use the following URL:{{{http://<fitnesse-location>/root}}} You can put variable definitions, and '''!path''' directives on this page.  All pages in the wiki will inherit these attributes.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/RootPage/properties.xml

@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-  <Files/>
-  <LastModified>20060717210007</LastModified>
-  <RecentChanges/>
-  <WhereUsed/>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/ShortcutKeys/content.txt

@@ -1,10 +0,0 @@
-Some of the buttons on the wiki page have shortcut keys.  These may or may not work in your browser!
-|'''Edit'''|''ALT-e''|
-|'''Properties'''|''ALT-p''|
-|'''Test'''|''ALT-t''|
-|'''Search'''|''ALT-s''|
-|'''Versions'''|''ALT-v''|
-
-Due to the above shortcut keys not working on most browsers a set of more modern shortcut keys have been provided.  Pressing ? on any normal wiki page (not the edit page, etc.) will bring up a modal dialog showing the standard set of shortcut keys.
-
-!img http://files/fitnesse/images/keyboard_shortcuts.png

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/ShortcutKeys/properties.xml

@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Files/>
-	<Properties/>
-	<RecentChanges>true</RecentChanges>
-	<Search/>
-	<Versions/>
-	<WhereUsed/>
-	<saveId>1052054924832</saveId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/SubWiki/content.txt

@@ -1,26 +0,0 @@
-!1 The SubWiki: Organizing !-FitNesse-! Pages into Hierarchies
-!2 Why Do We Need Page Hierachies?
-FitNesse, you recall, is a [[wiki][EditingFitNessePages]], but more than a normal one! A normal wiki is a collection of pages with a flat structure.  All the pages are peers.  FitNesse, on the other hand, is meant to manage many projects.  We'd like each project to have its own wiki hierarchy so that name collisions can be avoided, fixture code can be found easily, etc. We might even need hierarchies within those hierarchies.
-
-For example, project one and project two each have their own [[Test suites][<UserGuide.WritingAcceptanceTests.TestSuites]]. Some of the suites might in turn contain smaller suites. These projects probably also use completely different [[Class path][<UserGuide.WritingAcceptanceTests.ClassPath]] definitions. We'd like each project to be able to run acceptance tests using their own class path definitions. So we want a different class path page for each. This is what the FitNesse SubWiki feature makes possible.
-
-!2 How SubWiki Works
-A SubWiki is a whole new page hierarchy that lives beneath a single FitNesse page. In fact, such a SubWiki is an entirely separate wiki, with an entirely separate page namespace. Any FitNesse page can be the parent of such a SubWiki. For example the name of this page is [[<!-UserGuide.FitNesseWiki.SubWiki-!][<UserGuide.FitNesseWiki.SubWiki]].  Thus, this page is the SubWiki page whose parent is the [[<!-UserGuide.FitNesseWiki-!][<UserGuide.FitNesseWiki]] page. ''(Put your mouse on each of these links and look at the bottom of the display to see where they will be directed.)'' For any such SubWiki, you could have a separate page named SubWiki, and FitNesse would keep them all straight (you might have some trouble, if you did not organize your page links carefully, but that's another story).
-
-!3 Creating a SubWiki
-To create a sub wiki, simply create the parent page, and then add pages below it using the ''Add'' menu item, the ''!-ParentPage.SubPage-!'' syntax or the shortcut ''!->SubPage-!'' markup language syntax.
-
-When a sub-page is displayed, any unqualified links are assumed to be at the current level.  If you want to access a global page, you need to precede the link with a dot.  For example, from where we are now on this page, the link !-RecentChanges-! is really a link to !-.FitNesse.RecentChanges-! (which does not exist), whereas the link .RecentChanges is a link to the global page that contains the list of most recently changed pages.
-
-!3 Navigating through Sub Wikis
- * The '''!contents '''widget will create a list of all the immediate child pages of a parent page.
- * Absolute references look like this: !-.TopPage.MyPage.YourPage-! where !-TopPage-! is at the highest level.
- * Relative references look like this: !-YourPage.MyPage.HisPage-! where !-YourPage-! is a sibling of the page that holds the reference.
- * Sub page references look like this: !->ChildPage.GrandChildPage-! where !-ChildPage-! is a child of the page that holds the reference.
- * Backwards Search References look like this: !-&lt;AncestorPage.SomePage-! where !-AncestorPage-! is a parent, grandparent, or somewhere up the parent chain.  You can use this to search backwards through the page hierarchy until you find the named page.
-
-!3 [[!-Test Suites-!][<UserGuide.WritingAcceptanceTests.TestSuites]]: the Perfect Application of the SubWiki
-When you organize a suite of test pages, you will naturally want to make each of the individual test pages a child page of the main suite page.
-
-!3 Page Headers and Footers in !-SubWikis-!
-The PageHeader and PageFooter classes can be used to add specific headers and footers to sub wikis.  For example, the footer of this page is coming from <UserGuide.PageFooter.  These headers and footers can be inherited from parent pages.  So if there's no PageHeader or PageFooter at the current level, FitNesse will search upwards in the hierarchy until we find one. (See <UserGuide.WritingAcceptanceTests.SpecialPages)

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/SubWiki/properties.xml

@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<properties>
-<Files/>
-<RecentChanges/>
-<WhereUsed/>
-<saveId>1238174883665</saveId>
-<ticketId>-2525399175413409353</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/SymbolicLinks/content.txt

@@ -1,22 +0,0 @@
-!img-r http://files/fitnesse/images/symlinkDiagram.gif
-!3 What are SymbolicLinks?
-Symbolic Links allow a user to easily create parent-child links between pages without permanently affecting the wiki structure.  Refer to the diagram on the right.  You will notice that the !-ApplicationTests-! page has a child page named !-SuiteTests-! which contains several other pages.  The !-EnvironmentOne-! page has no static child pages but it does have a symbolic link to the !-SuiteTests-! page.  This symbolic link acts like a child page in almost every way and give two full names to the !-SuiteTests-! page:
-
- * !-.ApplicationTests.SuiteTests-! is the real name,
- * !-.EnviromentOne.SymbolicLink-! is a symbolic name for the same page.
-
-SymbolicLinks may also be made to external FitNesse directories.  See below.
-
-!3 Why Should I Use SymbolicLinks?
-One common reason need for Symbolic Links is the the testing of a system on multiple environments.  For example, imagine an application that site on top of an Oracle database.  Hundreds of FitNesse tests have been written for this application using Oracle settings and then the team is confronted with the need to run the application on !-MySql-!.  Getting both databases running under the same suite of tests can be very difficult and may result in duplicating all the tests.  With Symbolic Links, the database configurations can be stored in high level pages along with appropriate path elements.  Then the high-level pages may symbolically link to the test suite.  In this manner one suite of tests can be executed in multiple environments.
-
-Another reason is that you want to test two implementations for the same interface. 
-.FitNesse.SuiteAcceptanceTests.SuiteVersionsControllerTests is a practical example using symbolic links.
-
-!3 How do I use SymbolicLinks?
-Navigate to the page where you'd like to add a symbolic link.  Click the '''Properties''' button to load the ''properties'' view.  There is a section titled '''Symbolic Links'''.  There is a form here where may create a new symbolic link by suppling a single WikiWord name for the link and relative or absolute path to the page to which you'd like to link.  Once created, the symbolic link will be listed in the '''Symbolic Links''' section of the same ''properties'' view.    You may remove or rename existing links by clicking the corresponding '''Unlink''' or '''Create/Replace''' link.
-
-!3 External SymbolicLinks
-For various reasons, you may want to keep a branch of your FitNesse wiki in a different location on your disk, than the rest of the wiki.  You may link external branches into the main wiki by using SymbolicLinks.  To do so, simply provide the file path to the external FitNesse directory in URL format preceded with '''file:/''', e.g. ''!-<i>file:///User/MicahMartin/fitnesse/ExternalFitNesseRoot</i>-!''
-
-SymbolicLinks can also use environment variables to find a branch to add to your wiki, e.g. ''!-<i>file://${HOME}/MicahMartin/fitnesse/ExternalFitNesseRoot</i>-!''

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/SymbolicLinks/properties.xml

@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Files/>
-	<RecentChanges>true</RecentChanges>
-	<WhereUsed/>
-	<saveId>1201721251657</saveId>
-	<ticketId>-3379710537192929046</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/WhereUsed/content.txt

@@ -1 +0,0 @@
-If you click on the name of the page, !-FitNesse-! will print a list of every page that references that page.  Try it by clicking on !-WhereUsed-! above.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/WhereUsed/properties.xml

@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Files/>
-	<LastModified>20090228113827</LastModified>
-	<RecentChanges>true</RecentChanges>
-	<WhereUsed/>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/WikiImport/content.txt

@@ -1,16 +0,0 @@
-!3 What is WikiImport?
-WikiImport is a feature that allows you to import an entire wiki or subwiki from another FitNesse site.  All of the pages from the remote wiki will be copied to your local FitNesse installation and become part of your local wiki.
-
-!3 Why should I use WikiImport?
-In a development environment it is most practical to have a main FitNesse server where all the tests are maintained and new tests are added.  However, it is not practical for all the developers to run the tests on one server. Therefore each developer should have a FitNesse installation in their development environment.  The test pages from the main server get imported by each developer so they can execute the most recent tests against their current code base.
-
-!3 How do I use WikiImport?
-Create a page or use an existing page that will contain the imported wiki.  Open the ''properties'' view of this page.  There is a form title Wiki Import.  Supply the URL to the remote wiki that you'd like to import and submit the form.  This will take you to an import view where you will see all the imported pages being listed.  It may take a few moments for the import to complete.  You will know it's complete when the bottom of the page is visible and ends with an imported page count.
-
-Once a wiki has been imported, it may be updated at any time.  Simple open the ''properties'' view of the importing page or any imported page.  There will be a button in the '''Import Wiki''' section.  Clicking this button initiate an update of all the imported pages beneath the currently selected page.
-
-!3 New Edit Buttons
-Once you have imported a wiki, the '''Edit''' button will be turned off and two new edit buttons will be added: '''Edit Locally''' and '''Edit Remotely'''.  '''Edit Locally''' behaves just like the '''Edit''' button that you've used all along.  '''Edit Remotely''' allows you to easily edit the page from where the content is being imported.
-
-!3 Automatic Update Option
-In the WikiImport section of the ''properties'' page, you'll see a check box that says: "Automatically update imported content when executing tests".  Enabling this option will kick off an update for any test page prior to execution.  Child pages will inherit this option from parent pages, which means you need only set on the root of you test hierarchy.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/WikiImport/properties.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-  <Files/>
-  <LastModified>20080617162634</LastModified>
-  <RecentChanges/>
-  <WhereUsed/>
-  <saveId>1213737994217</saveId>
-  <ticketId>-6982862784974797638</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/WikiWord/content.txt

@@ -1,10 +0,0 @@
-The syntax of a wiki word is ''Camel Case'': an alternating pattern of upper and lower case letters.  Strictly speaking a wiki word is a string of two more more capital letters with lower case letters or numbers between them.
-
- * '''!-BobMartin-!''' is a wiki word.
- * '''!-SalesReport1972-!''' is a wiki word.
- * '''!-USAforEver-!''' is not, because there are two capitals in a row.
- * '''!-Usa1776-!''' is not because there is only one capital.
- * '''!-RcM-!''' is a wiki word because it is two or more capitals separated by lower case letters.
- * '''!-ItDoesNotMatterHowManyCapitalsThereAreYouCanHave1000IfYouLike-!''' is a wiki word with lots of capitals.
-----
-!note The Java Regular expression that we are using to represent a wiki word is: {{{\b[A-Z](?:[a-z0-9]+[A-Z][a-z0-9]*)+}}}

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/WikiWord/properties.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<properties>
-	<Files/>
-	<LastModified>20090327123919</LastModified>
-	<RecentChanges/>
-	<WhereUsed/>
-	<saveId>1238175559465</saveId>
-	<ticketId>-419557567139808752</ticketId>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/content.txt

@@ -1,19 +0,0 @@
-!2 Working With !-FitNesse-! Wiki Pages
-!-FitNesse-! provides an easy-to-use [[wiki][http://wiki.org/wiki.cgi?WhatIsWiki]] to create web pages that are run as tests. Test pages have a button on them allowing all the tests on the page to be run, so any user can go to that page and click the button at any time, and see if the tests are passing. Also, !-FitNesse-! provides means to automatically run tests, so it can be easily added to your automated build scripts.
-
-So what does a test page look like? A page name has the form of a >WikiWord. A >WikiWord consists of two or more concatenated words, each word begins with a capital letter.
-
-Although FitNesse is about writing acceptance tests, you'll probably want to study these tips for using the wiki:
-
-| [[Editing !-FitNesse-! Pages][>EditingFitNessePages]] | ''An intro to creating and changing ''!-FitNesse-!'' pages using the wiki markup language.'' |
-| [[Shortcut keys][>ShortcutKeys]] | ''The shortcuts for the buttons.'' |
-| [[Markup Language Reference][>MarkupLanguageReference]] | ''A reference for formatting ''!-FitNesse-!'' pages using the wiki markup language.'' |
-| [[Sub-wikis][>SubWiki]] | ''How to create hierarchies of ''!-FitNesse-!'' pages.'' |
-| [[Wiki Import][>WikiImport]] | ''Importing wiki pages from a remote ''!-FitNesse-!'' server.'' |
-| [[Page Properties][>PageProperties]] | ''Enabling and disabling page properties (also called attributes).'' |
-| [[Symbolic Links][>SymbolicLinks]] | ''Dynamically altering the wiki page structure.'' |
-| [[Refactoring pages][>RefactoringWikiPages]] | ''Renaming, moving and deleting existing pages.'' |
-| [[Where Used][>WhereUsed]] | ''Finding out which pages reference the current page.'' |
-| [[Headers and footers][>MarkupHeaderAndFooter]] | ''Specifying Headers and Footers for wiki pages'' |
-| [[Files section][>FilesSection]] | ''The location for attachments, images, etc.'' |
-| [[External HTML pages][>ExternalHtmlPages]] | ''In case you've already written some pages in HTML and want to use then in FitNesse'' |

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/properties.xml

@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<properties>
-<Files/>
-<RecentChanges/>
-<Search/>
-<Static/>
-<WhereUsed/>
-</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FixtureGallery/BasicFitFixtures/ActionFixture/content.txt

@@ -1,109 +0,0 @@
-
-''Previous page: [[!-ColumnFixture-!][<UserGuide.FixtureGallery.BasicFitFixtures.ColumnFixture]] Next page: [[!-RowFixture-!][<UserGuide.FixtureGallery.BasicFitFixtures.RowFixture]] Parent page: [[!-Basic FIT fixtures-!][<UserGuide.FixtureGallery.BasicFitFixtures]]''
-!2 !-ActionFixture-!
-'''!- ActionFixture -!'''!- was originally intended for workflow-style tests that are not repetitive. It uses a UI metaphor to automate other fixtures. -!
-
-# section Table Format
-!3 !-Table Format-!
-!- The first row of an -!'''!- ActionFixture -!'''!- table always initialises the fixture class, in this case the -!'''!- ActionFixture -!'''!- itself and not a custom subclass. All rows after the first begin with a command cell, followed by command arguments in the remaining cells. Some rows will have two and some will have three cells. The second row is typically used for the -!'''!- start -!'''!- command, which expects one argument &mdash; the class name for the actual fixture to automate. After that, you can use the following commands to describe the test: -!
-
-!- <ul> -!!- <li> -!'''!- check -!'''!- &mdash; executes a method and verifies its value. -!!- </li> -!!- <li> -!'''!- press -!'''!- &mdash; executes a -!'''!- void -!'''!- method without testing anything. -!!- </li> -!!- <li> -!'''!- enter -!'''!- &mdash; executes a method and passes an argument to it. -!!- </li> -!!- </ul> -!!- You can imagine an -!'''!- ActionFixture -!'''!- as an automation tool to populate UI forms and click on buttons that are connected to methods. -!
-
-{{{
-!-!-!|ActionFixture|
-|start|ActionFixtureTest|
-|enter|firstPart|Hello|
-|enter|secondPart|World|
-|press|join|
-|check|together|Hello, World|
-}}}
-# section Fixture class
-!3 !-Fixture class-!
-!- An important difference between -!'''!- ActionFixture -!'''!- and all other fixtures is that you should not extend the -!'''!- ActionFixture -!'''!- class in order to use it. Instead, you should extend the -!'''!- fit.Fixture -!'''!- class directly for your fixture and then pass it on to the -!'''!- ActionFixture -!'''!- using the -!'''!- start -!'''!- command. -!
-
-# section Java Source Code
-!3 !-Java Source Code-!
-{{{
-package info.fitnesse.fixturegallery;
-
-public class ActionFixtureTest extends fit.Fixture{
-	private String first, second, both;
-	public void firstPart(String s){
-		first=s;
-	}
-	public void  secondPart(String s){
-		second=s;
-	}
-	public void join(){
-		both=first+ ", "+second;
-	}
-	public String together(){
-		return both;
-	}
-}
-}}}
-# section .NET Source Code
-!3 !-.NET Source Code-!
-{{{
-using System;
-
-namespace info.fitnesse.fixturegallery
-{
-	public class ActionFixtureTest: fit.Fixture
-	 {
-		public String firstPart, secondPart, together;
-		public void join()
-		{
-			together=firstPart+ ", "+secondPart;
-		}
-	}
-}
-}}}
-# section Python Source Code
-!3 !-Python Source Code-!
-{{{
-
-from fit.Fixture import Fixture
-
-class ActionFixtureTest(Fixture):
-    _typeDict = {}
-
-    def __init__(self):
-        Fixture.__init__(self)
-        self.__first  = ""    #< Private attributes (Python convention).
-        self.__second = ""
-        self.__both   = ""
-
-    # JAVA: void firstPart(String s)
-    _typeDict["firstPart"] = "String"
-    def firstPart(self, s):
-        self.__first = s
-
-    # JAVA: void  secondPart(String s)
-    _typeDict["secondPart"] = "String"
-    def secondPart(self, s):
-        self.__second = s
-
-    # JAVA: void join()
-    _typeDict["join"] = "Default"      #< AUTO-DETECT: None = void
-    def join(self):
-        self.__both = "%s, %s" % (self.__first, self.__second)
-
-    # JAVA: String together()
-    _typeDict["together"] = "String"
-    def together(self):
-        return self.__both
-
-}}}
-# section Notes
-!3 !-Notes-!
-!- In the Java version, -!'''!- ActionFixture -!'''!- only works on methods. in the .NET version, -!'''!- enter -!'''!- and -!'''!- check -!'''!- can get and set fields and properties as well. -!
-
-# section Usage
-!3 !-Usage-!
-!-You can use the -!'''!- ActionFixture -!'''!- to describe UI-style verifications.-!
-
-!- In general, -!'''!- ActionFixture -!'''!- has been replaced by -!'''!- DoFixture -!'''!- (see -![[!-DoFixture-!][<UserGuide.FixtureGallery.FitLibraryFixtures.DoFixture]]!- ) and there are very few reasons why you would want to use an -!'''!- ActionFixture -!'''!- today. -!'''!- DoFixture -!'''!- allows you to write workflow-style tests much easier, with less code in both the fixture and FitNesse table. It also supports direct domain object wrapping. -!
-
-
-''Previous page: [[!-ColumnFixture-!][<UserGuide.FixtureGallery.BasicFitFixtures.ColumnFixture]] Next page: [[!-RowFixture-!][<UserGuide.FixtureGallery.BasicFitFixtures.RowFixture]] Parent page: [[!-Basic FIT fixtures-!][<UserGuide.FixtureGallery.BasicFitFixtures]]''