|
Post by Martin Nielsen on Oct 13, 2011 13:05:10 GMT -5
Question: Why aren't there any GUI testrunner where you can select test to run and with indicators that turns green or red as each test executes ?
Answer: TestApe is created to be an integrated part of the build process. The TestApe tests are ment to be designed and maintained by the software developer and executed by the build process. A GUI test runner is not needed to achive this.
|
|
|
Post by Martin Nielsen on Sept 30, 2011 9:52:51 GMT -5
April 2nd 2010, Release 791
•Full mock support for function and library calls. In this release all functions can be mocked. That includes functions that are internal to the unit or functions called in C library. Every test can supply its own individual mock. This will be in scope during that test only. Test suites can supply mocks that will remain in scope for the entire testsuite. The mock can validate the parameters and/or call the function it mocks.
•Automatic default mocks for unresolved externals. Mocking functions explicitly is possibility. As default the instrumenter will supply default mocks for all unresolved externals. Units with extensive use of external interfaces can have a test running immediately - no need to write dummy stub functions.
•New macros ALLOW, ALLOW_SIMULATE and ALLOW_VALIDATE implemented. These new macros allows you to pass control to a mock function. The scope of these macros defines when a mock is called and what happens after. When a mocked function is called, the framework can either return a specific value to the unit each time or invoke the supplied mock. The mock can choose to give back control to the mocked function. This is powerful as generic validation of parameters to functions - for example the format string and parameters of printf.
•Other features ◦Option to limit amount of tests from commandline. e.g. --> testexe 5-7 will execute testcase 5,6 and 7. testexe e1 will execute first testcase with an error. ◦Examples from documentation added to installation. ◦Improved debug support with testape_error_handler. ◦All functions (also C library functions used by the framework) can now be mocked. ◦Instrumenter will notify when a new release becomes available. ◦Mocked function and its current replacement shown in log. ◦New instrumenter options -o and -v to help troubleshooting. ◦Testcode can be written to produce consistent results when the amount of object files in the unit are changed. If object files are removed, default mocks are automatically supplied. If object files are added, the new functions are automatically mocked in existing tests.
•Fixed bugs ◦Bugfix: gcc -m32 is now passed correctly. ◦Bugfix: Support new versions of cl/link in Microsoft Visual Studio C++ 2008. ◦Bugfix: Support new versions of gcc in CygWin and Linux. ◦Bugfix: Mock return values could in rare cases become corrupted. ◦Bugfix: Added error message when instrumenter could not create temporary files. ◦Bugfix: Instrumenter allows gcc with -ltestape, so testape.a will be loaded from lib path. ◦Bugfix: testape_cache .ini style file handling improved. ◦Bugfix: Mocked static functions will break instrumentation.
|
|
|
Post by Martin Nielsen on Sept 28, 2011 11:08:35 GMT -5
TestApe can now be used with MinGW GCC on windows. Also supported in this beta are floating point types in validations or when mocking functions
A new possibility is to declare tests with arguments - these can be passed between tests and to testmain from command line.
The release is tested with GCC in Linux (debian lenny) and in Windows XP, Vista with GCC/Cygwin, GCC/MinGW, Visual Studio Express 2009 and Visual Studio Enterprise 2010.
More detailed information, documentation and release note can be found in the beta section on the download page (http://testape.com/free_unit_testing_tool.html#beta)
|
|
|
Post by Martin Nielsen on Sept 28, 2011 10:49:28 GMT -5
TestApe forum is now hosted on Proboards. Support questions can be posted here or send directly on email. Due to huge amount of spam, and my lack of time to fight it, the TestApe forum have not been in operation for the last year.
I will now try this approach instead in order to handle support issues. The new forum will be operational within the next weeks. You're of course still welcome to send questions on email.
|
|