Pioneers

At present, becoming a pioneer in geography is quite difficult. There is physics, chemistry, biology ... But there the word pioneer carries a slightly different meaning. Yes, they also go to uncharted areas, but still this is somehow not the case. We, programmers, as well as biologists and etc, are difficult to attribute to the pioneers. But there are people with whom we often argue , but they are the true pioneers of our time. They are the ones who have to climb into the jungle of our interfaces, to understand the complex relationships of our mistakes, and, to be honest, to grumble at us, for the lack of torre ways.
Okay, I tie it up with the lyrics, I start on the topic. Those who were on QADayand listened to Charles Sterlin, in principle, may not read further, by the way, everyone who has already tried Exploratory Testing, in principle, too. For the rest, let me briefly talk about research testing using Visual Studio 11 and, accordingly, TFS 11.
Forward, to the pampas?

Our team works on Agile, there are PBI, acceptance conditions and even, you won’t believe, each PBI has a Test Case, without passing which the team cannot say that the PBI is finished and it’s time for the testers to roll up their sleeves. It is quite clear that if we take the analogy with the jungle, then this is the first hard road:

Everything else is Terra Incognita. Often, getting into these uncharted lands, the tester finds unprecedented animals there. He, with a joyful expression on his face, runs to the programmer: "I, there, saw, here, this, well, like him, damn it!". To which he quite understandably receives the answer: “Well, you know, don’t worry so much. Everything will be fine. I'll go down there and look. You know, I went. There is nothing there. Did you tell me the right way? ” Is that familiar?
And the tester is starting to bridge new roads. He writes new Test Case, and walks on them, and finds new unprecedented animals, and the programmer, walking along this road, also sees them, and he has to hunt them. But the first, largest and most beautiful can not be found.
To prevent such situations from occurring in your jungle, testers using the Microsoft Test Manager (MTM) were able to leave the bread crumbs behind in the jungle.
To get started, go to MTM and select Do Exploratory Testing:


After which we are asked to select the jungle area, it is also PBI (1) and in the path (2):


The environment is ready for work:


We start testing with the “Start” button, launch our application and start testing, poke buttons, write comments, and at some point:


That's it! We won! We found him!
We write down the way we came here. To do this, just click on Create test case. After a short delay, a window of the form opens:


I didn’t even write a name for the Test Case in order to show this window in the exact form in which it was created.
Have you noticed the sequence of steps? All this is automatically generated.
Of course, a tester can rule all this. Expect Result, in the form of beacons, can write down the steps that he believes are not related to playing the bug, which you need to pay attention to during the next runs, but this is lyrics.
All. Named, save. In principle, you can immediately create a bug (there is a good button for this), but it seems more correct to me: close this test. And then try to go through this Test Case in the usual test mode. Type to reproduce and all that. Well, when the error repeats, then create a bug, which is joined by a video of the actions performed by the tester, IntelliTrace, System Information, screenshots, comments, etc. But all this is already from a different fairy tale, so that's all for today.

Ps By the way, if interested, then I found on msdn a ready-made laboratory for arbitrary testing . As usual, I warn you. The link has a lot of pictures and an indisputable desire to download a virtual machine to try it all.