On the instrument said the tester small Zhang to developer Xiao Li sent a incisively and vividly bug report, sure enough, Xiao Li according to the small Zhang of this "picture shadow graphics" without any difficulty will be the latent very deep bug caught. But is this bug a bug? I'm afraid I'll have to run again. She found the bug test to confirm that the problem had indeed been resolved. In fact, even if it is not to confirm that the bug has been Shang, Xiao Zhang also had to run a lot of the tests she had done to make sure that the code was changed by the programmers, and that the test that ran before it still ran, which is called regression testing.
It's always frustrating to do the same thing over and over and over again, and vs 2010 can help the little Zhang to get over the problem of regression testing, which is also the opposite of VS 2010, which could be a bright spot for all the manual testers.
Let's take the tester, Xiao Zhang and developer Xiao Li, for example, when Xiao Zhang ran a manual test (called TC 329) that he had written by using MTR (Microsoft Test Runner) in VS 2010, MTR built a "recording/ The playback engine's device will record every step she makes, like a tape recorder. Then Xiao Li, based on this "Operation recording" of Xiao Zhang (which is the action log mentioned earlier), can create a "coded UI Test" in Visual Stuido. "Test (refer to the three pictures below), in essence, he is actually the small Zhang ran the manual test into a based. NET code Automation test.
(Convert manual tests to automated tests using the action "recording")
(Operation of Calculator addition test "recording")
(The operation of the addition Test "recording" is converted to the appearance of the code)