Blueprint changed by rejon: Whiteboard changed: - Initially, we can integrate PHPUnit: http://www.phpunit.de/ --Brylie - Oxley - - https://code.launchpad.net/~brylie/aikiframework/doctrine is the code - that is there - - I think we need to make sure that: - - A.) phpunit is pulled from their repositories - - B.) figure out good way to integrate into a test mode, that we can - easily shutoff so not executing during runtime. - - C.) figure out how to use it to test aiki's core and extensions in a - modular way - - ### - - Great, here are the next steps: - - * we should merge this request into mainline, - * then we need to develop a plan for testing each class we have, and need a folder and naming convention for these test - * we then need to hook these test into the build system so we get automated tests - * add code to autobuild system and if it errors out, send emails to the developer lists - - ---- - Added optional PHPUnit (to enable: --enable-tests) feature which is disabled by default: PHPUnit testing support requires PHPUnit to be installed on the system running the tests. Create your tests under the aikiframework/tests directory which should reflect what exists in the aikiframework/src directory. You can see aikiframework/tests/system/libraries/LogTest.php for an example. Also, there is online documentation on using PHPUnit here: http://www.phpunit.de/manual/current/en/writing-tests-for-phpunit.html. Here's a quick example of running the tests: - ./autogen.sh && cd build && ../configure --enable-tests && make check - - -Steven + Ok, PHPUnit is installed and everything ready. We just need tests for + each class.
-- Add Unit Testing to Aiki Core and Extensions https://blueprints.launchpad.net/aikiframework/+spec/unit-testing _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
