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

Test::Unit

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

csUnit

http://www.csunit.org/
Programming language

Ruby

.NET

Category

Unit Testing, Intergration Testing

Unit 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

csUnit is an open source unit testing tool for the .NET Framework

csUnit is designed to work with any .NET compliant language. It has specifically been tested with C#, Visual Basic .NET, Managed C++, and J#
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

Yes

csUnit is an xUnit type testing framework and follows xUnit concepts
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

You can unit test front-end components of your applications with csUnit
Server-side
Allows testing the bahovior of a server-side code

Yes

Yes

You can unit test back-end components of your applications with csUnit
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

Yes

csUnit has fixture methods such as setup and teardown methods
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

Yes

Group fixtures are available in csUnit
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

LGPLv2.1, Ruby Licence

zlib 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

You can write your own mock objects manually
Grouping
Allows organizing tests in groups

No

Yes

It contains recipes for combining several test assemblies into one test suite
Other
Other useful information about the testing framework