-
And it's hard to imagine a simpler program than this. So we very quickly realize that exhaustive testing is just never feasible for an interesting program.
更简单的程序了,因此我们很快的意识到,对一个程序来说详尽的,测试是永远不可行的。
-
And if the test is true, it will change the value of this program counter to point to some other place in the memory, some other point in that sequence of instructions, and you'll keep processing.
如果测试结果为真，它会改变程序计数器的结果去,指向记忆存储器里的其他地方，指令序列里的其他地方，然后你会继续这个过程。
-
Well, you could just try it and see if it works, right? That's what testing is all about.
你可以仅仅的去试试运行程序，然后看看结果对不对？这就是测试的内容。
-
There's unit testing, where we validate each piece of the program independently.
一种是单元测试，也就是,分别验证程序中的每一个独立部分。
-
And check the answers, and say yeah that's what we expected. But it also involves reasoning. About why that's an appropriate set of inputs to test it on it.
然后说对，这就是我想要的结果,但是它跟推理也有关系,表现在关于为什么这是一个,测试我们程序的适合的输入集。
-
Testing and reasoning. Testing, we run our program on some set of inputs.
测试就是，我们输入一些信息，并且运行我们的程序，然后查看答案。
-
And they'll test an intermediate value near the end or near the beginning.
他们从最后或者程序的,开始处去取测试需要的中间值。
-
So one of the things I want you to notice here is that testing and debugging are not the same thing. When we test, we compare an input output pair to a specification.
这里我想大家注意的一件事,就是测试和调试是不同的两件事情,我们测试的时候，我们把输入输出,跟程序的规格说明书对比下。
-
Having reached the end of the block, go back up and check the test.
执行到了这块代码的最后，程序会回去再做一次测试。
-
First one, when I write a piece of code, especially code that has branches in it, when I design test cases for that piece of code, I should try and have a specific test case for each possible path through the code.
第一点，当我们写代码的时候，尤其是一些含有分支语句的代码的时候，当我为这些代码,设计测试用例的时候，我应该为每一个可能的程序路径,都设计一个特别的用例。
-
So let's try running Silly.
这个程序是用来测试一个数组是不是回文的。
-
The beauty of this is, it keeps me from getting lazy, and not only testing my program and the thing that found the bug, but in all the things that used to work.
运行函数而不用再输入了，这其中的,美妙之处在于，它让我变的勤快了点,并不是仅仅的去测试程序发现bug方面，同样适用于那些正常工作的模块。
应用推荐