Two releases in quick succession? Well, yes. Both of these releases are to address previously missed issues with the test suite and some test cases that were failing. In particular the MVC and generator tests had not been updated to reflect changes in Smarty 3. An additional test has also been added to cover mvcSiteBuilder.
There are still outstanding issues with testScaffold owing to a possible bug in Smarty 3. This is being investigated, but currently it does not appear possible to make variable method calls (things like $object->$method()) which the scaffold system relies on.
A minor change has been made to system::init(). A path can now be passed into it as a parameter to allow the system base path to be set explicitly, rather than being calculated based on the expected folder structure. This is part of a future update that will allow the Scorpio core files to be packaged into a single file to aid performance. Some current testing and non-repeatable profiling / guess-timates have seen execution times drop to as low as 40ms (yes including a full view dispatch through Smarty 3).
The packager work (based on Symfony 2's ClassCollectionLoader or CollectionClassLoader) is part of a larger effort to better package and arrange the Scorpio files for performance. More details later.
After spending a fair amount of time with PHP5.3+ it is becoming increasingly clear that while Scorpio itself is fine (and does not appear to be generating any E_STRICT notices at all), SimpleTest is not. In fact SimpleTest is making running test cases on PHP5.3+ very hard because it generates a deluge of warnings, notices and deprecated notices. Further there seems to be very little activity with the project.
Because of the above, the decision has been made to transition to PHPUnit and remove SimpleTest from Scorpio. This change will require PHPUnit be installed separately (it will not be bundled). Work is already under way to transition the current test cases and infrastructure. In some instances this is relatively straight forward, in others not.
We realise that this will be a source of frustration for some users (it affects the project as well!!) but it would be more of a pain if left alone.
The change to PHPUnit will not be made until the next major release or possibly one after.
Posted by: Dave Redfern (Writer), in News on 01 May 2010 @ 15:17
This
work is licenced under a
Creative Commons Licence.