Overview

FitNesse connects acceptance criteria with tests that check expected application behavior, giving stakeholders a shared place to document requirements and catch regressions. Pages are editable in a browser with wiki syntax or a rich-text editor, and people with web access to the server can run tests manually or automatically. That keeps documentation close to verification; the trade-off is that teams must deploy and operate the application themselves.

The project began in 2001 as a wiki and HTML front end to FIT. It is distributed as a Java jar, stores wiki pages as files, and is released under the Common Public License version 1.0.

Key features

Executable specifications

FitNesse includes FIT and SLIM test systems, and tests can also run from JUnit or Maven. The core is Java, while extensions enable testing in other languages and environments. This is a good fit when teams want acceptance criteria to become repeatable checks, though they must select and maintain the test setup that matches their application.

Integrations and test coverage

Listed plugins cover Maven, Ivy, Gradle, Git, TFS, and SVN-related support. Fixtures include Selenium-based browser testing, REST API and HTTP testing, PDF checks, and email retrieval. The breadth can support varied workflows, but it also leaves integration choices and upkeep with the team.

Access and transport security

Reading, writing, and testing permissions can be controlled separately, but all three protections are disabled by default. Search and related queries do not require authentication, and unauthenticated readers can access files in the /files directory. Teams handling restricted content should configure authentication and review those paths before relying on the wiki. The security guidance recommends SSL for network traffic and password-cipher authentication; SSL for test-system-to-application communication is limited to the SLIM Java client.

Deployment and capacity

The download guidance supports Java 11, 17, and 21 and notes that extensive use may exceed the JVM's default memory allocation. Increasing the heap may be necessary when tests fail for lack of memory, so larger suites bring an operational consideration beyond writing the checks.

Pricing

FitNesse is free: its open-source plan costs 0.00 USD per free. There is no free trial because the project is already free, and no commercial plans or limits are stated. This makes it a straightforward option for teams able to manage deployment and maintenance without a paid hosted tier.

Platforms

FitNesse supports API, Linux, macOS, Windows, web, and self-hosted use. Its local execution model and Java runtime requirement suit teams that can run the jar on a machine or server; it is not presented as a hosted service.

Who it's for

Choose FitNesse if delivery stakeholders need browser-editable requirements that can also run as acceptance tests, and the team is prepared to administer a Java server and its security settings. Look elsewhere if you need access protections enabled out of the box or want deployment handled for you.

Pros and cons

Pros: Requirements and runnable checks share wiki pages, helping teams keep acceptance criteria aligned with application behavior.
Pros: Built-in FIT and SLIM systems, JUnit and Maven execution, and plugins and fixtures for several build, version-control, browser, and service-testing workflows offer flexibility.
Pros: The project is free, with no commercial plans or limits stated.
Cons: The Java jar and server require local deployment and operational ownership.
Cons: Read, write, and test protections are off by default, while some queries and files remain accessible without authentication.
Cons: Extensive test use may require increasing the JVM heap.

Alternatives

Serenity BDD is another free option with broad platform support; its JUnit 4 support is deprecated and planned for removal in Serenity 6.0.0. Cucumber Open is a free project with Android and API platform support. Ginkgo is a free Go testing framework whose current supported major version is v2. CukeTest may suit teams wanting visual feature editing and JavaScript or Python, though its Lite plan has usage limits on some built-in automation libraries and 500 automation API calls. Karate is a free MIT-licensed framework for REST, GraphQL, and SOAP API testing, browser and desktop UI automation, and Gatling performance testing. Reqnroll offers a free Community plan with Visual Studio and Rider integration, community plugins, and support. Behat is free software provided without warranty. Godog is a free MIT-licensed option for API and self-hosted use, though its API may change before version 1.0.0. Browse BDD Testing Tools for more options.

Verdict

FitNesse is a strong choice for teams that want acceptance criteria to double as runnable checks and can take responsibility for a Java deployment. Its free, extensible approach is the main draw; the default-open access controls and server upkeep are the clearest reasons to choose another tool.

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

Chorus BDD vs FitNesse

Chorus BDD

FitNesse