This document discusses using agile practices like emergent architecture, test-driven development, and behavior-driven development when developing applications for Azure. It demonstrates creating a simple "Hello World" Azure MVC application with integration tests in StoryQ. The acceptance tests are extended to support Azure. The document also discusses how continuous integration with tools like TeamCity and Cerebrata CmdLets can be used to automate deploying and testing applications on Azure.

1. Agile and Azure
Emergent Code, BDD , TDD , Team City , Cerebrata
CmdLets
Presented by
Blushpackages : John Mitchell , Becca Martin

2. We started with a single test

3. Practise and Architectural Aims
 To use Emergent Architecture and coding practises
 To follow a Test Driven approach
 To extend our test foot print to Azure
 To put quality first
 To be responsive to requirement change
 To be continually releasable

4. Demonstration Introduction
 What will we demonstrate?
 Creation of a simple “Hello world” Azure MVC application
 Run this application under the Azure emulator to see it working
 Create a StoryQ integration test.
 Add the Azure support to the acceptance test
 Push that down into a base class for reuse.
 Run the acceptance test.
 Talk about how this would then fit with Team City or another CI
engine

5. Lets cut to some code

6. Azure Project Configuration

7. Architecture Diagram

8. CI Process – In Detail

9. Components For CI publish on
Azure
 JetBrains TeamCity
 Cerebrata Cmdlets
 Microsoft Azure Account
 Oracle VirtualBox Local VM Container
 Powershell
 Msbuild

10. CI Process
 Build (Locally)
 Run Unit Tests (Locally)
 Commit
 Run Unit Tests on commit build (CI)
 Publish to staging (Azure)
 Run Watin tests (Azure)
 If all green, VIP swop staging to production for BA (Azure)
 Send notification email with link to published test output
including rich StoryQ output tagged with story numbers

11. Build Output

12. Final Thoughts
 Azure can be integrated into a true Agile Process
 We can evolve our architecture to target Azure with out initial
commitment
 We can use TDD and BDD with Azure
 We can successfully automate deployment with tools like
Teamcity and Cerebrata CmdLets
 We will be publishing the technical details on the blush
packages blog http://blushpackages.com/blog

13. Links and Resources
 Watin : http://watin.org/
 Team City : http://www.jetbrains.com/teamcity/
 CommandLets : http://www.cerebrata.com/
 StoryQ : http://storyq.codeplex.com/
 Azure : https://www.windowsazure.com
 Nunit : http://www.nunit.org/
 NSubstitute : http://nsubstitute.github.com/
 Agile : http://www.blushpackages.com/Blog/post/WAgile-or-Agile-.aspx
 Emergent Architecture :
http://www.blushpackages.com/Blog/post/emergent-design-
overview.aspx
 BDD : http://www.blushpackages.com/Blog/post/bdd-overview.aspx

14. That’s All Folks
 John Mitchell - Freelance Developer / Architect
Johnm@blushpackages.com
Twitter @jemmitch1
 Becca Martin - Developer /Architect, Agile Coach, Azure
Evangelist
beccam@blushpackages.com
Twitter @martindotnet
Blush Packages Blog : http://blushpackages.com/blog
Slides : http://blushpackages.com/presentations