Knapsack Pro

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

Sleipnir

https://github.com/railsware/Sleipnir

Behat

https://docs.behat.org/en/latest/
Programming language

Swift

PHP

Category

Unit Testing, Acceptance Testing

Functional/Acceptance Testing

General info

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

Behat is an open source Behavior-Driven Development framework for PHP.

Behat uses the StoryBDD subtype of behaviour-driven development (the other subtype is SpecBDD); This means the tests we write with Behat look rather like stories than code. It is inspired by Ruby's Cucumber
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

N/A

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

You can test front-end behaviour by defining specifications for classes, objects and functions

Yes

To enable Behat to test a website, you need to add Mink and a browser emulator (selenium maybe, though slow) to the mix. Mink methods are the connector between Behat and an extensive list of available drivers, and they provide a consistent testing API.
Server-side
Allows testing the bahovior of a server-side code

Yes

You can test back-end behaviour by defining specifications for classes, objects and functions in the back-end

Yes

Behat can be used for Data Integrity Testing to verify that database operations are functioning properly
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

Yes

Fixtures are available by using beforeEach{ } and afterEach{ } to setup the test parameters

Yes

One can use the 'Doctrinefixturesbundle' to create the required fixture loaders and load them in our Behat scenarios when required, using the 'BeforeScenario' hook.
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

Group fixtures are available through the beforeAll{} and afterAll{} blocks to setup group fixtures

Yes

Behat allows for 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

By use of third party libraries like moodle-behat-generators
Licence
Licence type governing the use and redistribution of the software

MIT 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

Yes, developers can create mock objects with sleipnir using a third party library like Cuckoo.

By using third party libraries like Mock and Prophecy
Grouping
Allows organizing tests in groups

Yes

You can declare example groups with Slepnir

Yes

You can use tags to group features and scenarios together, independent of your file and directory structure
Other
Other useful information about the testing framework