FitNesse
fitnesse.org
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What FitNesse is
FitNesse is a free acceptance-test wiki for documenting application requirements and checking them against software behavior. Delivery stakeholders can write executable specifications as wiki pages, then run those pages as tests to check expected results and catch regressions. Pages can be edited in a browser with wiki syntax or a rich-text editor, and tests can be run manually or automatically by anyone with web access to the server. FitNesse is distributed as a Java jar and stores wiki pages as files. It requires Java Runtime Environment version 11; supported versions listed are Java 11, 17, and 21. Fit and Slim are built-in test systems, and tests can also run from JUnit or Maven. Extensions and fixtures cover integrations such as Git, Gradle, Selenium, REST and HTTP testing, PDF checks, and email retrieval. Page controls can restrict reading, writing, and testing, but are disabled by default. Search queries and files under /files may remain accessible without authentication unless protections are configured.
Who it suits
FitNesse suits software delivery teams that want requirements documented as runnable acceptance tests. It may also fit teams using Java or extensions to test other languages and environments.
Good to know, and what to watch
- Free, with no commercial plans or limits stated.
- Browser editing supports wiki syntax and rich text.
- Built-in Fit and Slim test systems.
- Listed plugins cover Maven, Git, Selenium, and REST testing.
- Page reading, writing, and testing restrictions are disabled by default.
- Search queries and /files may be accessible without authentication.
- Extensive use may require increasing the JVM memory allocation.
Plans
Every plan and priceFitNesse
Free plan
Getting started
- Install Java Runtime Environment 11, 17, or 21
- Download the FitNesse Java jar
- Run it on a machine or server
- Open the wiki in a browser and create pages with wiki syntax or the rich-text editor
- Configure Fit or Slim and any required plugins or fixtures
- Enable authentication and page protections before sharing access
Limits to check
Extensive use can exceed the JVM's default memory allocation, so the documentation suggests increasing heap size when tests fail for lack of memory. Reading, writing, and testing protections are disabled by default until configured.
The Club's review
FitNesse is a free, self-hosted wiki for turning acceptance criteria into executable tests. It suits delivery teams that want product stakeholders and developers working from the same requirements, provided they are prepared to run and secure a Java application. Its central advantage is traceability between what the software should do and checks that can expose regressions.
Overview
FitNesse began in 2001 as an HTML and wiki front end to FIT. Today, stakeholders can document requirements in browser-editable pages, using wiki syntax or a rich-text editor, then run those pages against an application. Anyone who can reach the server may run checks manually or automatically, making the wiki a shared acceptance record rather than a document that goes stale beside the test suite.
The trade-off is operational ownership. FitNesse arrives as a Java jar, stores wiki pages as files, and runs on a machine or server. Java Runtime Environment 11 is required; Java 11, 17, and 21 are supported. Teams must provide the runtime, deployment, backups and capacity management themselves.
Key features
Executable specifications
FIT and SLIM are built-in test systems, and tests can also be launched from JUnit or Maven. The Java core can be extended for other languages and environments. This combination is valuable when acceptance criteria need to become repeatable checks, but it also leaves teams responsible for choosing fixtures and maintaining the integration code that connects specifications to their application.
Broad test reach
Listed extensions cover Maven, Ivy, Gradle, Git, TFS and SVN-related workflows. Fixtures include Selenium browser checks, REST and HTTP testing, PDF verification and email retrieval. That breadth can keep web, service and document scenarios in one acceptance workspace; it does not remove the engineering work of wiring those systems together.
Editing and collaboration
Browser editing lowers the barrier for non-developers to review or update criteria, while executable pages give developers an immediate verification path. Gherkin support, API access and local execution add options for teams with established behavior-driven or service-testing practices.
Security and operation
Reading, writing and testing permissions can be controlled independently, which is useful for separating authoring from execution. Those protections are disabled by default, however. Search and related queries do not require authentication, and unauthenticated readers can access files in the /files directory. SSL guidance covers browser-to-wiki traffic and test-system-to-application traffic, with the latter limited to the SLIM Java client; password-cipher authentication is also recommended. These settings make deployment discipline essential. Extensive test use may exceed the JVM's default memory allocation, so failed memory-heavy runs can require a larger heap.
Pricing
FitNesse — free. This is an open-source project with no commercial plans or stated usage limits. There is no free trial because the software is free outright. The absence of seat or quota charges suits teams willing to operate their own instance; it also means infrastructure, Java maintenance and security configuration remain their responsibility.
Platforms
FitNesse supports API, Linux, macOS, Windows, web and self-hosted deployments. Its local execution model and Java packaging suit organizations that need control over where pages and test systems run, rather than a vendor-hosted workspace.
Who it's for
Choose FitNesse when analysts, testers and developers need a shared requirements wiki whose pages can execute against the application. It is particularly appropriate for Java-oriented teams or groups comfortable extending a Java tool and integrating build, browser and service checks. It is a weaker fit for organizations seeking a managed SaaS product, minimal administration, or security that is safe without deliberate configuration.
Pros and cons
- Pro: Requirements and runnable acceptance checks live together, helping teams detect drift and regressions.
- Pro: FIT, SLIM, JUnit and Maven execution plus browser and API fixtures cover varied acceptance scenarios.
- Pro: Free, open-source distribution avoids per-seat or test-volume charges.
- Con: Self-hosting a Java jar and managing file-based pages adds deployment and maintenance work.
- Con: Access controls are off by default, with unauthenticated search and /files exposure creating avoidable risk until configured.
- Con: Large suites can require JVM heap tuning when default memory is exhausted.
Alternatives
For a visual editor with JavaScript and Python support, a free tier and a 500-call automation quota, choose CukeTest; its Lite plan limits some built-in automation libraries and offers a free trial.
Serenity BDD is a free open-source library spanning web and desktop platforms, though JUnit 4 support is deprecated and planned for removal in Serenity 6.0. Cucumber Open is another free open-source option with free Cucumber Reports. Ginkgo is a free Go testing framework, currently on major version 2.
Choose Karate for a free-forever MIT-licensed framework centered on REST, GraphQL and SOAP APIs with browser and desktop UI automation, or Reqnroll when .NET teams want Visual Studio and Rider integration, community plugins and support through its Community plan. BddDotNet is free MIT-licensed software for Linux, macOS and Windows. Concordion is a free Java library under Apache License 2.0.
Browse more options in BDD Testing Tools.
Verdict
FitNesse is a strong choice for teams that want acceptance criteria to remain executable and collaboratively editable without subscription costs. Pick it when self-hosting and Java-based integration are acceptable; look elsewhere if you need a managed service or secure defaults that demand less operational attention.
The verdict
FitNesse combines requirement documentation with executable acceptance checks in a wiki. Teams should configure access controls and network protections before exposing it to users.
Questions people ask
How much does FitNesse cost?
FitNesse is free and open source under the Common Public License version 1.0. No commercial plans or limits are stated.
Which platforms can run it?
It supports Linux, macOS, Windows, self-hosted deployments, web access, and API use. It is distributed as a Java jar.
What Java versions are supported?
Java Runtime Environment version 11 is required, with Java 11, 17, and 21 listed as supported.
Can FitNesse test web and APIs?
Listed fixtures include Selenium-based web testing, REST API testing, and HTTP testing. PDF checks and email retrieval are also listed.
Are page permissions enabled automatically?
No. Reading, writing, and testing can be restricted separately, but those protections are disabled by default.
What security caveats apply?
The security guide says search and related queries do not require authentication, and unauthenticated readers can access files in the /files directory unless additional protections are configured.
What the maker publishes
- Acceptance testing
- FitNesse is a tool for specifying and verifying application acceptance criteria and keeping documentation aligned with software behavior. source
- Access controls
- Pages can independently require authentication for reading, writing, or testing; these controls are disabled by default unless configured. source
- Collaboration
- Its wiki lets software delivery stakeholders document requirements and verify them against the application. source
- Editing
- Pages can be edited in a browser using wiki syntax or a rich-text editor. source
- Executable specifications
- Wiki pages can be run as tests against an application to check expected results and catch regressions. source
- Founded
- 2001 source
- History
- The user guide says FitNesse started as an HTML and wiki front end to FIT in 2001. source
- Integrations
- The plugins page lists extensions for Maven, Ivy, Gradle, Git, Selenium, and REST service testing. source
- Java requirement
- The download page says FitNesse requires Java Runtime Environment version 11 and lists Java 11, 17, and 21 as supported. source
- Language support
- The core is written in Java and extensions allow testing in other languages and environments. source
- License
- FitNesse is released under the Common Public License version 1.0. source
- Network security
- The documentation describes SSL configuration for browser-to-wiki and test-system-to-application communication, with the latter limited to the SLIM Java client. source
- Operational limit
- The download guide says extensive use may exceed the JVM's default memory allocation and suggests increasing the heap when tests fail for lack of memory. source
- Purpose
- FitNesse is an acceptance-test wiki for specifying and verifying application acceptance criteria. source
- Runtime requirement
- The download page lists Java 11, 17, and 21 as supported versions. source
- Security
- Page security can separately restrict reading, writing, and testing, and all three protections are disabled by default. source
- Security caveat
- The security guide says search and related queries do not require authentication, and unauthenticated readers can read files in the /files directory. source
- Setup
- FitNesse is distributed as a Java jar and can run on a machine or server; wiki pages are stored as files. source
- Test feedback
- The site says tests can be run manually or automatically by anyone with web access to the server. source
- Test systems
- The user guide lists Fit and Slim as built-in test systems, with tests runnable from JUnit or Maven. source
- Tool integrations
- Listed plugins include Maven, Ivy, Gradle, Git, TFS, and SVN-related support. source
- Transport security
- The network security guide recommends encrypting and authenticating network traffic with SSL and enabling user authentication with a password cipher. source
- Web and service testing
- Listed fixtures include Selenium-based web testing, REST API testing, HTTP testing, PDF checks, and email retrieval. source
Checked against the maker's pages on 4 Oct 2026.