Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Released 24 July 2018
Fix for bug when no filename with jUnit output format
Recursively search directories below test suite home directory for *_ut. pro and *_uts.pro files
Fixed for bug in mguttestsuite_define::addTestingFolder that did not add absolute paths correctly
Add superclasses of test classes recursively
Released 18 November 2013
Passing keywords to MGUNIT down to MGutTestCase subclasses.
Reporting coverage of tested routines.
Adding Cobertura output option.
Allowing up to 8 arguments for substituting into ASSERT error message.
Released 18 May 2015
Checks for updates when using the VERSION keyword.
Fix for test cases with no valid tests.
Added RUNNERS keyword and allowed FILENAMES to accept a string array so that output can be send to multiple outputs
Released 12 February 2013
- Added optional
OUTPUTkeyword to tests which, if present and set during the the test, is echoed to the output.
- Added utilities to help test GUI applications.
- Updated "Using mgunit" documentation.
error_is_skip.probatch file with optional variable
MGUNIT_SKIP_MSGwhich can be set prior to including
error_is_skip.proto a message that will be used if an error causes the skip.
- Updated look for HTML output.
Released 7 July 2011
FAILURES_ONLYkeyword to display only failed tests.
- Simplified and improved user-level API documentation.
VERSIONkeyword to report mgunit version.
Released 22 February 2010
- Added an extra argument to
ASSERTwhich can be inserted into the message via C-style format codes.
- Added XML and JUnit output formats (and corresponding XML and JUNIT keywords to
MGUNITto turn them on).
- Added ability for a test to determine if it should count in the final results tally, i.e., if it is "skipped". Use the
ASSERTto skip a test instead of failing it if the condition is not met.
- Fixed memory leak.
Released 27 April 2009
- Framework for creating pass/fail unit tests with as little overhead and boilerplate text as possible. Simply create a new class which inherits from MGutTestCase, no init or cleanup methods are necessary unless the test requires some setup before it is run. Any function method whose name begins with "test" will be executed: it is considered a pass if it returns 1, failing if it returns 0 or crashes.
- Suites can automatically gather together many test case classes together if the tests follow a simple naming convention: end the test case classname in "_ut". In this way, mgunit can run individual test cases or test suites aggregating test cases at various levels.
- Several test runners for outputting test results to various formats are available; output can be sent to stdout, log files, or html files. In addition, there is a GUI test runner that will show results and re-run tests with the push of a button (also recompiling tests before running them).
- If there is common setup required for each test method in a test case, a setup method can be written. This method will be called before each test method (the teardown method will be called after each test method).
- Contains IDL Workbench templates for making it even faster to create new test cases/suites.
- Keywords to
MGUNITto retrieve the number of passing and failing tests.
- Color output to the terminal window when possible.
- Shell script to run mgunit from the UNIX command line.