Meet The Man in the Black Shirt. Donovan Brown is a Principal Cloud Advocate Manager of the Methods and Practices Organization in DevRel at Microsoft. Before joining Microsoft, Donovan spent seven years as a Process Consultant and a Certified Scrum Master. Cloud Methods and Practices are his thing. Donovan has traveled the globe helping companies in the U.S., Canada, India, Germany, and the UK develop solutions using agile practices, Visual Studio, and Team Foundation Server in industries as broad as Communications, Health Care, Energy, and Financial Services. What else keeps the wheels spinning on The Man in The Black Shirt? Donovan's also an avid programmer, often finding ways to integrate software into his other hobbies and activities, one of which is Professional Air Hockey where he was ranked as high as 11 in the world.View the profile
About the talk
In this video we'll show you how Visual Studio Team Services (VSTS) Manual Testing capability enables you to plan and execute tests against your next app or website project. We will show you how configure multiple configurations for your test setup (example: OS & Browser combos), how to create a test plan, and execute a test. We also cover how tests can link to the work your team needs to do to fix problems and all activity has full traceability with test run history and links between work and executed tests.
For more information see our documentation: https://docs.microsoft.com/en-us/vsts/manual-test/?view=vsts
Speaker: Donovan Brown
Hi, I'm Donovan Brown principal devops manager from Microsoft manual. Testing can be a key testing technique to deliver a great user experience both Visual Studio team services and team Foundation server offered the features. You need to manage your testing effort from manual and exploratory test to load and stress test going to start right here on the landing page in Visual Studio team Services. I know which account I want to start testing on and from here. I can simply click on the test link. This is what it take me to my test plans
tab a visual studio team Services already have a test plan created. I'll show you how I created that and also what configurations are Witcher incredibly important when you're trying to build out a test Matrix, I click on configuration you're going to be able to quickly see that I have two of them set up. One of them that says Windows 10 and chrome which is the browser on when I use and Windows 10 and Edge, but I also wanted to test on a different browser. Different operating system, I would simply come and add a new configuration. I barely give the configuration of title would say
Windows 10 and Firefox. Do that. I can come down here and add what we call configuration variables one of them for the operating system Windows 10 7/8. I'll show you how is there even though these aren't windows and then I can only come down here and she's a browser and I wanted to choose Firefox. Now when I say that you'll see that I have a new configuration over here on the left hand side below it. I can't control what values I want for browsers and what values I want to be flexible for operating system.
If I wanted to add Mac OS or Linux, I could actually add those here and even add Safari as a Mac specific with X happens to be their browser for this particular configuration and then build out my configuration. Now that I have the configuration that I want. I can apply those to my test plan or specific test Suites or test cases. That's what I build out the Matrix on where I want all those tests to be executed. Create a test plan. You simply come here and create a new plan a plan Subway has a date and a date range that allows us to know over this iteration. We explain to perform this
series of testing people create test plans over work items if they're big enough over releases generally and even over individuals prints that might make up a released so they have his Focus testing that they want to be able to do that with plans and you can create them at any granularity a level that you want. I happen to have a plan generated for the iteration that my team is currently working on now a plan can be broken up into different types of test Suite a suite is a collection of test cases and we offer three different types of tests with that you can use one of them. Is it static
sweet that is literally just a logical container where you can add whatever test cases to it you want the other is a requirement that is where you're taking a product backlog attest to that that Define is accepted. For that particular work item and they're linked together even outside of this particular test plan. And then finally we have a quarry Bay Suite where you can actually write a work out of query that looks for specific types of tasks will automatically populate itself with those particular types of tests. I happen to have all three types
here here. I have an indent s Suite that is a static one where I get to automatically choose which test I want to apply in this particular item. I can create new ones or I can go and run a query and find an existing test case that I might want to add in here and said we add it to the test as well. And now I have to test cases in here. If I open one of these up what you're going to be able to see is the anatomy of a particular test case here. I have the steps to perform open up the admin portion of our site. I went to click on security and then I want you to click on members and what
I'm expecting is able should be shown as a member of the security group here you can have as many steps as you want and they may or may not have expected results, but only those with it But the results when he can pass or fail when you're running through your application wish you had some type of exception. That is a static bass Suite a quarry Bay Suite is one where we actually have a query that defines what is actually going to be shown in this particular list and
this right here. They think it's his only Priority One test cases are ever going to show up in that particular list the right now, we only have Jessica's test showing up in here because it's the only one set the example and change the priority of this test from Priority to two Priority One and save it the next time I revisit this crave a sweet it's going to refresh and now you see that there's two test cases in there because they both meet the criteria of being a priority One Touch case actually is a work item brought into my test plan and all the
associated test cases are also brought in with it. And this is what we call a requirements based sweet. You might notice that the verify Jessica is actually listed twice. The reason why is because if I come here and I look at the assigned configuration Define two different configurations to this test but only one to be able to test if I wanted to go ahead and add the Firefox test to see what you're going to see the Jessica test in here three times have to all be satisfied for a test Matrix to be complete. Now what I want to do very quickly
just show you how you can run one of these tests and collect information on bugs that might show up and how you can go ahead and verify that a test actually works or not. So we're going to do is we're still going to collect this one here and we're going to Simply click on run a new pop-up window and it's going to have all of the directions in it for us to follow through on this machine. I can fire this up on any machine and be running a test on my mobile phone or another device external to my computer. But what I'm going to do is I'm going to follow the same directions right here on the
screen. So it says open the admin which is basically clicking on this gear here. It says open up security which happened to already be open up so I can go and say this is successful in this was successful and then it says click on members which is here and Abel should be shown which he is. So this test is successful at Abel's name not showing up there. I can simply click on the X and I'd be able to leave a comment explaining why this particular item was in I would tell what my expected response was will my actual response was and if I really need it to I could go ahead and create a bug notice
that the bug actually has in it the steps that I took which ones failed in any comments that I had had had I made a screenshot. I can simply copy and paste a screenshot right here into the steps to reproduce to help the engineer who gets this bug assigned to them to Repro the problem and be able to fix it. I'm going to go ahead and cancel out of this cuz I don't need to save it going to go ahead and say that the taxi past instead and now I can still be saved and closes to take your item. What information is going to be the door for us underneath the test top and we can go back in and we can
review our test runs. So now I'll try to come back here. I'd be able to see all the runs that I've done in the past which ones were completed which ones are in progress if there was any bugs filed and also be able to see the outcome of those individual tasks. So getting started with some very powerful. They give me the ability to build out an entire test Matrix with all your configuration test plans into sweets before I go I would encourage you to visit docs. Microsoft.com to learn more about manual testing.
Buy this talk
Access to all the recordings of the event
Buy this video
With ConferenceCast.tv, you get access to our library of the world's best conference talks.