I really really hate the QTestLib output on my Mac. It's a very ugly xwindows console result.
More...
|
| TestCase () |
| Constructs the testcase. More...
|
|
virtual TestEngine * | engine () |
| This method returns the current engine. More...
|
|
virtual void | setEngine (TestEngine *engine) |
|
virtual OutputHandler * | out () |
| this method returns the outputhandler More...
|
|
virtual void | testTrueImpl (bool condition, const char *statement, const QString &description, const char *file, int line) |
| The test true implementation. More...
|
|
virtual void | testEqualImpl (bool result, const QString &actual, const QString &expected, const char *actualStatement, const char *expectedStatement, const QString &description, const char *file, int line) |
| The test equal implementation. More...
|
|
virtual void | testSkipImpl (const QString &description, const char *file, int line) |
| Implements the skip test operation. More...
|
|
virtual TestCase * | currentTest () |
| this method returns the current testcase More...
|
|
virtual QString | currentMethodName () |
|
virtual void | giveTestResultToEngine (TestResult *result) |
| Gives the testresult to the engine. More...
|
|
I really really hate the QTestLib output on my Mac. It's a very ugly xwindows console result.
This extemely simple testing support class makes it possible for met to output the test results to a WebKit window. Where I can added clickable divs etc. to show test result details
The basic conventions for these tests are the sames as those of QTest. The main difference is the usage of exta output/compare info output messsages A simple unit test. Every private slot is called for a test