> On May 8, 2020, at 3:41 PM, Jinmei Liao <jil...@pivotal.io> wrote: > > It's not the test code, it's the "start locator" command itself. >
Same rules apply I think. If the method is deprecated don’t use it. If the method using it is intentionally using the deprecated behavior it too should be deprecated, thus removing the warning (deprecated code can call deprecated code). The non-deprecated methods should not use deprecated methods. If the logic of the deprecated method is still relevant then move it out of the deprecated method and call it from the deprecated method and the non-deprecated method. The fundamental point being that using deprecated code in current production or test code isn’t good practice. Suppression of deprecated code warnings should only be a thing if it's absolutely necessary or a specific and intentional test of deprecated code. A link to the issue at hand might be helpful for context. -Jake
