1 FitNesseConfigure - essenius/FitNesseRun GitHub Wiki

The FitNesseConfigure task creates the plugins.properties file for FitNesse, which contains its configuration data. It does that by examining the folder structure, finding Java, FitNesse and FitSharp (the .Net runner). If it cannot find FitSharp, it will assume that Java fixtures will be used. SLIM is set as the default test system. It can also unblock the used ports in the firewall if needed. Further, it creates the pipeline variables FitNesse.StartCommand and FitNesse.WorkFolder for use in other pipeline tasks.

Finally (and this is specifically for Web testing), it adds the Firefox binary to the path if it wasn't already in there. This is because by default the Azure DevOps hosted agents do have Firefox installed, but not in the path. Chrome and Internet Explorer are already in the path.

The tasks works best with hosted agents, but can also be used with on-premises agents. If you want to use an on premises agent, you need to ensure that Java and the browsers/browser drivers you need are installed and available in the path before running FitNesseConfigure.

The table below shows the available parameters.

Parameter	Description	Default
Target Folder	Data folder for FitNesse, where wiki and fixture folders are expected	.
Desired port	Port to run the FitNesse instance on	9123
SLIM Port	First port to run the SLIM server on	8085
SLIM Pool Size	Pool size for SLIM (starts from SLIM Port)	5
SLIM timeout	Timeout for the SLIM server (seconds)	30
Unblock Ports	Open firewall for incoming traffic on the FitNesse/FitSharp ports	false

• If you want to unblock the firewall ports, you need to ensure that the process running the agent has sufficient rights.