08 hopex v next vsts -v2

9
Building More Reliable And Better Performing Web Applications With Visual Studio Team Service HOPEX VNEXT – VSTS OCT. 2016 – MICHEL BRUCHET - ARCHITECT

Upload: michel-bruchet

Post on 14-Apr-2017

55 views

Category:

Services


0 download

TRANSCRIPT

Page 1: 08 hopex v next   vsts -v2

Building More Reliable And Better Performing Web Applications With Visual Studio Team Service

HOPEX VNEXT – VSTS

OCT. 2016 – MICHEL BRUCHET - ARCHITECT

Page 2: 08 hopex v next   vsts -v2

P a g e 2

What is VSTS?Tracking

work

Code repository

Build

Deployment

Package

Test

Page 3: 08 hopex v next   vsts -v2

P a g e 3

Work items

Teams use the work item types (WITs) provided with the Agile process to plan and track progress of software projects. Teams define user stories to manage the backlog ofwork and then, using the Kanban board, track progress by updating the status of those stories

To gain insight into a portfolio of features, scenarios, or user experiences, product owners and program managers can map user stories to features. When teams work in sprints, they define tasks which automatically link to user stories.Using the web portal or Microsoft Test Manager, testers can create and run test cases. Bugs and issues are used to track code defects and blocking issues.

Work items | Bug | Build | Release | Package | Test

Page 4: 08 hopex v next   vsts -v2

P a g e 4

Manage bugsWork items | Bug | Build | Release | Package | Test

How do you track and manage defects in your code? How do you make sure software problems and customer feedback get addressed in a timely manner to support high-quality software deployments? And, how do you do this while making good progress on new features?

At a minimum, you need a way to capture your software issues, prioritize them, assign them, and track progress. Moreover, you'll want to manage your bugs in ways that align with your Agile practices

Page 5: 08 hopex v next   vsts -v2

P a g e 5

Manage your buildWork items | Bug | Build | Release | Package | Test

To build your code or deploy your software you need at least one agent, and as you add more code and people, you'll eventually need more.

You can have more than one build definition for your code, each definition build contains more than one step. Each step can• Execute a build Action• Use Utility• Execute Test• Package build, publish it• Deploy the build

Page 6: 08 hopex v next   vsts -v2

P a g e 6

Manage your releaseWork items | Bug | Build | Release | Package | Test

Support a rapid release cadence and manage simultaneous releases. Set up release definitions that represent your environments from development to production. Run automations to deploy your app to each environment. Add approvers to sign off that the app has been successfully deployed in an environment. Create your release manually or automatically from a build. Then track your releases as they are deployed to various environments

Page 7: 08 hopex v next   vsts -v2

P a g e 7

Manage your packagesWork items | Bug | Build | Release | Package | Test

Package Management is an extension that makes it easy to discover, install, and publish packages. It's deeply integrated with other Team Services hubs like Build so that package management can become a seamless part of your existing workflows.

Page 8: 08 hopex v next   vsts -v2

P a g e 8

Manage your testsWork items | Bug | Build | Release | Package | Test

Test continuously while you code, build, and deploy your app. Find problems before launching your app or updates into production. You can then better assess whether your app meets your customers' needs and is ready for release

VSTS supports• Manual and exploratory testing• Continuos testing• Performance testing• Developer Unit testing• Cloud mobile testing

Page 9: 08 hopex v next   vsts -v2

P a g e 9