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

Espec

https://github.com/antonmi/espec

Nose

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

Elixir

Python

Category

Unit Testing

Unit Testing, unittest Extensions

General info

BDD driven testing framework for Elixir

It is a testing framework written from scratch which is inspired by RSpec and the main idea is to close to its perfect DSL (Domain Specific Language)

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.
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 components can be tested; there is also espec_phoenix for the Phoenix web framework

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
Server-side
Allows testing the bahovior of a server-side code

Yes

databases and server behaviour can be tested using Espec

Yes

Nose can test back-end components and functionality as small units. One can write tests for each function that provides back-end functionality
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

N/A

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.
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

Yes

Group fixtures are allowed with nose, where a multitest state can be defined.
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

Through use of third party libraries like test-generator and from the 'unittest.TestCase' library
Licence
Licence type governing the use and redistribution of the software

MIT License

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

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

It has a Built-in mocking functionality on top of Erlang 'meck' library

Yes

The nose library extends the built-in Python unittest module therefore has access to unittest.mock
Grouping
Allows organizing tests in groups

Yes

By use of context blocksand tags functions

Yes

With nose it collects tests automatically and there’s no need to manually collect test cases into test suites.
Other
Other useful information about the testing framework