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

	Nose https://nose.readthedocs.io/en/latest/	Kiwi https://github.com/kiwi-bdd/Kiwi
Programming language	Python	Swift
Category	Unit Testing, unittest Extensions	Unit 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.	Kiwi is a Behavior Driven Development library for iOS development The goal behind Kiwi is to provide a BDD library that is simple to setup and use, and create tests that are more readable than what is possible with the bundled test framework.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes Kiwi is an xUnit style framework
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 components with kiwi
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 components with kiwi
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.
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 kiwi has a beforeEach(aBlock) which is run before every 'it' block in all enclosed contexts. Code that sets up the particular context should go here and afterEach(aBlock) which is run after every it block in all enclosed contexts
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	Yes through the beforeAll(aBlock) and afterAll(aBlock) functions.
Licence Licence type governing the use and redistribution of the software	GNU Library or Lesser General Public License (LGPL) (GNU LGPL)	Proprietary, Open source
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 Kiwi has inbuilt support for stubs and mocks,including null mocks, class mocks, protocol mocks
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 Kiwi uses the block syntax in iOS to define groups of assertions and share setup state between collections of tests
Other Other useful information about the testing framework