Concordion vs Sleipnir comparison of testing frameworks
What are the differences between Concordion and Sleipnir?

	Concordion https://concordion.org/	Sleipnir https://github.com/railsware/Sleipnir
Programming language	Java	Swift
Category		Unit Testing, Acceptance Testing
General info	Concordion is a tool used to write and manage automated acceptance tests in Java based projects Concordion specifications are written in Markdown, HTML or Excel and then instrumented with special links, attributes or comments respectively. When the corresponding test fixture class is run, Concordion interprets the instrumentation to execute the test. Concordion lets you write them in normal language using paragraphs, tables and proper punctuation. This makes specification more natural to read and write, and helps everyone to understand and agree about what a feature is supposed to do.	Sleipnir is a BDD-style framework for Swift Sleipnir is a pure Swift BDD testing framework inspired by cedar, that is not dependent on NSObject, and does not use XCTest. Sleipnir has nice command line output and support for custom test reporters and other features, like seeded random tests invocation, focused and excluded examples/groups
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	N/A
Client-side Allows testing code execution on the client, such as a web browser	Yes You can specify tests for front-end components and functionality with concordion	Yes You can test front-end behaviour by defining specifications for classes, objects and functions
Server-side Allows testing the bahovior of a server-side code	Yes You can test server-side components and functionality with concordion.	Yes You can test back-end behaviour by defining specifications for classes, objects and functions in the back-end
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes Concordion contains fixtures which correspond to a specific instrumentation within the code. That is when specifications are written they are instrumented with special links, attributes or comments which are then run with their corresponding fixtures	Yes Fixtures are available by using beforeEach{ } and afterEach{ } to setup the test parameters
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.	Yes One can group fixtures in concordion	Yes Group fixtures are available through the beforeAll{} and afterAll{} blocks to setup group fixtures
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.	N/A	N/A
Licence Licence type governing the use and redistribution of the software	Apache License 2.0	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 By use of third party libraries like mockito	Yes Yes, developers can create mock objects with sleipnir using a third party library like Cuckoo.
Grouping Allows organizing tests in groups	Yes One can group tests into suites	Yes You can declare example groups with Slepnir
Other Other useful information about the testing framework