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

The biggest bright spot for Visual Studio 2010 is the number of MS Test Manager tools integrated in Visual Studio Ultimate 2010 and vs Test Professional 2010, It can be said to provide a set of IDE (integrated development environment) tailored for the majority of the test work (which is statistically about 70%). I called it ite (integrated test environment), and in a sense, the appearance of this set of ITE, means that the manual tester will be from the current "Broadsword Lance" era step into the "semi-automatic rifle" era.

Since the ite of VS 2010 is the equivalent of a semi-automatic rifle, where did the semi-automatic rifle achieve 50% of automation and correspondingly reduce the 50% manual labor of the tester? I would like to be able to devote enough time before and after the April 12 vs 2010 Official release to try to clarify this issue in a few paragraphs of blog space.

One of the most compelling automation features in Test Manager, I think, is the automatic collection of bug information. For example, today, if a tester discovers a bug, she usually needs to keep a record of the steps she has made before encountering the bug, and then notify the relevant developer Xiao Li (through bugzilla, for example). If Xiao Li could not reproduce the bug submitted on his own machine based on the information on the bug report submitted by Xiao Zhang, he would usually return the bug report to Xiao Zhang, let her add a more detailed description or ask her to attach a screenshot. If bad luck, it is likely that after several such round-trip, Xiao Li can not reproduce the small report of the bug, needless to say, at this time two people may be because the bug delayed the other work in their hands annoyed.

Although the phenomenon described above by a software person as "bug ping pong" may sound extreme, no developer or tester will be unfamiliar with it, as such mishaps may have fallen on their heads yesterday. The VS 2010 Test Manager is likely to make this so-called "bug ping" phenomenon forever history, it can make every one like Xiao Zhang such a manual tester easily "write" a more informative and informative bug report. Such a bug report can cover the description of each step, a screenshot of the moment of error, complete system configuration information, or even a timestamp-operated video or a complete machine run record that can be used for precise mode (this is called IntelliTrace in VS 2010, The image below is the "looks".

What's even more magical is that if Xiao Zhang is running tests in a virtual test environment managed by Lab Manager (another "killer" in VS 2010), she can also take a "snapshot" of the entire test environment and submit the link to the "Environment snapshot" to Xiao Li together with the bug report, At this time, Xiao Li can directly sit on the link "time Reverse express" back to that let him find the bug crime moment, witnessed the shadowy little "burglar" of the truth.

You reader, please believe what I write is really not science fiction, do not believe that there are pictures as evidence: