Software Testen mit Visual Studio Lab Management

Dec 3, 20122 likes660 views

Nico Orschel

Presentation from Microsoft Techdays 2012 Basel Speakers: Nico Orschel (MVP VS ALM, AIT), Marc Müller (4tecture)

Introduction 5’
Build, Deploy and Test 20’
Infrastructure 10’ Agenda
Lab Management for Devs 15’
Summary / Q&A 10’

You can’t fix
Testers find bugs but may be
unable to document them in
what you can’t
sufficient detail so that they can
be acted upon by developers.
reproduce .
“If it can’t happen twice, it didn’t
happen once” - James (my mechanic)

Developers may not have access to the only
environment in which a bug can be isolated.

Allow testers to create bugs that contain “actionable”
information.

Allow developers the ability to “Make it happen the
second time”

Give developers access to the test environment at the
point the bug was encountered.

Test Case (for
repro steps)

Screenshot

Video Capture

System Info

Debug Log

Test
Environment

Log

Action
Recording

Pre-Prod environment
Web Web DB
UAT Server Server Cluster Release
Manager

QA environment
Dev environment
Web DB
Web + DB
Server Server
Server
Build environment
Web DB
Server Server
Tester
Devs

build
applicati
on

deploy
run
applica
tests
tion

build
app.

restore
snapsh run restore
ot tests env.

take
env. deploy
snapsh app.
ot

Software Testen mit Visual Studio Lab Management

Revert virtual environment to ‘clean’ baseline in
minutes than hours

Predictable (Web) deployment (using MSDeploy)

Post-deployment snapshot facilitates exploratory
testing

Available since Visual Studio 2010
Integrates with Hyper-V
Allows us to:

Team Foundation Server
(TFS) System Center Virtual
Lab Management Machine Manager
Test Case management
Hyper-V Hosts Library Shares
Build management
VM1 LS1
Work Item Tracking
VM2 LS2
Source Control VMn LSn

17

Team Foundation Server
System Center
Lab Management Virtual Machine Manager
Test
Test Case Management Controller

Build Management Hyper-V host Library Share
VM1 Stored Virtual
Source Control Machine
Lab agent

Work Item Tracking Test Agent Stored Virtual
Stored Virtual
Stored Virtual 2
Machine
Machine 2
Build Environment
Build agent
Controller
Client: Client:
Test Manager Visual Studio
Build agent for
Compilation

Microsoft® Visual Studio® 2012 Premium

OR

Microsoft® Visual Studio® Test Professional 2012

No more waiting for build setup

• Revert to a ‘known’ state in minutes
• Predictable multi-machine application deployment
• Know build quality before investing in further testing

No more wasteful testing

• Prioritize test cases based on code changes

No more no repro

• Environment snapshots, Intellitrace and other collectors capture exact state of problem

Allow Testers to capture bugs the first time they happen

Document the hell out of a bug so that even a Developer
can fix it

Use Rich Bug data (Intellitrace, Video, Action Logs,
Snapshot Environments) to find and fix the root cause

Create tests that prove the bug is gone

Continuous delivery is a challenge to implement seamlessly without changing work processes. The key is to introduce automation, responsibility, and a pipeline approach. Automating builds, tests, and deployments using tools like Maven, Jenkins, Vagrant, and configuration management ensures reliable and reproducible software releases. Implementing principles like committing often, comprehensive testing, and promoting changes through stages restores trust and readiness in a project.

Continuous delivery-with-mavenJohn Ferguson Smart Limited

Maven is close to ubiquitous in the world of enterprise Java, and the Maven dependency ecosystem is the de facto industry standard. However, the traditional Maven build and release strategy, based on snapshot versions and carefully planned releases, is difficult to reconcile with modern continuous delivery practices, where any commit that passes a series of quality-control gateways can qualify as a release. How can teams using the standard Maven release process still leverage the benefits of continuous delivery? This presentation discusses strategies that can be used to implement continuous delivery solutions with Maven and demonstrates one such strategy using Maven, Jenkins, and Git.

Continuous Development with Jenkins - Stephen Connolly at PuppetCamp Dublin '12Puppet

Alm 4 AzureClemens Reijnen

