As a TSP in DX at Microsoft, I am constantly asked to talk about DevOps and what DevOps means for Microsoft. Although there are many definitions of DevOps floating out in our industry, at Microsoft, DevOps is the merging of people, process and products such that we can continually deliver value to our end users. And clearly, VSTS/TFS and Azure are the products which enables this whole DevOps mindset.
Randy Pagels and I created a DevOps demo which show how VSTS/TFS and Azure can do this. For the next couple of blogs, I will walk you through how to set up our DevOps demo using an asp.net website backed by sql server hosted in Azure. Source control, work item tracking, CI builds and CD pipelines , unit tests, automated ui tests and load tests are all done using VSTS.
All artifacts for this blog series can be found here: https://github.com/abelsquidhead/MercuryHealth
Randy Pagels has written up the actual demo script we use with this demo environment. You can read through the demo script here: http://www.teamsystemcafe.net/WhatsBrewing/Edit/38
Table Of Content
Part 3: Setting up your Git Repo
Part 4: Setting up your Build
Part 5: Setting up your Release Pipeline
This section will walk you through creating a team project, adding the work items needed for the demo to the team project and creating a test plan for the demo.
This demo requires a Team Project using the Scrum Template.
- Browse to your VSTS portal and click on New under Recent projects & teams
- Enter MercuryHealth for project name, select Scrum for process template and Git for version control and select Create project
Adding all the Features, PBI’s, Tasks and Test Cases are done using our command line script. You can download all artifacts needed for this walkthrough here: https://github.com/abelsquidhead/MercuryHealth
- Bring up a command line box and browse to the directory you downloaded this demo
- Call CreateDevOpsDemo /? For the help menu
- Call CreateDevOpsDemo /collection:collectionUrl /p:project /user:username /password:password
If you get any errors trying to authenticate, make sure to setup an Alternate authentication credentials. You are warned to use a Personal Access Token, but a AAC is what is needed to authenticate to VSTS.
In order to create a test plan that makes some sort of sense, we will first move some PBI’s to our first sprint, then create a test plan which just tests the current sprint’s pbi’s.
- Browse to work tab for the MercuryHealth project you just created in VSTS and Click on Work tab, then click on Features
- Open the tree node for Track Nutrition, multi select all the PBI’s under Track Nutrition and move them to Sprint 1
- Click on Test
- Click on the green plus and select Test plan
- Type Current Sprint for the Name and click Create
- Click on the green plus and select Requirement-based suite in the drop down
- Add a search clause for iteration under MercuryHealth\Sprint1, click Run Query, Select all the PBI’s and click Create suites
- You should have a test plan with some cases in them
Next up, part 3. Setting up your git repo for the demo