• Save
Agile azure manchester azure user group  v3
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Agile azure manchester azure user group v3






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Agile azure manchester azure user group v3 Presentation Transcript

  • 1. Agile and AzureEmergent Code, BDD , TDD , Team City , CerebrataCmdLetsPresented byBlushpackages : 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 CIengine
  • 5. Lets cut to some code
  • 6. Azure Project Configuration
  • 7. Architecture Diagram
  • 8. CI Process – In Detail
  • 9. Components For CI publish onAzure 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 outputincluding 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 initialcommitment We can use TDD and BDD with Azure We can successfully automate deployment with tools likeTeamcity and Cerebrata CmdLets We will be publishing the technical details on the blushpackages 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 / ArchitectJohnm@blushpackages.comTwitter @jemmitch1 Becca Martin - Developer /Architect, Agile Coach, AzureEvangelistbeccam@blushpackages.comTwitter @martindotnetBlush Packages Blog : http://blushpackages.com/blogSlides : http://blushpackages.com/presentations