Alm 4 Azure with screenshots

ALM 4 AzureTFS 2010 for Azure Cloud Development 26 mei 2011 1

Clemens Reijnen• Sogeti | Management Consultant www.ClemensReijnen.nl @ClemensReijnen Clemens.Reijnen@Sogeti.nl 2

work together__with work packages__on alm artifacts 3

4http://msdn.microsoft.com/en-us/library/bb385832.aspx

ALM 4 Azure Cloud SystemGoals: Collaborative High Quality Flexible Automated Repeatable Efficient 5

Scenario 1: Dev onlyScenario 2: Dev and TestScenario 3: Dev, Test and Build, DeployScenario 4: Dev, Auto Tests and Build, DeployScenario 5: Dev, Auto Tests, Build, Deploy, Acc test and Operations 6

Scenario 1:Developer only 1 Source Production Repository Staging C# 3 TEAM (implementatie + unittests) (TFS) Developers implementeren het systeem  Local unittesting ‘SprintReview’Build  Compile  Run Unit Tests 2 8

dry run – local storage and compute

test run – cloud storage and local compute 10

debug – Intellitrace deploy 11

debug – Get Intellitrace file 13

debug – Find exception 14

debug 15

debug – send to peer 16

Scenario 1:Developer only Pro: Con: Easy installation and configuration No collaboration Single click deployment from VS2010 Easy deployment errors (configuration) What about test and ops 17

Scenario 2:Developer withmanual tester Source Production Repository Staging C# 3 TEAM (implementatie + unittests) (TFS) 1 Developers implementeren het systeem  Local unittesting Testers specificeren testcases ‘SprintReview’Build 4  “Dry” run van tests tegen Development Fabric  Compile  Run Unit Tests 2 19

Microsoft TestManager 21

Source Production Repository Staging TEAM (TFS) 3 1 4 2 1 2 4 Functional, system, Build Verification Platform accepatancemanual tests executed Tests (unit tests) and tests executed onin compute emulator other quality gates, Azure staging - tested with MTM. executed in the build. with MTM.

Microsoft Test Manager – Specify Test Cases 23

Link Requirements to Tasks and Test Cases 24

Specify test case 25

Test with or without debugging 26

without Visual Studio 27

1 Get the CSX folder and CSFG file234

Challenges with changing URL’s

Shared Steps 2 the rescue 30

1 Shared Step : open application 31

1 Shared Step : used by all test cases 32

Fast Forward 33

Diagnostic DataAdapters

Capture information during test execution 35

Create your own adapter.

For example: WAD 37

Or Intellitrace Files 38

Capabilities• Link test cases to requirements• Fast Forward• Test data Iterations• Test case management• Test configurationsInteresting capabilities 4 Azure• Shared steps ( 4 VIPS Swap ) – common practice: new hosted service only change the name in the DNS…• Diagnostic adapters ( Rich bug reports ) capturing the logsNot working capabilities in Azure• Test Impact 4 manual tests• IntelliTrace 4 manual tests (although possible custom adapter) 39

Scenario 2:Developer withmanual tester Pro: Con: Easy installation and configuration Easy deployment errors (configuration) Single click deployment from VS2010 Time consuming (deploy and test) Testers connected, same heartbeat as dev Not repeatable (annoyed testers) Proven quality Testers connected  40

Scenario 3:Developer with manual testerand deployment build 3 Source Production Repository Staging C# TEAM (implementatie + unittests) (TFS) 1 Developers implementeren het systeem  Local unittesting Testers specificeren testcases ‘SprintReview’Build 4  Dry run van tests tegen Development Fabric  Compile  Run Unit Tests 2  Package (CSRun.exe, CSPack,exe, CSManage.exe)  Deploy 2 Staging (CMdLets, Powershell) 42

Automatic Deployment Management API CSPack CSRun CSManage PowerShell CmdLets Build Targetshttp://scottdensmore.typepad.com/blog/2010/03/azure-deployment-for-your-build-server.htmlhttp://blogs.msdn.com/b/tomholl/archive/2011/02/23/using-msbuild-to-deploy-to-multiple-windows-azure-environments.aspx 43

Change .ccproj project 44

CSPack used in Target fileUse PowerShell script 45

Configure build definition

