Hmm ... I noticed that, in trunk (r14896), rt.py is running the
functional tests (including the recorded scripts) with the python -O
flag. Is that intentional?
For one possibly unwanted effect of this, I noticed that the
osaf.framework.script_recording.script_lib module does verification
using assert statements, so no verification is now being done (i.e.
you shouldn't believe the calls in the script to script_lib.VerifyOn()).
Similarly, I'd think that asserts triggered in non-test code would
cause test failures. (Skipping the asserts for perf tests is fine, of
course).
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
