StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Testing Frameworks
  4. Testing Frameworks
  5. Cypress vs FitNesse

Cypress vs FitNesse

OverviewDecisionsComparisonAlternatives

Overview

FitNesse
FitNesse
Stacks32
Followers62
Votes0
GitHub Stars2.1K
Forks712
Cypress
Cypress
Stacks3.5K
Followers2.0K
Votes115
GitHub Stars49.4K
Forks3.4K

Cypress vs FitNesse: What are the differences?

<Write Introduction here>
  1. Testing Approach: Cypress is primarily focused on end-to-end testing of web applications, providing tools for testing the user experience. In contrast, FitNesse is more oriented towards acceptance testing, allowing users to create and execute tests directly against the application's specifications.

  2. Technology Stack: Cypress is built on JavaScript and utilizes its ecosystem for writing test scripts, while FitNesse relies on Java for creating test cases. This difference in technology stack can influence the ease of integration and the learning curve for users familiar with a specific programming language.

  3. Real-time Testing: Cypress provides a live reloading feature that allows developers to see the impact of code changes in real time, making debugging and code modifications more efficient. FitNesse, on the other hand, typically requires manual test execution, making it more suitable for scenarios where real-time feedback is not essential.

  4. Community Support: Cypress has a more active and rapidly growing community compared to FitNesse, resulting in regular updates, plugins, and community-contributed resources that enhance the testing experience. FitNesse, while established, may have a smaller community and fewer resources available for users seeking help or customization options.

  5. Execution Speed: Cypress is known for its fast test execution speed, as it runs tests directly in the browser and can parallelize test runs for quicker results. FitNesse, on the other hand, may have slower test execution times due to its architecture and setup requirements, impacting the efficiency of testing workflows.

  6. User Interface: Cypress offers a sleek and user-friendly interface that enables developers and testers to write and visualize tests easily, providing detailed insights into test results and interactions with the application. FitNesse, while functional, may have a more complex and less intuitive interface that requires some learning curve for new users.

In Summary, Cypress and FitNesse differ in their testing approach, technology stack, real-time testing capabilities, community support, execution speed, and user interface, impacting the user experience and efficiency of test automation workflows.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on FitNesse, Cypress

Dane
Dane

Feb 7, 2020

Needs adviceonCypressCypressJestJest

As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.

836k views836k
Comments
Yildiz
Yildiz

testmanager/automation tester at medicalservice

May 12, 2020

Needs adviceonAngularJSAngularJSTypeScriptTypeScriptCypressCypress

In the company I will be building test automation framework and my new company develops apps mainly using AngularJS/TypeScript. I was planning to build Protractor-Jasmine framework but a friend of mine told me about Cypress and heard that its users are very satisfied with it. I am trying to understand the capabilities of Cypress and as the final goal to differentiate these two tools. Can anyone advice me on this in a nutshell pls...

277k views277k
Comments

Detailed Comparison

FitNesse
FitNesse
Cypress
Cypress

It is an open source project. The code base is not owned by any company. A lot of information is shared by the FitNesse community. It's extremely adaptable and is used in areas ranging from Web/GUI tests to testing electronic components.

Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.

FitNesse is an easy to use wiki web server;Easy to set up: just download the application (a Java jar file) and start it;Specifications/requirements can be used as test input;The major languages are supported
Time Travel; Debuggability; Automatic Waiting; Spies, Stubs, and Clocks; Network Traffic Control; Consistent Results; Screenshots and Videos
Statistics
GitHub Stars
2.1K
GitHub Stars
49.4K
GitHub Forks
712
GitHub Forks
3.4K
Stacks
32
Stacks
3.5K
Followers
62
Followers
2.0K
Votes
0
Votes
115
Pros & Cons
No community feedback yet
Pros
  • 29
    Open source
  • 22
    Great documentation
  • 20
    Simple usage
  • 18
    Fast
  • 10
    Cross Browser testing
Cons
  • 21
    Cypress is weak at cross-browser testing
  • 14
    Switch tabs : Cypress can'nt support
  • 12
    No iFrame support
  • 9
    No multiple domain support
  • 9
    No page object support
Integrations
Karate DSL
Karate DSL
Java
Java
No integrations available

What are some alternatives to FitNesse, Cypress?

Mocha

Mocha

Mocha is a feature-rich JavaScript test framework running on node.js and the browser, making asynchronous testing simple and fun. Mocha tests run serially, allowing for flexible and accurate reporting, while mapping uncaught exceptions to the correct test cases.

Jasmine

Jasmine

Jasmine is a Behavior Driven Development testing framework for JavaScript. It does not rely on browsers, DOM, or any JavaScript framework. Thus it's suited for websites, Node.js projects, or anywhere that JavaScript can run.

Jest

Jest

Jest provides you with multiple layers on top of Jasmine.

Robot Framework

Robot Framework

It is a generic test automation framework for acceptance testing and acceptance test-driven development. It has easy-to-use tabular test data syntax and it utilizes the keyword-driven testing approach. Its testing capabilities can be extended by test libraries implemented either with Python or Java, and users can create new higher-level keywords from existing ones using the same syntax that is used for creating test cases.

Karate DSL

Karate DSL

Combines API test-automation, mocks and performance-testing into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Besides powerful JSON & XML assertions, you can run tests in parallel for speed - which is critical for HTTP API testing.

CodeceptJS

CodeceptJS

It is a modern end to end testing framework with a special BDD-style syntax. The test is written as a linear scenario of user's action on a site. Each test is described inside a Scenario function with I object passed into it.

Cucumber

Cucumber

Cucumber is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs.

Protractor

Protractor

Protractor is an end-to-end test framework for Angular and AngularJS applications. Protractor runs tests against your application running in a real browser, interacting with it as a user would.

AVA

AVA

Even though JavaScript is single-threaded, IO in Node.js can happen in parallel due to its async nature. AVA takes advantage of this and runs your tests concurrently, which is especially beneficial for IO heavy tests. In addition, test files are run in parallel as separate processes, giving you even better performance and an isolated environment for each test file.

TestCafe

TestCafe

It is a pure node.js end-to-end solution for testing web apps. It takes care of all the stages: starting browsers, running tests, gathering test results and generating reports.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana