4 Example Test Output - essenius/FitNesseRun GitHub Wiki

Test results will be published to Azure Pipelines via the NUnit 3 format, which can be read by version 2 of the standard Publish Test Result task. Each test page translates to a test-case entity. A summary of the assertions per page is provided in the failure/message entity of the test-case. It will also be used if there are no failures, to make clear how many assertions there were on the page. It looks a bit strange to provide failure messages for passed tests, but this was the only way I could think of to pass on a page summary. The full test result HTML is incorporated in test-run/test-suite/output of the result file.

The FitNesseRun task will fail if any of the tests fails. So, for the test results publication to work, make sure to enable Continue on error in the control options for FitNesseRun, or else the Publish Test Results task will not get executed. Additionally , set the parameter Run this task for Publish Test Results to Even if a previous task has failed, unless the build was canceled.

The result always has one test suite and can have one or more test cases. Every test page in FitNesse translates to a test case. If everything passes, you will see something like this in the results: Click Outcome (where you see Aborted (+1)) and then Clear to show all results instead of only the failed and aborted ones. You will then see the list of all tests that have ran. Select the suite entry to show some more details, and then select the Attachments tab, You should then see three files: fitnesse.xml (the test results that FitNesse returned), DetailedResults.html (the viewable results) and results_nunit.xml (the results converted to NUnit 3 that were used to populate the page in Azure Pipelines). Select DetailedResults.html and then Download. The file will be downloaded to your standard Downloads folder. Then open it to view all ran FitNesse tests: