Migrating from 0.1.4 to 0.2.0
Migrating Test Cases
The last component is the test system. This has been overhauled to make it easier to work with and to try and provide a level of abstraction from the test library. The test system has been moved to a dedicated /test folder in libraries and several additional classes have been added.
All tests should now inherit from testCaseScorpio. This abstract class provides some basic utility methods including a skip() for SimpleTest is production mode is set. This prevents test cases from running on a production system.
The additional classes include objects for locating test cases and returning object sets and a HTML reporter - test cases can now be run via the admin system or a web server with relative ease.
These changes along with a much larger simpletest autoload file make it far more reliable to run tests and allows for the test case management tools to be used by both the CLI and Web systems.
The changes required are relatively minor, simply change the inheritance to testCaseScorpio instead of the previous MyUnitTestCase. This class still exists, but it will be removed in later releases of the Scorpio framework.
In summary...
That covers the major changes that are likely to cause issues. CLI Applications are the major issue. Both test cases and MVC require very little in the way of modification, in fact in some cases it is more of just updating config files than actual code changes.
Of course any updates should be thoroughly tested in a development and then a staging environment before being placed into production.
This release of Scorpio is a big leap forward both in quality and stability, moving forward this will continue to be improved.
Posted by: Dave Redfern (Writer), in Documentation on 24 Apr 2009 @ 02:27
Contents:
This
work is licenced under a
Creative Commons Licence.