Knapsack Pro

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

Test::Unit

https://test-unit.github.io/

Hound

https://github.com/HashNuke/hound
Programming language

Ruby

Elixir

Category

Unit Testing, Intergration Testing

Browser Automation, Intergration 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

Elixir library for browser automation and writing intergration tests

It is a front-end testing library that has support for: Selenium (Firefox, Chrome), ChromeDriver and PhantomJs. Also supports JavaScript applications and retries tests a few times before reporting errors
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

Allows for browser Automation and writing of end-to-end tests for web apps, supports Selenium WebDriver, ChromeDriver, and PhantomJS - GhostDriver
Server-side
Allows testing the bahovior of a server-side code

Yes

N/A

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

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.

Yes

Group fixture methods are supported

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

Yes

Not inbuilt but by use of a third party library like ExopData
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

Yes, through the use of a third party library like Mockery
Grouping
Allows organizing tests in groups

No

N/A

Other
Other useful information about the testing framework