7 Task Versions - essenius/FitNesseRun GitHub Wiki

You will notice in Azure Pipelines that there are two versions of this task. One is the stable version (currently 0) and one is the development version (currently 1). Only the development version gets new features so once you need a new feature you will need to migrate. Note that the development version has more frequent updates as the stable version only gets blocking bug fixes.

My Definition of Done includes missing no more than 5 statements per source file in unit testing, which generally leads to a coverage of over 95%. This holds for both the stable version and the development version, so I expect both versions to run reliably.

Version 0 is the pre-release that relied on NuGet packages with a publication convention to distribute the FitNesse fixtures and test pages. With the release of universal packages in Azure Artifacts, the task could be considerably simplified, and that has resulted in Version 1. I also took the opportunity to simplify the folder structure by merging the data folder and the fixtures folder, as all pre-release tests showed that this was an unnecessary complication, especially on hosted agents. You won't see a lot of differences other than that some parameters have been removed.

A natural time to move from Version 0 to Version 1 is when you adopt universal packages, but Version 0 will also work with those. If you start fresh, I recommend using Version 1.

Version 1 made the use of FitSharp optional, so it can now also be used to test with Java based fixtures. If the task cannot find FitSharp under the data folder somewhere, it will not configure FitNesse for FitSharp, and by default it is configured for Java.