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

	Intern https://github.com/theintern/intern	Cedar https://github.com/cedarbdd/cedar
Programming language	JavaScript	Swift
Category	Unit Testing, Functional Testing	Unit Testing
General info	Intern is minimal test system for JavaScript designed to write and run consistent. Intern is a complete test system for JavaScript designed to help you write and run consistent, high-quality test cases for your JavaScript libraries and applications. Using Intern we can write tests in JavaScript and TypeScript using any style like TDD, and BDD. Intern can run unit tests in most browsers that support ECMAScript	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
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes Cedar is an xUnit style framework
Client-side Allows testing code execution on the client, such as a web browser	Yes Intern is a complete test system for JavaScript It Runs in the browser and can test any front-end component and functionality	Yes You can test front-end components and behaviour with Cedar, its language is biased towards describing the behavior of your objects.
Server-side Allows testing the bahovior of a server-side code	Yes Since it is a complete testing system that can test any type of JavaScript code, it can test server-side behaviour and components as well	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
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 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
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	N/A
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
Licence Licence type governing the use and redistribution of the software	FreeBSD 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)	Intern uses the Dojo Toolkit’s AMD loader. To mock, you should be able to just use the standard AMD 'map' feature, else you can use third party libraries like sinon.js	Yes Cedar contains inbuilt mock/test double functionality
Grouping Allows organizing tests in groups	Yes You can group tests into Suites which may be specified as file paths or using glob expressions, there is typically one top-level suite per module.	Yes Cedar supports shared example groups. You can declare them in one of two ways: either inline with your spec declarations, or separately.
Other Other useful information about the testing framework