Turnip vs BeanTest comparison of testing frameworks
What are the differences between Turnip and BeanTest?

Turnip

https://github.com/jnicklas/turnip

BeanTest

https://github.com/NovatecConsulting/BeanTest
Programming language

Ruby

Java

Category

Acceptance Testing, Integration Testing

Unit Testing, Intergration Testing

General info

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.

A testing solution for Java EE applications

BeanTest is a testing solution for Java EE Applications which combines the speed of unit tests with almost the coverage of integration tests with minimal configuration and with standard and well known frameworks like JPA, CDI, Mockito and Junit
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

Turnip can perform end-to-end tests therefore test front-end components and functionality

Yes

You can test front-end components of your EE application
Server-side
Allows testing the bahovior of a server-side code

Yes

Turnip is used to test server-side behaviour and components

Yes

BeanTest is used to test business logic or the back-end that is information exchange between the database and the UI
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

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.

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

Licence
Licence type governing the use and redistribution of the software

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

By intergrating with RSpec turnip has access to the rspec-mocks gem

Yes

You are able to provide your own Mocks in BeanTest to test external dependencies
Grouping
Allows organizing tests in groups

Yes

Turnip Integrates directly into your RSpec test suite which allows declaring example groups and contexts.

Other
Other useful information about the testing framework