This document discusses applying automated application lifecycle management (ALM) practices to Azure cloud development. It outlines 5 scenarios with increasing levels of automation: 1) developers only, 2) adding manual testing, 3) adding automated deployment to a staging environment during builds, 4) adding automated testing during builds, and 5) fully automated testing, building, deployment, and acceptance testing integrated with operations. The document demonstrates configuring automated deployment and testing with Microsoft tools like Visual Studio, Test Manager, and PowerShell for Azure. While increasing automation brings benefits, it also requires more complex build workflows and management of certificates and configurations.

Automated Deployment Pipeline using Jenkins, Puppet, Mcollective and AWSBamdad Dashtban

This document discusses using Jenkins, Puppet, and Mcollective to implement a continuous delivery pipeline. It recommends using infrastructure as code with Puppet, nodeless Puppet configurations, and Mcollective to operate on collectives of servers. Jenkins is used for continuous integration and triggering deployments. Packages are uploaded to a repository called Seli that provides a REST API and can trigger deployment pipelines when new packages are uploaded. The goal is to continuously test, deploy, and release changes through full automation of the software delivery process.

Deep Dive Modern Apps Lifecycle with Visual Studio 2012: Application Lifecycl...Microsoft Developer Network (MSDN) - Belgium and Luxembourg

Automated Deployment with Maven - going the whole nine yardsJohn Ferguson Smart Limited

Automating your build process with Continuous Integration is certainly a great idea, but why stop there? Why not go the whole nine yards and automate the deployment process as well? Staging and production deployments are typically more complicated and more involved than a simple development deployment, but doing them by hand can be time-consuming, tricky and error-prone. Indeed, turning your staging and production deployments into a one-click affair has a lot going for it.

Puppet & JenkinsMatthew Barr

Puppet, Jenkins, and continuous integration (CI) were discussed. The presentation covered installing Jenkins as a master and slaves using Puppet, integrating Github pull requests with Jenkins and Mergeatron, and testing Puppet code with tools like Puppet Lint, Rspec-Puppet, and eventually running Puppet code on VMs. Future work may involve catalog checking and running Puppet code against real systems.

Continuous delivery chernivcyVolodymyr Yelchev

The document discusses strategies for continuous delivery through parallel development and continuous integration, including maintaining feature branches, release branches, and a main development branch. It also outlines the general development workflow and processes for building, deploying, acceptance testing, releasing, and pushing updates to production through automated deployment. The goal is to enable one-click software updates and releases at any time through establishing testing, integration, and deployment best practices.

Deep Dive Modern Apps Lifecycle with Visual Studio 2012: Software Testing wit...Microsoft Developer Network (MSDN) - Belgium and Luxembourg

This document discusses software testing with Microsoft Test Manager 2012 and Lab Management 2012. It provides an overview of the testing process, including: (1) getting the source and compiling projects, (2) copying the build to the test environment, (3) running deployment scripts on each machine, (4) creating an environment snapshot, (5) executing automated tests, (6) sending test results, (7) publishing results to Team Foundation Server. It also discusses features like virtual machine templates, environment management with System Center Virtual Machine Manager, and capabilities for manual testing, snapshot/restore, sharing bug snapshots, network fencing, and support for 3rd party virtualization and physical machines.

Continuous Deployment Pipeline with mavenAlan Parkinson

The document discusses using Maven to implement a continuous deployment pipeline. It addresses how to structure Maven projects to support various test stages like integration and acceptance testing in separate modules. It also provides solutions to issues Maven causes, such as rebuilding artifacts unnecessarily and an inability to simulate release versions, through the use of unique versioning and the Versions plugin. Continuous deployment is achieved by running tests and deploying builds from separate modules after each commit.

Hudson: from build jobs to build pipelinesJohn Ferguson Smart Limited

This document discusses techniques for continuous integration and deployment using Hudson. It recommends using Hudson to automate the build, testing and deployment process. This allows for faster feedback, better visibility and automated delivery. It describes how to use various Hudson plugins to implement continuous integration practices like automatic builds, testing, code quality metrics, notifications and promoting builds through test, UAT and production environments. The goal is to deploy code changes into production automatically through a continuous deployment pipeline.

Build Automation using Maven Ankit Gubrani

