FitNesse vs. SpecFlow

Useful and straightforward. Appian and other low-code BCM tools can be easily integrated. Writing a script for a test is similar to writing a script in English. So simple to use because it's a wrapper class for selenium. FitNesse is being implemented with the goal of doing it correctly the first time. As a result, migrations of both the client and the server are made easier.

Incentivized

It is best suited for implementing the automated test cases in a human readable form so it's easy for non-technical members of the team and stakeholders to understand the test cases, features and the functionalities of the application. Automation of Integration tests and End to End tests are good use case. It is less appropriate or situations where the focus is only on the writing and maintenance of unit tests.

Incentivized

• This program makes it simple to do both integration and acceptability testing.
• FitNesse was a huge asset to us when it came to rule testing.
• Scripting with command language is simple.

Incentivized

• Versatility to be used in combination with different kinds of automated testing like automated performance testing, API testing, UI testing etc. I use JavaScript, Selenium, C#, email testing libraries, database testing libraries in combination with BDD with SpecFlow. I am able to use all these with SpecFlow to make my automation framework to be able to automate any kind of automated testing.
• It provides different widely used runner options like NUnit, XUnit etc. Before I started to work on establishing proper test automation in my workplace, the previous automation framework (non-BDD based) as well as unit tests used NUnit runner. The transition to using BDD was smooth because we could use the same runner and there were no compatibility issues.
• The auto-complete feature is good. I use it with Visual Studio as well as Rider and I don't have to recall the entire Gherkin statements. I just type a few words and the entire Gherkin statement implemented in framework is auto-suggested by SpecFlow. It saves time and context switching.

Incentivized

• Limitations with rich text fields.
• FitNesse cannot properly read the interface if labels or accessibility text is not available.
• Not used for Web interface testing.

Incentivized

• SpecFlow does not accepts optional input variables in the methods defined during Gherkin statement implementation. Cucumber supports optional input variables in the methods defined during Gherkin statement implementation.
• The tests identified while using SpecFlow with NUnit removes all white spaces in the scenario names. It makes the tests less readable. If the white spaces are not auto-removed, it would be much better for readability as well as their actual identification in the repository.

Incentivized

The FitNesse testing automation framework is very simple to operate. It is simple to connect with the Jenkins and Bamboo environments. It is dependable, and it is simple and quick to include new tests. The process of debugging and fixing test failures is straightforward. FitNesse, including its installation, may be utilized with a minimum of fuss and difficulty. Maintaining scripts and monitoring their output is designed to be a relatively straightforward process.

Incentivized

SpecFlow is .Net based which supports C#. Behave is Python based. Cucumber is Java based. Ghost Inspector is no-code based but provides very limited testing features. We wanted to implement BDD so we rued out using Ghost Inspector. Most of the developers in my team are C# experts so it was decided for everyone's comfort to go for SpecFlow rather than Behave or Cucumber. It's import to have technical experts in the language of the automation framework because there are many situations where the solutions to the test automation needs are not straightforward and implementing those requires expertise in the related programming language.

Incentivized

• Saves developer time on regression testing.
• Developers can spend time on other prioritizes while FitNesse runs regression testing.
• Transitioning into another testing platform would be costly.

Incentivized

• Everyone stays on the same page regarding the behavior of existing functionalities whether it be technical or non-technical individuals. So there is less need for multiple people to get involved which saves time and thus money.
• Reusing the same code through the implemented Gherkin statement saves test automation time and thus reduces cost.
• We combine SpecFlow with other opensource testing technologies to make our automation framework more versatile which further saves costs for us.

Incentivized