Do not to test a private method.

最新推荐文章于 2023-12-19 21:11:57 发布

转载最新推荐文章于 2023-12-19 21:11:57 发布 · 121 阅读

0 ·

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/kklldog/p/4496143.html

本文探讨了单元测试中私有方法的测试策略，提出将私有方法移到独立类中进行测试或通过公共方法间接测试私有方法功能的方法，并强调了只在私有方法功能与公共接口相关时才进行测试。

If you want to unit test a private method, something may be wrong. Unit tests are (generally speaking) meant to test the interface of a class, meaning its public (and protected) methods. You can of course "hack" a solution to this (even if just by making the methods public), but you may also want to consider:

If the method you'd like to test is really worth testing, it may be worth to move it into its own class.
Add more tests to the public methods that call the private method, testing the private method's functionality. (As the commentators indicated, you should only do this if these private methods's functionality is really a part in with the public interface. If they actually perform functions that are hidden from the user (i.e. the unit test), this is probably bad).

http://stackoverflow.com/questions/250692/how-do-you-unit-test-private-methods

转载于:https://www.cnblogs.com/kklldog/p/4496143.html