Maven is an open source build automation tool used primarily for Java projects to manage builds, documentation, dependencies, and reports. It uses a project object model (POM) file to manage build configuration and dependencies. Maven has defined build lifecycles consisting of phases that execute plugin goals. It provides standard project layout and dependency management. Maven searches dependencies in local, central, and remote repositories. Build profiles allow customizing builds for different environments. Plugins are used to perform tasks like compiling, testing, packaging, and generating documentation.

kishore_NokiaKishore reddy Varra

Kishore Reddy has over 6 years of experience in DevOps engineering using tools like Ansible, Chef, and Puppet for configuration management, version control, and build automation. He has extensive experience setting up OpenStack and Amazon Web Services environments and deploying applications to servers like Tomcat and JBoss. He is proficient in writing scripts, creating Ansible roles/playbooks, and automating deployments through Jenkins.

Apache Maven for SoftServe IT AcademyVolodymyr Ostapiv

413450-rc218-cdw-jenkins-workflowAndy Pemberton

This document provides an overview of Continuous Delivery with Jenkins Workflow. It discusses what Jenkins Workflow is, how to create and edit workflows using the Jenkins graphical interface or external scripts. It also covers integrating tools, controlling workflow flows, script security, and ways to scale workflows using features like checkpoints. The document includes a sample continuous delivery pipeline workflow example and discusses how to extend Jenkins Workflow through plugins.

Version Management in MavenGeert Pante

This document discusses best practices for software version management in Maven. It covers what software versioning is, how Maven can help through plugins like the Maven release plugin, and tips for organizing Maven modules and versions. Key recommendations include using the Maven release plugin to manage releases, determining what scope to version (individual modules, applications or systems), and using Maven plugins like dependency:tree to analyze dependencies and versions:use-next-snapshots to update versions.

Let’s start Continuous Integration with jenkinsTomohide Kakeya

Ci jenkins maven svnAnkur Goyal

An Introduction to MavenVadym Lotar

This document provides an introduction to the Apache Maven build tool. It discusses Maven's history and advantages, including its ability to automate builds, manage dependencies, and generate documentation. The core concepts of Maven such as the project object model (POM), plugins, goals, phases, and repositories are explained. Maven allows projects to be easily built, tested, packaged, and documented through the use of a standardized project structure and configuration defined in the POM.

Alm 4 Azure with screenshotsClemens Reijnen

Release With Maveneugenn

This document describes the Maven release process which involves checking in code, preparing a release by updating POMs and tagging the code, performing the release by deploying artifacts, and rolling back a release if needed. The release:prepare goal updates POMs, runs tests, and commits/tags the code. The release:perform goal checks out the tagged code, runs tests, and deploys artifacts. A single command can prepare and perform the release. Best practices include doing a dry run to simulate SCM operations before an actual release.

Building Java Apps on Heroku and Force.comSalesforce Developers

This document provides an overview of building Java applications on Heroku and Force.com platforms. It discusses key Heroku concepts like dynos, processes, environment variables, add-ons, logging and scaling. It also demonstrates how to deploy a sample Java app to Heroku using the Eclipse plugin and Maven. Tips are provided on OAuth setup, externalizing sessions using Memcache add-on and collaborating with others. Pricing and enterprise options are mentioned at the end.

Jenkins Meetup PuneUmesh Kumhar

This document provides an overview of continuous integration and deployment using Jenkins. It discusses why CI is needed, defines CI and continuous deployment, introduces Jenkins as a popular CI tool, and describes how Jenkins implements distributed builds using a master-slave architecture. Key points covered include how CI provides continuous feedback to developers, how Jenkins integrates various DevOps stages, and how the master schedules jobs and monitors slaves that execute builds.

MavenМарія Русин

Jenkinsconf Presentation - Advance jenkins management with multiple projects.Ohad Basan

Drupal & Continous Integration - SF State Study CaseEmanuele Quinto

Securing jenkinsCloudBees

SharePoint Application Lifecycle Management (ALM)Ayman El-Hattab

This document provides an overview of how to use Team Foundation Server (TFS) to manage the development lifecycle of SharePoint solutions. It describes how developers can use TFS for source control, work item tracking, building and deploying solutions, running tests, and releasing to staging and production environments. Key aspects covered include integrating Visual Studio projects with TFS, running daily builds, testing using virtual machines, and deploying solutions using WSP packages.

Visual Studio 2010 ALM Tools Overview Ayman El-Hattab

This document discusses Microsoft SharePoint MVP Ayman ElHattab and provides information on several topics related to application lifecycle management (ALM) including governance, development, and operations. It also summarizes the evolution of development tools from the 1970s to present day and highlights key capabilities of Microsoft Team Foundation Server 2010 such as work item tracking, version control, test case management, build management, and lab management.

More Related Content

What's hot (20)

Continuous delivery chernivcyVolodymyr Yelchev

Deep Dive Modern Apps Lifecycle with Visual Studio 2012: Software Testing wit...Microsoft Developer Network (MSDN) - Belgium and Luxembourg

Continuous Deployment Pipeline with mavenAlan Parkinson

Hudson: from build jobs to build pipelinesJohn Ferguson Smart Limited

Build Automation using Maven Ankit Gubrani

kishore_NokiaKishore reddy Varra

Apache Maven for SoftServe IT AcademyVolodymyr Ostapiv

413450-rc218-cdw-jenkins-workflowAndy Pemberton

Version Management in MavenGeert Pante

Let’s start Continuous Integration with jenkinsTomohide Kakeya

Ci jenkins maven svnAnkur Goyal

An Introduction to MavenVadym Lotar

Alm 4 Azure with screenshotsClemens Reijnen

Release With Maveneugenn

Building Java Apps on Heroku and Force.comSalesforce Developers

Jenkins Meetup PuneUmesh Kumhar

MavenМарія Русин

Jenkinsconf Presentation - Advance jenkins management with multiple projects.Ohad Basan

Drupal & Continous Integration - SF State Study CaseEmanuele Quinto

Securing jenkinsCloudBees

Continuous delivery chernivcyVolodymyr Yelchev

Deep Dive Modern Apps Lifecycle with Visual Studio 2012: Software Testing wit...Microsoft Developer Network (MSDN) - Belgium and Luxembourg

Continuous Deployment Pipeline with mavenAlan Parkinson

Hudson: from build jobs to build pipelinesJohn Ferguson Smart Limited

Build Automation using Maven Ankit Gubrani

kishore_NokiaKishore reddy Varra

Apache Maven for SoftServe IT AcademyVolodymyr Ostapiv

413450-rc218-cdw-jenkins-workflowAndy Pemberton

Version Management in MavenGeert Pante

Let’s start Continuous Integration with jenkinsTomohide Kakeya

Ci jenkins maven svnAnkur Goyal

An Introduction to MavenVadym Lotar

Alm 4 Azure with screenshotsClemens Reijnen

Release With Maveneugenn

Building Java Apps on Heroku and Force.comSalesforce Developers

Jenkins Meetup PuneUmesh Kumhar

MavenМарія Русин

Jenkinsconf Presentation - Advance jenkins management with multiple projects.Ohad Basan

Drupal & Continous Integration - SF State Study CaseEmanuele Quinto

Securing jenkinsCloudBees

Similar to Software Testen mit Visual Studio Lab Management (20)

SharePoint Application Lifecycle Management (ALM)Ayman El-Hattab

Visual Studio 2010 ALM Tools Overview Ayman El-Hattab

Managing Test Labs Without the HeadachesImaginet

In 2010, Microsoft released a bold new featureset to support management of virtual test environments. "Lab Management" provided the ability to easily spin up test environments, perform automated build and deployments, run automated tests, and collect diagnostic data. Unfortunately, many teams were discouraged by the infrastructure requirements. Now, with Visual Studio 2012 and standard environments, even small teams or groups that can't use Microsoft's Hyper-V can still benefit from lab management. This session will demonstrate how to configure your existing environments for many of the same compelling features formally available only with Hyper-V.

Att lyckas med integration av arbetet från flera scrum team - Christophe Acho...manssandstrom

This document discusses strategies for integrating work from multiple Scrum teams. It outlines the role of an integration team in continuously integrating work. Key success factors for the integration team include: integrating work early, having the necessary resources and environments, practicing continuous integration, using automated tests, maintaining at least two test environments, performing early performance tests, stopping work if integration breaks, having a clear contract between development and integration teams, making the integration process and status visible.

SF DevOps: Introducing VagrantMitchell Hashimoto

Vagrant is a tool for building and managing virtual machine environments. It allows users to create and configure VMs, provision them with automation scripts, and collaborate by sharing the same development environment. Using Vagrant provides benefits like isolation, repeatability, and testing DevOps scripts locally. It also encourages DevOps practices by allowing developers to develop and test infrastructure code in a VM similarly to production.

Visual Studio 2010: A Perspective - David ChappellSpiffy

Big Gains With Little Virtual Machines Sumeet MehraJay Leone

VMware Lab Manager is a solution for managing virtual machine configurations for development and testing environments. It allows users to access a shared library of pre-configured virtual machine configurations. Copies of these configurations can be instantly provisioned using a fraction of the normal storage. Identical copies can run simultaneously on the lab network. An easy to use web portal provides access to the library and resources can be controlled through quotas and leases. Lab Manager helps consolidate infrastructure, reduce costs, and improve provisioning times for tasks like software development, testing, training and demos.

Leveraging Azure for Performance TestingTarun Arora

Working with various clients in the industry I have realized that the biggest barrier in Load Testing & Performance Testing adoption is the high infrastructure and administration cost that comes with this phase of testing. I will present an approach using Visual Studio and Windows Azure to effectively abstract the administration cost of infrastructure management and lower the total cost of Load & Performance Testing. This should hopefully help you leverage Windows Azure for Performance Testing your applications.

Visual Studio 2010 Testing OverviewSteve Lange

This document discusses testing capabilities in Visual Studio 2010, including test case management, lab management, exploratory testing, and coded UI testing. It highlights how Visual Studio 2010 aims to align testing with the development lifecycle and enable tighter collaboration between developers and testers. Key capabilities like test case management allow tracking test cases as work items in Team Foundation Server, while lab management helps simplify environment setup and improves test hardware utilization.

End-To-End Visual Studio Application Lifecycle ManagementHosam Kamel

Visual Studio Application Lifecycle Managment end-to-endHosam Kamel

Releasing fast code - The DevOps approachMichael Kopp

Agile makes you Develop faster, DevOps also makes you Deploy faster but how do you make your Application faster? Many currently used Performance Management practices don’t work anymore as they are too time consuming. It takes a new approach to track performance in Continuous Integration, get more value out of Load Testing and leverage production data for performance optimization. We will show you real world examples on how the new DevOps approach can work.

XebiaLabs, CloudBees, Puppet Labs Webinar Slides - IT Automation for the Mode...XebiaLabs

Virtualize and automate your development environment for fun and profitAndreas Heim

The document discusses using Vagrant to virtualize and automate development environments. Vagrant allows developers to create identical virtual environments that match production. This ensures environments are the same across operating systems and developers. Vagrant uses automation tools like Chef and Puppet to configure environments. It addresses challenges like different dependency versions and allows quick resets. It advocates treating environments as code to make them documented, versioned and easily shared.

Electric CloudFly & Love Story Films TV

This document summarizes an IT solutions company called Electric Cloud. It discusses: 1. The company was founded in 2002 and has grown to 90 employees, shipping products since 2004 and being cash flow positive and ahead of operating plan. 2. Electric Cloud's vision is to lead the market for Software Production Management solutions to remove software production bottlenecks and increase productivity up to 15 times. 3. Electric Cloud's solutions include ElectricCommander to automate processes, ElectricAccelerator to accelerate builds up to 20 times faster, and ElectricInsight for analytics.

Relay health build systemroncordell

The document describes RelayHealth's build and deployment system for a large codebase with over 7 million lines of code maintained by 12 development teams. It outlines the development life cycle which includes daily commits by developers, automated builds and testing, and weekly deployments to test and production environments. The automated build system utilizes CruiseControl.NET to continuously build releases from the code repository, run tests, and promote "green" builds to the test system. Deployments are managed through branching in the code repository and involve building, testing, and deploying code to stage and production environments without downtime. Planned changes include migrating to Team Foundation Server and tools for continuous integration and deployment.

Team Development and Release ManagementSalesforce Partners

If you are building a commercial Force.com app with a team of developers, this session is for you. Join us to learn best practices for setting up your Force.com IDE, managing source code, creating automated builds, deploying to test environments, and more. Hear from a panel of seasoned ISVs who are employing key team development principles. This session is primarily for product managers, architects, and developers (isvpartners).

Mobile DevOps - Trends and ChellengesSanjeev Sharma

Continuous Delivery OverviewWill Iverson

Continuous Delivery refers to the process of releasing high quality software quickly and with confidence through the use of build, test and deployment automation. By applying Lean techniques to the development, test and deployment of software, waste is reduced and staff are freed up to work on more important tasks. By following a continuous delivery model, release cycles shift from a matter of months to weeks or days. In this presentation, we will look at the key tools and processes involved in transitioning from a manual culture to one that embraces automation. We will look at real world examples, including the tools and architectural components. We will discuss organizational impacts, including the dramatic improvements in morale as team delivery commitments are met more easily through automation.

Don't touch that servercrdant

SharePoint Application Lifecycle Management (ALM)Ayman El-Hattab

Visual Studio 2010 ALM Tools Overview Ayman El-Hattab

Managing Test Labs Without the HeadachesImaginet

Att lyckas med integration av arbetet från flera scrum team - Christophe Acho...manssandstrom

SF DevOps: Introducing VagrantMitchell Hashimoto

Visual Studio 2010: A Perspective - David ChappellSpiffy

Big Gains With Little Virtual Machines Sumeet MehraJay Leone

Leveraging Azure for Performance TestingTarun Arora

Visual Studio 2010 Testing OverviewSteve Lange

End-To-End Visual Studio Application Lifecycle ManagementHosam Kamel

Visual Studio Application Lifecycle Managment end-to-endHosam Kamel

Releasing fast code - The DevOps approachMichael Kopp

XebiaLabs, CloudBees, Puppet Labs Webinar Slides - IT Automation for the Mode...XebiaLabs

Virtualize and automate your development environment for fun and profitAndreas Heim

Electric CloudFly & Love Story Films TV

Relay health build systemroncordell

Team Development and Release ManagementSalesforce Partners

Mobile DevOps - Trends and ChellengesSanjeev Sharma

Continuous Delivery OverviewWill Iverson

Don't touch that servercrdant

More from Nico Orschel (20)

TFS Release Management Deep DiveNico Orschel

95 Prozent brauchen es, 5 Prozent machen es: Load Testing mit VS leicht gemachtNico Orschel

TFS 2015: Build und Release der neuen GenerationNico Orschel

Testing XAML-based Windows Store Apps mit VS 2013Nico Orschel

Testmanagement mit Visual Studio 2013Nico Orschel

DWX 2014 - Testmanagement mit Visual Studio 2013Nico Orschel

DWX 2014 - Coded UI in der Praxis: Von Lokalisierung bis NachhaltigkeitNico Orschel

Testmanagement mit Visual Studio 2013 / CodedUI / Neues aus der Produktgruppe...Nico Orschel

UI Testautomation in der Praxis: Von Lokalisierung bis NachhaltigkeitNico Orschel

UI Testautomation in der Praxis ... von Lokalisierung bis Nachhaltigkeit (Cod...Nico Orschel

Ein Dialog unter Fremden: Testautomatisierung in der PraxisNico Orschel

Test Management mit Visual Studio 2012 (Developer Week 2013)Nico Orschel

Links und rechts des Weges: Qualitätssicherung ist mehr als Testfallverwaltung Nico Orschel

Whitepaper Visual Studio 2010 Lab ManagementNico Orschel

Application Lifecycle Management für Tester (mit TFS 2012)Nico Orschel

Whitepaper Team Foundation Server 2010 Lab ManagementNico Orschel

Kürzere Testvorbereitungsphasen durch integrierte TestlaboreNico Orschel

Ausweg aus der Kommunikationskrise oder das Ende von „Bei mir funktioniert’s“?Nico Orschel

Automatisiertes Testen mit CodedUI (ohne Frust)Nico Orschel

Test Management mit Visual Studio 2012Nico Orschel