Changes between Version 3 and Version 4 of oss/lolunit
- Timestamp:
- Sep 8, 2011, 8:47:08 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
oss/lolunit
v3 v4 1 1 = The LolUnit test framework = 2 2 3 LolUnit came from a need tofor a lightweight unit test system. Our previous framework of choice was [http://cppunit.sourceforge.net/doc/lastest/cppunit_cookbook.html CppUnit], but we stopped using it because there was no practical way to pre-build it for all the platforms we support (Windows with various compilers, Android, iOS, PS3…). Also, we had to keep as many precompiled binaries as there were versions of libstdc++, multiplied by the number of possible configurations (debug, release…). This was very difficult to maintain.3 LolUnit came from a need for a lightweight unit test system. Our previous framework of choice was [http://cppunit.sourceforge.net/doc/lastest/cppunit_cookbook.html CppUnit], but we stopped using it because there was no practical way to pre-build it for all the platforms we support (Windows with various compilers, Android, iOS, PS3…). Also, we had to keep as many precompiled binaries as there were versions of libstdc++, multiplied by the number of possible configurations (debug, release…). This was very difficult to maintain. 4 4 5 5 Though we use it in production code, LolUnit’s overall quality should not be considered higher than '''proof of concept''' for now. … … 11 11 * can be built with `-fno-exceptions -fno-rtti` 12 12 * formats its standard text output in the same way as CppUnit 13 14 Features will be added depending on internal use but also user requests. 13 15 14 16 == Download == … … 62 64 }}} 63 65 64 One major problem I have with this system is that `Addition` needs to be declared and defined at two different places. Similarly, `Test1` needs to be declared, then given as an argument to `CPPUNIT_TEST_SUITE`, and finally as an argument to `CPPUNIT_TEST_SUITE_REGISTRATION`. 66 One major problem I have with this system is that `Addition` needs to be declared and defined at two different places. Similarly, `Test1` needs to be declared, then given as an argument to `CPPUNIT_TEST_SUITE`, and finally as an argument to `CPPUNIT_TEST_SUITE_REGISTRATION`. There is no reason the user should have to duplicate this information. 65 67 66 68 This is the LolUnit equivalent: … … 93 95 } 94 96 }}} 97 98 We believe it is a lot simpler.