Fitnesse startup parameters and Configuration

After the latest version of fitnesse 20140630 is started by default, the webpage style is completely different from the bootstrap style of fitnesse.org.
You must configure theme = Bootstrap in plugins. properties to start the bootstrap-style fitnesse.

Start the bootstrap-style fitnesse

After downloading the latest 20140630 fitnesse-standalone.jar from fitnesse.org,
Start fitnesse:

?

1	D:\fitnesse\fitnesse-20140630>java -jar fitnesse-standalone.jar -p 40630

Enter URL: http: // localhost: 40630 in the browser
The fitnesse website is as follows:

But fitnesse.org is like this:

This problem plagued me for two weeks. I accidentally saw the parameter table at fitnesse startup:

The startup parameters can be defined in plugins. properties,

Open the https://github.com/unclebob/fitnesse/blob/master/plugins.properties for the fitnesse source code site

See the following content:

?

123456789101112

### Theme## Themes can be used to customize the look and feel of the wiki.# Build in theme include fitnesse_straight (the default), fitnesse_mint,# fitnesse_topnav and bootstrap (based on the Twitter bootstrap front-end# framework).##Theme=fitnesse_straightTheme=bootstrap ##

In plugins. properties, you have set the webpage style to bootstrap,

Download plugins. properties to the fitnesse running directory:

After restarting fitnesse, you can see the following website:

Success!

Run the following command to start the test case:

URL:

?

1	http://localhost:11026/BaiduMapApiSuite.GetIpLocation?test

Fitnesse also supports output of test results in XML format, as long as the URL is entered:

?

1	http://localhost:11026/BaiduMapApiSuite.GetIpLocation?test&format=xml

Note:

• /Finalcounts/right is the number of test cases passed
• /Finalcounts/wrong is the number of failed test cases
• /Finalcounts/ignores is the number of unexecuted Test Cases
• /Finalcounts/effectons indicates the number of test cases that cause exceptions, which is the statement that fitneese reports Java exceptions.

It indicates that/finalcounts/wrong +/finalcounts/effectons> 0
By calling this URL with curl or wget in the command line, you can start regression testing on a regular basis or after each installation in the continuous integration tool Hudson/Jenkins.

Start the test again in the command line mode:

Let's take a look at the startup command line parameters of fitnesse:

?

1234567891011

D:\fitnesse\fitnesse-20111026>java -jar fitnesse.jar -hUsage: java -jar fitnesse.jar [-pdrleoa]        -p <port number> {80}        -d <working directory> {.}        -r <page root directory> {FitNesseRoot}        -l <log directory> {no logging}        -e <days> {14} Number of days before page versions expire        -o omit updates        -a {user:pwd | user-file-name} enable authentication.        -i Install only, then quit.        -c <command> execute single command.

The-CCan execute a single test case or test suite

?

1	D:\fitnesse\fitnesse-20111026>java -jar fitnesse.jar -p 9001 -c "BaiduMapApiSuite.GetIpLocation?test&format=xml" > test-result.txt

Open text-result.txt: