Maximizing Quality with Visual Studio Team Services Test Hub

Visual Studio Team Services is one of the most widely used application lifecycle management tools today in software development. This course will give you a full gamut of concepts on Test Hub including test planning, execution, and results analysis.
Course info
Rating
(10)
Level
Beginner
Updated
Jun 14, 2018
Duration
3h 13m
Table of contents
Course Overview
Defining Quality
Transitioning from MTM to Test Hub
Maximizing Reuse with a Bottom-up Approach to Test Planning
Creating Best-practice Test Plans and Suites
Minimizing Duplication with Shared Steps
Executing Test Plans
Analyzing Results with Test Hub Reports
Understanding Automated Testing
Facilitating Integrated Device Testing
Description
Course info
Rating
(10)
Level
Beginner
Updated
Jun 14, 2018
Duration
3h 13m
Description

The concept of quality in any software project is arguably one of the most important concepts to foster. In Maximizing Quality with Visual Studio Team Services Test Hub, you will learn the skills necessary to take software excellence to the highest level. First, you will learn about software quality and test execution. Next, you will discover advanced topics such as automation testing and mobile device lab testing. Finally, you will explore test execution analytics. By the end of this course, you will learn everything you need to become a high-performing quality engineer using VSTS.

About the author
About the author

Scott has over 20 years of experience with software development, ALM consulting, and cloud computing.

More from the author
Section Introduction Transcripts
Section Introduction Transcripts

Course Overview
It's an exciting time for Visual Studio Team Services, and with the onset of Test hub in lieu of Microsoft Test Manager, wielding the power of the web toolset is now easier than ever. Whether you're new to the concept of quality and test tools or you're an expert trying to master the best practices of using Test hub, this course will help get you there. Besides some of the basic but critical processes surrounding quality, I also dive into several fun areas such as Power BI data analytics, UI test automation with Selenium, and both manual and automated mobile device testing. This course will take you from A to Z and teach you everything you need to know to get on the right path with Test hub and quality assurance excellence. I hope you join me on this journey. I promise we'll have a little fun while we learn together. At the end of this course, you'll be poised to maximize quality on any software project using the new tools available in Test hub.

Analyzing Results with Test Hub Reports
An integral part of the test execution process is the critical ability to convey the overall progress of the test effort, as well as the quality evolution of the product being built. The QA group often reports on factors that are relevant all the way up to executive levels on a product. It's for this reason that analytics and visuals might be more important to QA than any other team member. The first thing we need to do is understand the iterative effort of analyzing test runs. After each test run, a quick analysis step can impart some critical historical data over the course of builds. Let's see exactly what that means. You remember this slide from the last module, right? Well, this process is still valid, but we learned a few new requirements in the process of executing test cases. In the cycle, the first task includes resetting all the test cases. Test cases need to be reset back to active status prior to each test run. I recommend resetting all test cases every time, as resetting even a single test case generates a test run. Naturally, then test cases are re-executed. After the test run is complete, outcomes are all set on the executed test cases. Some may pass, some may fail, some may be blocked, and some may be not applicable. In either case, all statuses change for all tests run during the execution. At this point, the execution step is complete; however, reviewing test runs and updating the analysis on the unsuccessful test cases is a good practice that can yield some valuable historical information over time. Okay, so the rulebook is getting a little cramped here. If we add any more rules, we're going to need a double-sided scroll me thinks. Let's add rule 6 to the degree, that being the action of updating analyses after test executions. And back comes the Wizard to make sure our decree is inked facetiously in blood. Let's dive into a short demo and see exactly what this all means.

Understanding Automated Testing
Welcome back to the home stretch. I think you'll find the last two modules to be a little bit pushovers, but in a good way. We get to talk about some fun subjects as we wind down. I'm going to take a demo-first approach in this short module and talk about automated testing. Now before you get nervous, I'm only going to gloss over the concept of automated testing, and then show you how it impacts Test hub. If you're poised to learn more about automated testing, just search the subject in the Pluralsight catalog and you'll find many courses. I'm going to run quickly through a very simple Selenium framework, if I can even call it a framework, that I've added to our Test hub demo assembly, which are all included in the exercise files if you're interested, and then I'll show how running that impacts our daily life in Test hub. Let's have a little bit of fun.

Facilitating Integrated Device Testing
Before we wrap everything up, let's dive into another fun module around integrated device testing. I hope you enjoyed tinkering with automation. I know I did. That's one of my favorite subjects to teach. Not to be undone, there are a handful ways we can pull in device testing into our test bag of tools in both manual and automated ways. In this module, let's have some fun as we learn about a few device testing platforms you can use in Sauce Labs and Perfecto mobile, and then wrap up with a neat way to automate some device testing with Perfecto Mobile and VSTS. Since this module once again is about tinkering with some edgy technologies, I'll stick to demos in favor of slides before we wrap up.