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

	Tacinga https://github.com/OwenMcDonnell/tacinga	Intern https://github.com/theintern/intern
Programming language	Java	JavaScript
Category	Unit Testing	Unit Testing, Functional Testing
General info	Tacinga is an Object-Oriented Java unit testing library	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
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.		No
Client-side Allows testing code execution on the client, such as a web browser	Yes You can unit test front-end components with tacinga	Yes Intern is a complete test system for JavaScript It Runs in the browser and can test any front-end component and functionality
Server-side Allows testing the bahovior of a server-side code	Yes You can test back-end components and functionality.with tacinga	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
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	N/A	N/A
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	MIT License (for non-commercial use); Commercial License (for commercial use)	FreeBSD 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)	You can use external libraries like mockit	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
Grouping Allows organizing tests in groups	N/A	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.
Other Other useful information about the testing framework