Cedar vs TwistedTrial comparison of testing frameworks
What are the differences between Cedar and TwistedTrial?

	Cedar https://github.com/cedarbdd/cedar	TwistedTrial https://twistedmatrix.com/trac/wiki/TwistedTrial
Programming language	Swift	Python
Category	Unit Testing	Unit Testing, unittest Extensions
General info	Cedar is a BDD-style testing for swift using Objective-C Cedar is a BDD-style Objective-C/Swift testing framework that has an expressive matcher DSL and convenient test doubles (mocks). It provides better organizational facilities than the tools provided by XCTest/OCUnit In environments where C++ is available, it provides powerful built-in matchers, test doubles and fakes	Trial is a unit testing framework for Python built by Twisted Matrix labs Trial is composed of two parts: First is a command-line test runner, which can be run on plain Python unit tests and can do automated unit-test discovery across files, modules, or even arbitrarily nested packages. Second is a test library, derived from Python's 'unittest.TestCase'
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	Yes Cedar is an xUnit style framework	No
Client-side Allows testing code execution on the client, such as a web browser	Yes You can test front-end components and behaviour with Cedar, its language is biased towards describing the behavior of your objects.	Yes Front-end components can be tested for example adding a web front-end using simple twisted.web.resource.Resource objects
Server-side Allows testing the bahovior of a server-side code	Yes You can test back-end components with a bias towards their expected behaviour. Cedar specs also allow you to nest contexts so that it is easier to understand how your object behaves in different scenarios	Yes Server-side behaviour can be tested with Trial, it has various functions for this in the twisted.web.Resource package
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes Cedar has beforeEach and afterEach class methods which Cedar will look for on every class it loads. You can add these onto any class you compile into your specs and Cedar will run them	Yes Trial supports various fixture methods such as 'setUp()' and 'tearDown' functions fixture for normal semantics of setup, and teardown
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 Methods like 'setUp()' allow for creation of 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	Through use of third party libraries like test-generator.
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 Cedar contains inbuilt mock/test double functionality	Yes Trial can access the mock library inbuilt in python for mocking purposes
Grouping Allows organizing tests in groups	Yes Cedar supports shared example groups. You can declare them in one of two ways: either inline with your spec declarations, or separately.	Yes Trial allows tests to be grouped into test packages
Other Other useful information about the testing framework