对我来说，单元测试是快速运行的 测试，通常测试没有大的外部依赖项（如数据库）的单独的类。
To me, unit tests are fast running tests that typically test individual classes that don't have heavy external dependencies like databases.
我还要强调的是，放弃功能测试并不是总是正确的，因为执行功能测试很快很容易，至少低级的测试是这样的。
I will also argue that it is never all right to forgo functional testing, because it is so quick and so easy to perform, at least a minimal level of functional testing.
我需要决定对不同的测试用例是使用一个测试方法还是多个测试方法。
I need to decide if I will have just one test method or many test methods for the different test cases.
测试、测试再测试。我是一名黑盒测试粉丝。
我创建了一个快速测试结构来测试我的插件(不需要单元测试库)，该结构创建了许多跨区，跨区中是一些数字，紧接数字后面的是该数字的正确格式。
I created a quick test structure to test my plug-in (no need for a unit testing library), which creates dozens of spans with various Numbers and the correct format right after the number.
我发现，用JUnit实现测试分类最简单的方法是将测试在逻辑上划分为与其测试类型相应的特定目录。
I find that the easiest way to implement test categorization with JUnit is to logically divide tests into specific directories corresponding to their test type.
我即将在软件测试协会会议上做的一个报告要问到我们现在所知道的：什么是探索性测试，我们如何进行这种测试？
My upcoming talk to the Conference of the Association for Software testing asks what we know now: what is exploratory testing and how do we do it?
我是否会用到探测性测试、测试驱动设计、确认测试或者其他任何一种方法，又或者是这些方法的综合。
Am I using exploratory testing, test driven design, validation or any other approach or mix of approaches.
（例如，考虑一下，设计1风格中的测试套件：要确保所有用户界面控件在更改后的测试中被涉及是一件多么困难的事情?）长期以来，这导致了我称为“测试套件变质”的问题，完整的测试套件仍旧在运行，但什么也测试不了。
Will the tester even know that's a goal of the suite?) Over time, this leads to what I call "test suite decay, " in which a suite full of tests runs but no longer tests much of anything at all.
（例如，考虑一下，设计1风格中的测试套件：要确保所有用户界面控件在更改后的测试中被涉及是一件多么困难的事情?）长期以来，这导致了我称为“测试套件变质”的问题，完整的测试套件仍旧在运行，但什么也测试不了。
Will the tester even know that's a goal of the suite?) Over time, this leads to what I call "test suite decay, " in which a suite full of tests runs but no longer tests much of anything at all.
应用推荐