| 1 | ------------- |
|---|
| 2 | Release notes |
|---|
| 3 | ------------- |
|---|
| 4 | |
|---|
| 5 | |
|---|
| 6 | mgunit 1.3 |
|---|
| 7 | ---------- |
|---|
| 8 | |
|---|
| 9 | * Added utilities to help test GUI applications. |
|---|
| 10 | |
|---|
| 11 | * Updated "Using mgunit" documentation. |
|---|
| 12 | |
|---|
| 13 | |
|---|
| 14 | mgunit 1.2 |
|---|
| 15 | ---------- |
|---|
| 16 | Released 7 July 2011 |
|---|
| 17 | |
|---|
| 18 | * Added FAILURES_ONLY keyword to display only failed tests. |
|---|
| 19 | |
|---|
| 20 | * Simplified and improved user-level API documentation. |
|---|
| 21 | |
|---|
| 22 | * Added VERSION keyword to report mgunit version. |
|---|
| 23 | |
|---|
| 24 | |
|---|
| 25 | mgunit 1.1 |
|---|
| 26 | ---------- |
|---|
| 27 | Released 22 February 2010 |
|---|
| 28 | |
|---|
| 29 | * Added an extra argument to ASSERT which can be inserted into the |
|---|
| 30 | message via C-style format codes. |
|---|
| 31 | |
|---|
| 32 | * Added XML and JUnit output formats (and corresponding XML and JUNIT keywords |
|---|
| 33 | to MGUNIT to turn them on). |
|---|
| 34 | |
|---|
| 35 | * Added ability for a test to determine if it should count in the |
|---|
| 36 | final results tally, i.e., if it is "skipped". Use the SKIP keyword |
|---|
| 37 | of ASSERT to skip a test instead of failing it if the condition is |
|---|
| 38 | not met. |
|---|
| 39 | |
|---|
| 40 | * Fixed memory leak. |
|---|
| 41 | |
|---|
| 42 | |
|---|
| 43 | mgunit 1.0 |
|---|
| 44 | ---------- |
|---|
| 45 | Released 27 April 2009 |
|---|
| 46 | |
|---|
| 47 | * Framework for creating pass/fail unit tests with as little overhead and |
|---|
| 48 | boilerplate text as possible. Simply create a new class which inherits from |
|---|
| 49 | MGutTestCase, no init or cleanup methods are necessary unless the test |
|---|
| 50 | requires some setup before it is run. Any function method whose name begins |
|---|
| 51 | with "test" will be executed: it is considered a pass if it returns 1, |
|---|
| 52 | failing if it returns 0 or crashes. |
|---|
| 53 | |
|---|
| 54 | * Suites can automatically gather together many test case classes together if |
|---|
| 55 | the tests follow a simple naming convention: end the test case classname in |
|---|
| 56 | "_ut". In this way, mgunit can run individual test cases or test suites |
|---|
| 57 | aggregating test cases at various levels. |
|---|
| 58 | |
|---|
| 59 | * Several test runners for outputting test results to various formats are |
|---|
| 60 | available; output can be sent to stdout, log files, or html files. In |
|---|
| 61 | addition, there is a GUI test runner that will show results and re-run tests |
|---|
| 62 | with the push of a button (also recompiling tests before running them). |
|---|
| 63 | |
|---|
| 64 | * If there is common setup required for each test method in a test case, a |
|---|
| 65 | setup method can be written. This method will be called before each test |
|---|
| 66 | method (the teardown method will be called after each test method). |
|---|
| 67 | |
|---|
| 68 | * Contains IDL Workbench templates for making it even faster to create new |
|---|
| 69 | test cases/suites. |
|---|
| 70 | |
|---|
| 71 | * Keywords to MGUNIT to retrieve the number of passing and failing tests. |
|---|
| 72 | |
|---|
| 73 | * Color output to the terminal window when possible. |
|---|
| 74 | |
|---|
| 75 | * Shell script to run mgunit from the UNIX command line. |
|---|
