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

Nose

https://nose.readthedocs.io/en/latest/

Sleipnir

https://github.com/railsware/Sleipnir
Programming language

Python

Swift

Category

Unit Testing, unittest Extensions

Unit Testing, Acceptance Testing

General info

Nose is a Python unit test framework

This is a Python unit test framework that intergrates well with doctests, unnittests, and 'no-boilerplate tests', that is tests written from scratch without a specific boilerplate.

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

nose is a unit testing tool which is very similar to unittest. It is basically unittest with extensions therefore just like unittest is can test front-end components and behaviour

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

Nose can test back-end components and functionality as small units. One can write tests for each function that provides back-end functionality

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

nose supports fixtures at the package, module, class, and test case levels, so that initialization which can be expensive is done as infrequently as possible.

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

Group fixtures are allowed with nose, where a multitest state can be defined.

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.

Through use of third party libraries like test-generator and from the 'unittest.TestCase' library

N/A

Licence
Licence type governing the use and redistribution of the software

GNU Library or Lesser General Public License (LGPL) (GNU LGPL)

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

The nose library extends the built-in Python unittest module therefore has access to unittest.mock

Yes

Yes, developers can create mock objects with sleipnir using a third party library like Cuckoo.
Grouping
Allows organizing tests in groups

Yes

With nose it collects tests automatically and there’s no need to manually collect test cases into test suites.

Yes

You can declare example groups with Slepnir
Other
Other useful information about the testing framework