When you click on Test History you will be shown the directory of all tests and suites that are in the test history database. This directory also shows you the status of the last 20 results from each test or suite. You can click on the name of the test or suite to get a detailed page history, or you can click on any of the individual status elements to see the particular test result.
The detailed page history shows you a directory of all the test results for that test or suite. The bar chart shows how how the number of tests (for suites) or assertions (for tests) has grown over time, and the pass/fail ratio. Clicking on an entry takes you to that specific test result.
Details
The test history database is kept in FitNesseRoot/files/testResults. Beneath this directory there is a subdirectory for each test or suite. These directories contain the page history and are named for the page that contains the test or suite. Beneath the page history directory is a file for each test result.The test result files are named using the following scheme YYYYMMDDHHMMSS_R_W_I_E.xml where YYYYMMDDHHMMSS is the date and time of the test run, and R, W, I, and E are integers representing the number of Right, Wrong, Ignored, and Exception counts for the test or suite. For tests they are assertion counts. For suites they are test counts. (Example: 20090513134259_12_20_4_2.xml)
The test files contain the XML that describes the test run. The format of this XML is identical to the XML packet returned by the format=xml flag when you run a test. (See
Purging
There are buttons at the top of the Test History page that allow you to purge old history files. You have your choice of all, >7 days, or >30 days. If you want to purge a different number of days, you can change the Test History.purgeOptions in the configuration file to allow additional purge options, or you can use the RESTful URL form. (See RestfulServices).You can also clean up the test history right after a test execution. To do so, configure a property test.history.days in the configuration file or as a page variable and assign it the number of days you want to keep history. Additionally, you can configure the property Test History.maxCount in the configuration file to limit the number of histories to keep.
Comparing History
When viewing the history for a page, you can select any two test results by clicking in their checkboxes. Then, if you click the Compare button, you will be shown the two test results side-by-side along with an indicator that tells you if the results are identical or not.Only tests can be compared this way. Suites cannot.
Notice that the comparison is pretty smart. It tries to line up the two tests on a table-by-table basis. It can detect if tables have been inserted or deleted. The % code that you see on the left is just the match score for the tables.