On Wed, Dec 4, 2013 at 9:50 AM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > No, I wouldn’t do that by default: that would defeat the whole purpose of > deprecation. If you want to ignore deprecations, you should do it yourself in > your own tests, at your own risk, IMHO.
what about: - when the preference #raiseWarning: is true, a test sending a deprecated message fails - when the preference #raiseWarning: is false, a test sending a deprecated message succeeds Implemented in: Name: SLICE-Issue-11423-Running-unit-tests-that-raise-deprecation-warnings-makes-them-fail-incomprehensibly-DamienCassou.1 Author: DamienCassou Time: 4 December 2013, 9:56:07.727774 am UUID: bc043b07-b57b-4b5c-b140-8805a4397d31 Ancestors: Dependencies: SUnit-Tests-DamienCassou.31, SUnit-Core-DamienCassou.107 - when the preference #raiseWarning: is true, a test sending a deprecated message fails - when the preference #raiseWarning: is false, a test sending a deprecated message succeeds -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
