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

	SpecFlow https://specflow.org/	Cedar https://github.com/cedarbdd/cedar
Programming language	.NET	Swift
Category	Acceptance Testing	Unit 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.	Cedar is a BDD-style testing for swift using Objective-C Cedar is a BDD-style Objective-C/Swift testing framework that has an expressive matcher DSL and convenient test doubles (mocks). It provides better organizational facilities than the tools provided by XCTest/OCUnit In environments where C++ is available, it provides powerful built-in matchers, test doubles and fakes
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes Cedar is an xUnit style framework
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	Yes You can test front-end components and behaviour with Cedar, its language is biased towards describing the behavior of your objects.
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	Yes You can test back-end components with a bias towards their expected behaviour. Cedar specs also allow you to nest contexts so that it is easier to understand how your object behaves in different scenarios
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.	Yes Cedar has beforeEach and afterEach class methods which Cedar will look for on every class it loads. You can add these onto any class you compile into your specs and Cedar will run them
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	Yes Cedar contains inbuilt mock/test double functionality
Grouping Allows organizing tests in groups	Yes You can create test suites with specflow	Yes Cedar supports shared example groups. You can declare them in one of two ways: either inline with your spec declarations, or separately.
Other Other useful information about the testing framework