Alternatives to FitNesse logo

Alternatives to FitNesse

Selenium, Cucumber, SpecFlow, Postman, and Cypress are the most popular alternatives and competitors to FitNesse.
23
47
+ 1
0

What is FitNesse and what are its top alternatives?

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.
FitNesse is a tool in the Testing Frameworks category of a tech stack.
FitNesse is an open source tool with 1.8K GitHub stars and 670 GitHub forks. Here’s a link to FitNesse's open source repository on GitHub

Top Alternatives to FitNesse

  • Selenium

    Selenium

    Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well. ...

  • 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. ...

  • SpecFlow

    SpecFlow

    It is used to define, manage and automatically execute human-readable acceptance tests in .NET projects. Writing easily understandable tests is a cornerstone of the BDD paradigm and also helps build up a living documentation of your system. ...

  • Postman

    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Cypress

    Cypress

    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. ...

  • JUnit

    JUnit

    JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks. ...

  • PHPUnit

    PHPUnit

    PHPUnit is a programmer-oriented testing framework for PHP. It is an instance of the xUnit architecture for unit testing frameworks. ...

  • Mockito

    Mockito

    It is a mocking framework that tastes really good. It lets you write beautiful tests with a clean & simple API. It doesn’t give you hangover because the tests are very readable and they produce clean verification errors. ...

FitNesse alternatives & related posts

Selenium logo

Selenium

11.3K
8.8K
520
Web Browser Automation
11.3K
8.8K
+ 1
520
PROS OF SELENIUM
  • 170
    Automates browsers
  • 154
    Testing
  • 101
    Essential tool for running test automation
  • 24
    Record-Playback
  • 24
    Remote Control
  • 8
    Data crawling
  • 7
    Supports end to end testing
  • 6
    Functional testing
  • 6
    Easy set up
  • 4
    The Most flexible monitoring system
  • 3
    Easy to integrate with build tools
  • 3
    End to End Testing
  • 2
    Integration Tests
  • 2
    Comparing the performance selenium is faster than jasm
  • 2
    Record and playback
  • 2
    Compatible with Python
  • 2
    Easy to scale
  • 0
    Integrated into Selenium-Jupiter framework
CONS OF SELENIUM
  • 7
    Flaky tests
  • 2
    Slow as needs to make browser (even with no gui)

related Selenium posts

Kamil Kowalski
Lead Architect at Fresha · | 27 upvotes · 1.2M views

When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

See more
Benjamin Poon
QA Manager - Engineering at HBC Digital · | 8 upvotes · 771.4K views

For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

See more
Cucumber logo

Cucumber

743
728
32
Simple, human collaboration.
743
728
+ 1
32
PROS OF CUCUMBER
  • 20
    Simple Syntax
  • 5
    Simple usage
  • 4
    Huge community
  • 3
    Nice report
