fitnesse VS Cucumber.js

(I notified the Martin and the FitNesse user mailing list about this back in 2010. I assume their threat model is that the default hash function is about the same as a closed office door - a request to stay out, or at least knock first - rather than a strong preventative measure.)

"Uncle" Bob Martin's "FitNesse", see https://en.wikipedia.org/wiki/FitNesse and http://fitnesse.org/ , uses its own hash function, at https://github.com/unclebob/fitnesse/blob/master/src/fitness... .

The Python equivalent is:

    import base64

Cucumber is not the first failed test framework that uses English-like syntax for automated testing (it may be for other uses, but definitely not real test automation). Do you still remember FitNesse (it was quite big about 10 years ago, an example here)? Now it is hardly mentioned.

I fell in love with that framework back in the 00s so much that I bought the book, but pragmatically unless the domain expert is willing to write the tests, or specify requirements, it's a non-starter. I also think that Cucumber and its derivatives are the modern version of Fitnesse, but suffer from the same "requirements aren't Agile" problem for sure

Also, it took an inordinate number of clicks to find the modern source code, which has an unusual license: https://github.com/unclebob/fitnesse/blob/master/LICENSE.txt ("Common Public License Version 1.0"); a cursory search seems to imply it's the precursor to the Eclipse Public License, but I still can't recall the last time I saw CPL in use

The only known project that he contributed (and constantly mentioned in his videos) - FitNesse (https://github.com/unclebob/fitnesse), but 59 commits doesn't make him look like expert.

You may find interesting to look for open source projects claimed to be TDD and see what their tests are, like fitnesse

The only one I can think of that may be done with TDD is Uncle Bobs fitnesse: https://github.com/unclebob/fitnesse.

Another resource that takes you through a practical approach of TDD is the book “Growing Object-Oriented Software Guided by tests”(https://www.programmingbooks.dev/extra/#growing-object-orien...). It’s a great book and really helps to take the concepts of TDD into practice.

He's #7 contributor, with 59 commits in 4 years.

In-house testing tools help you to differentiate what people say and what they actually do with a product by testing it. FitNesse and Bugwolf are pretty good at this.

The article quotes a code sample from FitNesse – the author has apparently maintained that codebase since then. You can check out the code for the current version at https://github.com/unclebob/fitnesse, or browse the code in a Monaco editor using https://github1s.com/unclebob/fitnesse/blob/HEAD/src/. (I have no idea if that code is “well-regarded”, but as you wrote, you can read it for yourself.)

What you're describing is most commonly known as acceptance testing, or behavior-driven tests. There's an excellent framework for this called Cucumber. They have gems for both plain Ruby and Rails.

It is a known fact that before any developer pushes the code (either to the development environment or Staging environment before migrating to the Production environment), he would be performing unit testing on the code changes that he has made. For unit testing, developers have a variety of unit-testing frameworks to choose from. JUnit and Jasmine are the most popular unit-testing frameworks. Other types of tests performed at a module/package level are functional tests and visual regression tests. Cucumber is a popular choice for Behavior-Driven Development (BDD) or functional testing, and a visual screenshot comparison tool named Wraith is preferred for performing visual regression testing.

Some BDD frameworks such as JBehave, RSpec, Mocha, Jasmine, Cucumber, among others, embrace the use of this template. Spek is not an exception to this rule. The main difference is that it doesn’t force you to use a concrete assertion framework or additional behavioral files (e.g Cucumber or JBehave).

There are a lot of more or less good testing frameworks in the wild. Some of existing testing frameworks doing their job very well and are de facto a standard, like a "cucumber" for BDD testing.

Just to add, anyone who is curious to learn more about BDD I would recommend checking out the Javascript flavor of Cucumber. It's cool stuff and immensely useful! https://github.com/cucumber/cucumber-js

And pretty deep into that rabbit hole you get Cucumber and the Gherkin language (https://cucumber.io/); project managers write "natural English" unit tests, but to get them to work, the developers write essentially a chatbot interpreter to process the files and run them.

Cucumber is an automation tool based on the BDD framework, using which you can write automated acceptance tests for web applications in the Gherkin language.

Many testing frameworks use Domain Specific Languages (DSLs) to define tests in plain English. Perhaps the most notable example is Gherkin, the language used by the Cucumber testing framework: