Test::Unit vs Turnip comparison of testing frameworks
What are the differences between Test::Unit and Turnip?

	Test::Unit https://test-unit.github.io/	Turnip https://github.com/jnicklas/turnip
Programming language	Ruby	Ruby
Category	Unit Testing, Intergration Testing	Acceptance Testing, Integration Testing
General info	Test::Unit is a unit testing framework for Ruby Test::Unit is an implementation of the xUnit testing framework for ruby which is used for Unit Testing. However Test::Unit has been left in the standard library to support legacy test suites therefore if you are writing new test code use Minitest instead of Test::Unit	Turnip is a Gherkin extension for RSpec Turnip is an open source Ruby gem that provides a platform for acceptance tests.It combines Gherkin, a language defined by the Cucumber Behavior-Driven Development (BDD) tool to express requirements, and RSpec, an open source BDD tool for Ruby developers.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	Yes test-unit is a xUnit family unit testing framework for Ruby	No
Client-side Allows testing code execution on the client, such as a web browser	It could have tested some front-end components but its now legacy hence wouldn't work with the many new front-end components	Yes Turnip can perform end-to-end tests therefore test front-end components and functionality
Server-side Allows testing the bahovior of a server-side code	Yes	Yes Turnip is used to test server-side behaviour and components
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes Fixture methods are available through its ClassMethods Module	No
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 fixture methods are supported	No
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.	No	No
Licence Licence type governing the use and redistribution of the software	LGPLv2.1, Ruby Licence	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)	No	Yes By intergrating with RSpec turnip has access to the rspec-mocks gem
Grouping Allows organizing tests in groups	No	Yes Turnip Integrates directly into your RSpec test suite which allows declaring example groups and contexts.
Other Other useful information about the testing framework