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

Turnip

https://github.com/jnicklas/turnip

Testify

https://github.com/stretchr/testify
Programming language

Ruby

Go

Category

Acceptance Testing, Integration Testing

Unit 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 set of golang packages that has many tools for testing Go code

Testify is a Go testing framework that has some great features like easier assertions, Test suite Interfaces, and Mocks
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

Yes, since it is also easily hooked to 'testing' package it is used to test front-end components
Server-side
Allows testing the bahovior of a server-side code

Yes

Turnip is used to test server-side behaviour and components

Yes

Yes it can also be used to test back-end components and functionality
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

No

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.

No

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.

No

N/A

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

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

Yes

Its 'mock' package has a mechanism for easily writing mock objects that are used in place of real objects
Grouping
Allows organizing tests in groups

Yes

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

Yes

Using the 'suite' package developers can build a test suite as a struct build teardown and setup methods as well as testing methods on the struct then run them with 'go test'
Other
Other useful information about the testing framework