View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
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
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
Components For CI publish onAzure JetBrains TeamCity Cerebrata Cmdlets Microsoft Azure Account Oracle VirtualBox Local VM Container Powershell Msbuild
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
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