To run the automated tests you'll need to have NUnit installed.

There are two types of automated testing in FlexWiki: UnitTests and BuildVerificationTests.

UnitTests are intended to test FlexWiki at an API level. Typically, these tests simply ensure that a given piece of FlexWiki code produces the expected output when called with a particular input. These tests can be found in the FlexWiki.UnitTests project.

BuildVerificationTests are intended to test a fully installed and configured version of FlexWiki. These tests ensure that when someone makes a particular web request against a FlexWiki instance, the expected result (HTML for the FlexWiki web interface, XML for the FlexWikiWebService) is returned. These tests can be found in the BuildVerificationTests project.

Both UnitTests and BuildVerificationTests are driven via NUnit. You can run them either interactively via NUnitGui, TestDriven.NET or some other interactive testing framework, or by using the build script. Note that if you run the BuildVerificationTests interactively, you will need to install FlexWiki somewhere on your machine and set the values in the app.config file appropriately.

To run the UnitTests with the build script, open a command window in the root of your FlexWiki source directory and run

 build test

To run the BuildVerificationTests with the build script, open a command window in the root of your FlexWiki source directory and run

 build verify

Running the BuildVerificationTests with the build script, will automatically build and install FlexWiki and update the app.config file with the appropriate values.

"Summary: An overview of the different kinds of automated tests available for FlexWiki development.