Deploy during build 1. Change .ccproj project • New build target which uses the built-in CorePublish target 2. Create PowerShell script • Called by build target and uses Azure CMDLets 3. Edit Build Config • Add the necessary parameters 4. Do something with certificates • Put the Azure certificate on the build server 47

Scenario 3:Developer with manual testerand deployment build Pro: Con: Easy installation and configuration Time consuming testing No click deployment from build Application can contain ‘annoying’ bugs Repeatable ‘proven’ deployments* Build workflow knowledge necessary Testers connected, same heartbeat as dev Powershell, ccproj tweaks, target files, Proven quality certificates *demo needs some additional environment tweaks for different csfg files per environment 48

Scenario 4:Developer with automated regresiontests, manual tests and deployment build 3 Source Production Repository Staging C# TEAM (implementatie + unittests) (TFS) Test cases (automated UI tests) 1 Developers implementeren het systeem  Local unittesting 4 Testers specificeren testcases ‘SprintReview’Build  Dry run van tests tegen Development Fabric  Compile  Automation van testcases 5  Run Unit Tests (moeten gedraaide testcases zijn voor CodedUI) 2  UI automation tests run tegen Development Fabric  Package (CSRun.exe, CSPack,exe, CSManage.exe) en associëren met test plan  Deploy 2 Staging (CMdLets, Powershell) 50

CodedUI

Different URL’s 1 2 53

UIMap Editor 54

Execute from MTMExecute from VS 55

Execute from BuildExecute from Test Agent 56

Automated Test Settings 57

Where to run the auto test? a) At the Build server? (no … only unit test) b) In the Development environment? (only dry run for autoamtion) c) In the Test environment? (sure, functional tests.. You need emulator at the test env) d) In the Azure environment? Some definitely not all (money) 58

Scenario 4:Developer with automated regresiontests, manual tests and deployment build Pro: Con: No click deployment from build Build workflow knowledge necessary Repeatable ‘proven’ deployments* Powershell, ccproj tweaks, target files, Testers connected, same heartbeat as dev Certificates Proven quality Test Infrastructure knowledge necessary Automated BVT on different Environments A balanced thinking of test automation Comfortable Acc Testing Done Done *demo needs some additional environment tweaks for different csfg files per environment 59

Automated ALM for Azure Cloud development App fa ApplicEfficient, repeatable with proven quality fast Managflexible delivering of useful functionality … 4 (June) AcceptationMaking optimal use of the characteristics of Azure:- Identical environments (Guest OS versioning).- Separate in depended staging production environments. ‘Release ’Drop- Easy up and downgrade of applications.  Package (same as test env- Unambiguous deployment mechanism 3 package)- rich diagnostic capabilities  Acc testing met MTM en- Simplified Application Deployment & Management Diagnostic Data Collectors- … BUILD Production (TFS) Staging C# TEAM (implementation + unittests) Test cases (automated UI tests) Developers implement the system  Local unit testing Testers specify test cases ‘SprintReview’Build  Dry run tests cases against Development Fabric  Compile  Automation of test cases  Run Unit Tests 1  2 Package (CSRun.exe, CSPack,exe, CSManage.exe)  UI automation tests execute against Development  Deploy 2 Staging (CMdLets, Powershell) Fabric and associate with a test case  Run automated Test Suites (MTC.exe) with different environments (test controller – agents infrastructure) Operations determine instrumentation data  Collect and publish test results  DFO, SLA  “Build Verification Tests” green -> deployment 2 ‘test  Usages Metrics, payment production 61

Scenario 1: Dev onlyScenario 2: Dev and TestScenario 3: Dev, Test and Build, DeployScenario 4: Dev, Auto Tests and Build, DeployScenario 5: Dev, Auto Tests, Build, Deploy, Acc test and OperationsScenario 6: TFS on AzureScenario 7: Other Infrastructure on Azure 62

http://www.clemensreijnen.nl	948
http://www.clubcloud.org	83
http://clemensreijnen.nl	51
http://feeds.feedburner.com	33
http://blogs.msdn.com	27
http://paper.li	1
http://www.linkedin.com	1
http://cache.baidu.com	1

Alm 4 Azure with screenshots

by Clemens Reijnen on May 27, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

8 Embeds 1,145

Statistics

Alm 4 Azure with screenshots — Presentation Transcript