6 projects tagged "Unit test"
HyperSQL is like the doxygen program with Javadoc added, but for SQL. It hypermaps SQL views, packages, procedures, and functions to HTML source code listings, and it shows all the code locations where these are used. You can use JavaDoc-style comments for documentation and even embed UnitTests with them.
crpcut is the Compartmented Robust Posix C++ Unit Test system. crpcut (pronounced "Crap Cut") runs all test cases in their own process and their own working directory, which makes it perfectly normal to test that asserts do trap, and the test suite continues even in the event of an unexpected SIGSEGV. By using the C++11 features long available in GCC, the tests are extremely easy to write.
Coco is another code coverage utility for Ruby 1.9. One uses it from rspec or unit/test with a simple "require 'coco'". It displays the names of files that are covered less than 90% on the console. It builds a simple HTML report only for files covered less than 90%. It reports sources that have no tests. It is UTF-8 compliant. It is configurable via a simple YAML file. It has colorized console output.
ytest is a PHPUnit extension, based on the PHP extension "runkit", that allows you to replace static, private, and global functions with fakes, stubs, or mocks. This eases the automated testing of PHP applications that weren't written in a TDD fashion (i.e. test-first). It can also be helpful on projects where many methods are kept private, or projects that don't use OOP so much. ytest has already been used to "test after" (as opposed to "test first") some real-life commercial projects, and has proven useful. It needs PHP >= 5.2.
STK/Unit is a pure SQL testing framework for MariaDB and MySQL. Users can create Base Tests (Stored Procedures) which are part of Test Cases (databases) and, optionally, Test Suites (other Stored Procedures). Output is stored in internal tables. You can convert it to a human-readable string, valid HTML, or query some convenient views which group results. It can be used to test any SQL structure (tables, views, triggers, stored routines), as well as server upgrades or configuration changes.