Hi guys,
Deprecation is a subclass of Warning, not Error. And I think this is
absolutely correct.
So the basic question here is if the action on Warnings and
Notifications in general in SUnit is correct or should be changed.
This is not necessarily limited to Deprecation.
Of course we need a possibility to test assertions about Deprecations
and other Notifications as well, so it sure is not a good idea to make
"transparent" changes and simply ignore Deprecation or any other kind of
Notification/Warning.
Just my 2 cents
Joachim
Am 05.12.13 10:41, schrieb b...@openinworld.com:
Luc Fabresse wrote:
Hi All,
I think that trapping Deprecations silently is not a good idea.
As you said, people will not see them and it will be hard to upgrade
code.
Why not having a Preference?
or another button in the TestRunner such as: "Run ignoring Deprecation"?
#Luc
2013/12/4 Damien Cassou <damien.cas...@gmail.com
<mailto:damien.cas...@gmail.com>>
On Wed, Dec 4, 2013 at 9:18 AM, Marcus Denker
<marcus.den...@inria.fr <mailto:marcus.den...@inria.fr>> wrote:
> There is a related bug tracker entry:
I will try to propose a slice that ignores deprecation warnings while
running the tests. But this will make it harder for people to find
deprecated message sends.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
Or adding a new reported category "Deprecations" to go with "Expected
Failure"
--
-----------------------------------------------------------------------
Objektfabrik Joachim Tuchel mailto:jtuc...@objektfabrik.de
Fliederweg 1 http://www.objektfabrik.de
D-71640 Ludwigsburg http://joachimtuchel.wordpress.com
Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
