Overview

Started in 2001 as a wiki interface to FIT, FitNesse brings requirements and verification into the same pages. Stakeholders can edit in a browser with wiki syntax or a rich-text editor, then run checks manually or automatically through the server. This makes expected behavior easier to keep alongside the documentation it governs, and can help teams catch regressions. It is not a hosted service: teams run the Java application themselves, and its wiki pages are stored as files.

FitNesse is distributed as a Java jar. Java 11 is required, with Java 11, 17, and 21 listed as supported versions. The project uses the Common Public License version 1.0.

Key features

Executable acceptance criteria

FIT and SLIM are built-in test systems, and tests can also run from JUnit or Maven. The core is Java, with extensions for other languages and environments. That gives teams several routes from a readable specification to an automated check, but also leaves them responsible for selecting and maintaining a test setup that suits their application.

Integration and coverage

Plugins include Maven, Ivy, Gradle, Git, TFS, and SVN-related support. Fixtures cover Selenium-based browser tests, REST and HTTP services, PDF checks, and email retrieval. This breadth makes FitNesse relevant beyond purely Java acceptance checks; teams should still weigh the work of configuring the integrations they need against a more focused testing tool.

Security and operations

Reading, writing, and testing can each be restricted independently, but all three protections are off by default. Search and related queries do not require authentication, and unauthenticated users can read files under /files. A server exposed beyond a trusted environment therefore needs deliberate access configuration, not just page permissions. The documentation recommends SSL for network traffic and password-cipher authentication; its test-system-to-application SSL guidance is limited to the SLIM Java client. Heavy test use may also exceed the JVM's default heap allocation, so memory failures can require increasing it.

Pricing

FitNesse is free: its open-source plan costs 0.00 USD per free. There is no free trial because the software is already free, and no commercial plan or usage limit is stated. The trade-off is operational rather than a paid tier: teams provide the Java runtime, server, configuration, and ongoing maintenance.

Platforms

FitNesse supports API, Linux, macOS, Windows, web, and self-hosted use. Execution is local, with browser-based access to the wiki and tests. Java is a prerequisite, so teams should confirm their runtime environment before adopting it.

Who it's for

FitNesse is a strong fit for teams that want acceptance criteria to be both stakeholder-readable and runnable, especially where the listed build, version-control, browser, and service-testing extensions match an existing stack. It is less suitable for teams seeking a managed service, or for anyone planning to expose the wiki without taking ownership of its disabled-by-default protections and unauthenticated file and search access.

Pros and cons

Pros: Specifications can be executed as tests, keeping expected behavior close to requirements and making regression checks part of the same workflow.
Pros: Built-in FIT and SLIM systems, JUnit and Maven execution, and a range of testing fixtures give teams multiple integration paths.
Pros: The software is free and self-hosted, with no commercial-plan costs stated.
Cons: Teams must run and maintain a Java application and may need to increase JVM heap for extensive testing.
Cons: Read, write, and test protections are disabled by default, while search and /files access remain unauthenticated.
Cons: SSL guidance for test-system-to-application traffic applies only to the SLIM Java client.

Alternatives

Browse BDD Testing Tools for a broader set of behavior-driven development options. Choose Cucumber Open for a free option spanning Android, API, Linux, macOS, and Windows. Godog is another free, self-hosted API option, though its API may change before version 1.0.0. Choose Karate if you want a free MIT-licensed framework spanning REST, GraphQL, and SOAP API testing as well as browser and desktop UI automation. Ginkgo is a free Go testing framework for Linux, macOS, and Windows. Behat is free software for Linux, provided without warranty. CukeTest offers a free Lite plan with visual feature editing and JavaScript and Python support, alongside usage limits on some built-in automation libraries. Reqnroll may suit teams seeking Visual Studio or Rider integration, community plugins, and community support on its free Community plan. Serenity BDD is a free open-source library available across Android, iOS, Linux, macOS, self-hosted, web, and Windows environments.

Verdict

Choose FitNesse if your team wants acceptance requirements to double as runnable checks and is prepared to host and secure the Java application. Its combination of executable wiki pages and broad test integrations is the reason to choose it; default access settings and the work of operating the server are the reasons to look elsewhere.

	FitNesse	JBehave
Free plan	Yes	Yes
Free trial	No	No
Paid from	Free	Free
Open source	No	No
Platforms	api, Linux, macOS, self-hosted, Web, Windows	self-hosted
Free plan	Yes	Yes
Gherkin support	Yes	Yes
Execution mode	local	both
Browser testing	Yes	Yes
API access	Yes	Yes

FitNesse vs JBehave

FitNesse

JBehave