SpecFlow vs Shoulda comparison of testing frameworks
What are the differences between SpecFlow and Shoulda?

	SpecFlow https://specflow.org/	Shoulda https://github.com/thoughtbot/shoulda
Programming language	.NET	Ruby
Category	Acceptance Testing
General info	SpecFlow is a test automation solution for .NET SpecFlow is a test automation solution for .NET which follows the BDD paradigm, and is part of the Cucumber family. SpecFlow tests are written with Gherkin, using the official Gherkin parser which allows you to write test cases using natural languages and supports over 70 languages.	Meta gem containing Shoulda Context and Shoulda Matchers Shoulda contains two other gems: Should Context and Shoulda Matchers. Should Context allows better naming and grouping of your tests. Shoulda Matchers provides a set of "matchers", i.e. methods that allow you to write much more concise assertions.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	No
Client-side Allows testing code execution on the client, such as a web browser	Yes Front-end behaviour is tested. With specflow specifications of the expected behaviours are made and specflow tests against this	N/A
Server-side Allows testing the bahovior of a server-side code	Yes Back-end behaviour is tested. Specifications of the expected behaviours are made and specflow tests against them	N/A
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes BeforeTestRun and AfterTestRun are executed once for each thread which is a limitation of the current architecture.	N/A
Group fixtures Allows defining a fixed, specific states of data for a group of tests (group-fixtures). This ensures specific environment for a given group of tests.	N/A	N/A
Generators Supports data generators for tests. Data generators generate input data for test. The test is then run for each input data produced in this way.	Yes SpecFlow contains a generator component. The SpecFlow IDE integration tries to locate the generator component in your project structure, in order to use the generator version matching the SpecFlow runtime in your project	N/A
Licence Licence type governing the use and redistribution of the software	BSD license	MIT License
Mocks Mocks are objects that simulate the behavior of real objects. Using mocks allows testing some part of the code in isolation (with other parts mocked when needed)	Yes Specflow intergrates well with mock to give it excellent mocking capabilities	N/A
Grouping Allows organizing tests in groups	Yes You can create test suites with specflow	Yes
Other Other useful information about the testing framework		Shoulda Context is compatible with Minitest and Test::Unit. Shoulda Matchers is compatible with RSpec and Minitest.