Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Mark Obsolete messages as error in v4.7 #736
It depends. There are basically two option:
Sometimes, features keep implemented, even though we let the C# compiler give a compile error. This allows older integration libraries (built by others) that depend on that feature to keep working, while you allow new development to stop using that feature. This is a strategy I don't often use btw.
But as long as the feature is implemented, unit tests are warranted, although, since the feature is ready to be removed, unit tests could theoretically be removed, although that risks introducing breaking changes on code that might still be used by other libraries.
In case the feature is no longer implemented, the solution is simple: remove the unit tests.