CONS OF CUCUMBER
    Be the first to leave a con

    related Cucumber posts

    Benjamin Poon
    QA Manager - Engineering at HBC Digital · | 8 upvotes · 771.4K views

    For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

    With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

    See more
    Sarah Elson
    Product Growth at LambdaTest · | 4 upvotes · 334.1K views

    @producthunt LambdaTest Selenium JavaScript Java Python PHP Cucumber TeamCity CircleCI With this new release of LambdaTest automation, you can run tests across an Online Selenium Grid of 2000+ browsers and OS combinations to perform cross browser testing. This saves you from the pain of maintaining the infrastructure and also saves you the licensing costs for browsers and operating systems. #testing #Seleniumgrid #Selenium #testautomation #automation #webdriver #producthunt hunted

    See more
    SpecFlow logo

    SpecFlow

    64
    64
    0
    A testing framework which supports Behaviour Driven Development
    64
    64
    + 1
    0
    PROS OF SPECFLOW
      Be the first to leave a pro
      CONS OF SPECFLOW
        Be the first to leave a con

        related SpecFlow posts

        Postman logo

        Postman

        66.4K
        54.4K
        1.8K
        Only complete API development environment
        66.4K
        54.4K
        + 1
        1.8K
        PROS OF POSTMAN
        • 486
          Easy to use
        • 369
          Great tool
        • 275
          Makes developing rest api's easy peasy
        • 156
          Easy setup, looks good
        • 143
          The best api workflow out there
        • 53
          It's the best
        • 53
          History feature
        • 44
          Adds real value to my workflow
        • 42
          Great interface that magically predicts your needs
        • 34
          The best in class app
        • 11
          Can save and share script
        • 9
          Fully featured without looking cluttered
        • 7
          Option to run scrips
        • 7
          Collections
        • 7
          Global/Environment Variables
        • 6
          Dead simple and useful. Excellent
        • 6
          Dark theme easy on the eyes
        • 6
          Shareable Collections
        • 5
          Great integration with newman
        • 5
          Awesome customer support
        • 4
          Documentation
        • 4
          The test script is useful
        • 4
          Simple
        • 3
          Makes testing API's as easy as 1,2,3
        • 3
          Easy as pie
        • 3
          Saves responses
        • 3
          This has simplified my testing significantly
        • 2
          API-network
        • 2
          Mocking API calls with predefined response
        • 2
          I'd recommend it to everyone who works with apis
        • 1
          Graph
        • 1
          Pre-request Script and Test attributes are invaluable
        • 1
          Continuous integration using newman
        • 1
          Now supports GraphQL
        • 1
          Postman Runner CI Integration
        • 1
          Easy to setup, test and provides test storage
        • 0
          Runner
        • 0
          <a href="http://fixbit.com/">useful tool</a>
        CONS OF POSTMAN
        • 9
          Stores credentials in HTTP
        • 7
          Poor GraphQL support
        • 7
          Bloated features and UI
        • 6
          Cumbersome to switch authentication tokens
        • 2
          Expensive
        • 1
          Support websocket
        • 1
          Import curl
        • 1
          Import swagger
        • 1
          Can't prompt for per-request variables

        related Postman posts

        Noah Zoschke
        Engineering Manager at Segment · | 30 upvotes · 2.1M views

        We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

        Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

        Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

        This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

        Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

        Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

        Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

        See more
        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.2M views

        Our whole Node.js backend stack consists of the following tools:

        • Lerna as a tool for multi package and multi repository management
        • npm as package manager
        • NestJS as Node.js framework
        • TypeScript as programming language
        • ExpressJS as web server
        • Swagger UI for visualizing and interacting with the API’s resources
        • Postman as a tool for API development
        • TypeORM as object relational mapping layer
        • JSON Web Token for access token management

        The main reason we have chosen Node.js over PHP is related to the following artifacts:

        • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
        • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
        • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
        • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
        See more
        Cypress logo

        Cypress

        1.3K
        1.5K
        102
        When testing is easy, developers build better things faster and with confidence.
        1.3K
        1.5K
        + 1
        102
        PROS OF CYPRESS
        • 25
          Open source
        • 19
          Great documentation
        • 17
          Simple usage
        • 17
          Fast
        • 10
          Cross Browser testing
        • 9
          Easy us with CI
        • 4
          Npm install cypress only
        • 1
          Good for beginner automation engineers
        CONS OF CYPRESS
        • 19
          Cypress is weak at cross-browser testing
        • 12
          Switch tabs : Cypress can'nt support
        • 11
          No iFrame support
        • 8
          No file upload support
        • 8
          No xPath support
        • 8
          No multiple domain support
        • 8
          No page object support
        • 7
          Re-run failed tests retries not supported yet
        • 7
          Cypress doesn't support native app
        • 7
          No support for multiple tab control
        • 6
          No support for multiple browser control
        • 6
          No support for Safari
        • 4
          $20/user/thread for reports
        • 4
          Not freeware
        • 4
          Adobe
        • 3
          No 'WD wire protocol' support
        • 3
          Using a non-standard automation protocol

        related Cypress posts

        Kamil Kowalski
        Lead Architect at Fresha · | 27 upvotes · 1.2M views

        When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

        See more
        Robert Zuber

        We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

        See more
        JUnit logo

        JUnit

        1.4K
        466
        0
        A programmer-oriented testing framework for Java
        1.4K
        466
        + 1
        0
        PROS OF JUNIT
          Be the first to leave a pro
          CONS OF JUNIT
            Be the first to leave a con

            related JUnit posts

            We are looking for a Testing Tool that can integrate with Java/ React/ Go/ Python/ Node.js. Which amongst the three tools JUnit, NUnit & Selenium would be the best for this use case?

            See more
            Joshua Dean Küpper
            CEO at Scrayos UG (haftungsbeschränkt) · | 1 upvote · 147.4K views

            We use JUnit for our Java Unit and Integration tests in Version 5. Combined with @JMockit2 and @truth (from Google) we perform all kinds of tests on our minecraft, standalone and microservice architecture.

            We prefer JUnit over TestNG because of the bigger community, better support and the generally more agile development. JUnit integrates nicely with most software, while TestNG support is a little more limited.

            See more
            PHPUnit logo

            PHPUnit

            465
            225
            12
            Testing framework for PHP
            465
            225
            + 1
            12
            PROS OF PHPUNIT
            • 4
              TDD Unit Testing
            • 2
              TDD Integration Testing
            • 2
              TDD Acceptance Testing
            • 1
              Software Quality
            • 1
              TDD Unit Testing
            • 1
              Unit Testing
            • 1
              The de facto standard for xUnit testing in PHP
            CONS OF PHPUNIT
            • 1
              Mocked services require more effort and understanding

            related PHPUnit posts

            Shared insights
            on
            BehatBehatPHPUnitPHPUnit

            What is the best solution (PHPUnit or Behat) for test automation (unit and functional tests)?

            See more
            Mockito logo

            Mockito

            444
            123
            0
            Tasty mocking framework for unit tests in Java
            444
            123
            + 1
            0
            PROS OF MOCKITO
              Be the first to leave a pro
              CONS OF MOCKITO
                Be the first to leave a con

                related Mockito posts