Use VS 2010 to improve the level of automation of software testing (5)

Typically, when a developer fixes a bug based on a tester's report, the tester confirms it again, which means that the test case that found the bug needs to be executed again to make sure that the bug that was found has indeed disappeared. Moreover, many software companies require testers to repeatedly execute test cases that have "uncovered" bugs at the end of each milestone or iteration to prevent those bugs that have been fixed from "showing" again. Obviously, this means that many manual tests are repeated over and over again.

In order to reduce the needless duplication of manual testing personnel, VS 2010 introduces a "tape recorder" feature in its testing tool that allows manual testers to "record" all the steps in the use case when they first execute a test case, which is "recorded" in VS Called Action Log in 2010, when testers need to perform a test case again, they can use the playback function on the tape recorder to automate some continuous operation without having to do each step manually.

In order to have a more intuitive understanding of the "recording" and "Playback" features of manual tests in VS 2010, let's look at a simple example. Let's say we're going to take a look at the addition function of "calculator" in Windows, first we'll create a test case in MTM (Microsoft Test Manager) and then open MTR (Microsoft Test Runner) with this test case. It is important to note that before you run a test case for the first time using MTR, in order for MTR to "record" the entire operation, we must check the "Create Action recording" checkbox (refer to Figure 1) before you start the test.

　

Figure 1 Check the Create action recording checkbox for the first time you perform a test

Then you'll see an interface where the top half of the interface is a test step that testers write themselves when they use MTM to create test cases, and the bottom half of the interface is the MTR automatically recorded in the background (refer to Figure 2).

Figure 2 for the operation "Recording" under the Action step