|
Eloy, I think it would be better to display the names of any tests that cannot be carried out, with an appropriate message an colour, instead of just showing nothing at all. I realise that that would be a bigger change, but I think it is worth doing.
Hehe,
in fact that was my first idea. To show some sort of notice about that. I agree developers should be able to view them (to complete-backport as many custom checks as possible). But normal users... they will see something like "This test cannot be performed under Moodle 1.x"... and? Panic? :-/ What's the point about showing to normal users that those custom checks are missing? So, perhaps we could enforce the tests always if running under debug (although I really thing developers don't use to run those env checks in old versions - the fact is that this was broken since ages). I just discovered it when synchronising the environment.xml file between all branches. In the other side... I think we are in the "safe side" up to Moodle 2.0, mainly because 2.0 requires 1.9 and 1.9 has ALL the custom checks properly running. So perhaps we could make another task (2.0, 2.1...) about possible enhancements of the whole environmental stuff. What do you think? Ciao |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Major
Environment custom checks aren't backwards compatible
 |
|
Now, when custom checks are being executed... if they are against future releases... and the custom check (file or function) is missing... just skip the test. In the other hand, if test is for current release, enforce existing file and function.
This way environment.xml are 100% BC, so the HEAD one can run under 18_STABLE and 19_STABLE perfectly.
Ciao