Bridging the communication Gap & Continuous Delivery

6,472 views

Published on

This is a case study of a top retailer in UK which was following Agile but not all the Agile practices. We will discuss how collaboration between business and engineering team improved using BDD and how it was used to generate automated acceptance tests. We will also discuss how continuous integration was implemented which laid foundation for continuous delivery.

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
6,472
On SlideShare
0
From Embeds
0
Number of Embeds
3,937
Actions
Shares
0
Downloads
29
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • This is a case study of a top retailer in UK which was following Agile but not all the Agile practices. We will discuss how collaboration between business and engineering team improved using BDD and how it was used to generate automated acceptance tests. We will also discuss how continuous integration was implemented which laid foundation for continuous delivery.
  • This is a case study of a top retailer in UK which was following Agile but not all the Agile practices. We will discuss how collaboration between business and engineering team improved using BDD and how it was used to generate automated acceptance tests. We will also discuss how continuous integration was implemented which laid foundation for continuous delivery.
  • Bridging the communication Gap & Continuous Delivery

    1. 1. Bridging the communication Gap & Continuous Delivery Case study of a top retailer in UK Masood Jan Mazataz Ltd
    2. 2. Agenda Communication Gap. Bridging the Gap. Simplifying Automated Functional & Unit Testing. Continuous Integration. Path to Continuous Delivery.
    3. 3. The CommunicationGap • The BA/Arch agree with business regarding stories (epics) and creates HLD/LLD. • The Developer reads the LLD and sometimes makes a different set of assumptions to create code. • The Tester reads the requirements and may make a second set of assumptions to create test plans • The Developer finishes the story, does the “Works On My Machine” stuff, and checks in. • The Testers wait for a build in Test Environment, usually couple of hours/days. • If Build was successful tester verifies function against test plans. • Identifies defects raises them. • Developer analyses the defect, debugs to fix it. • The Testers wait for another build.
    4. 4. The Result Late feedback. Confusion during development and testing. Change of requirements not clearly propagated. Surprises.
    5. 5. What was needed  Focus on development and delivery of Prioritised, Verifiable Business Stories.  Focus on providing a common vocabulary that bridges the gap between Business and Technology.  Focus on exposing business rules to be reviewed by stake holders.  Focus collaboration between Developers, Testers, Architects, BA’s and the Business.  Make it easy to Automate functional testing.
    6. 6. What did we doWe behaved ourselves!
    7. 7. How did we do that Have Small Vertical stories of Business Value. Agree & Document business rules. Agree & Document the behaviour. Agree how story would be accepted. Create executable scenarios for each behaviour.  Given, When and Then. Develop the behaviour and verify the scenarios. Show completed scenarios to Truth. React to feedback. We synched up!
    8. 8. The Result Business and engineering team speak same language. Quick Feedback. Requirements changes were easily communicated. No surprises.
    9. 9. What tools we used ? JBehave (Java) Selenium for web applications.
    10. 10. Why JBehave? Java, all the teams were aware of it. Built on JUnit framework. Scenarios written in text file. Given , When & Then annotations. JBehave code generator (custom). Integrates well on CI.
    11. 11. The JBehave Framework
    12. 12. See it in Action ! Simple Login Story
    13. 13. Example StoryStory Title: Login to the Customer Service Centre (CSC)So That: I can resolve customer issue with an orderAs: A userI Need: To Login to the CSCAcceptance Criteria:1. I should be able to login using valid username and password2. I should not be able to login using invalid username or password
    14. 14. Defining ScenariosScenario 1: Valid LoginGiven the user is on Login PageWhen the user types user name service And the user types password service And clicks login buttonThen the user should be logged in And the user should see a message, Welcome, Service Administrator.Scenario 2: Invalid LoginGiven the user is on Login PageWhen the user types user name wrong And the user types password wrong And clicks login buttonThen the user should not be logged in And the user should see a message, Invalid Username or Password.
    15. 15. JBehave Code Generator • Create valid_login.scenario file in eclipse. • Copy login scenario into it and save. • Right click on this file and choose • JBehaveCodeGenerator • Generate Code • This will create two java files • ValidLogin.java • ValidLoginSteps.java
    16. 16. ValidLogin.javapublic class ValidLogin extends Scenario { public ValidLogin () { super(new ValidLoginSteps()); }}
    17. 17. ValidLoginSteps.java public class ValidLoginSteps extends Steps { @Given("the user is on the Login Page") public void theUserIsOnTheLoginPage() { throw new RuntimeException("Step not yet implemented"); } @When("the user types username $username") public void theUserTypesUsername(String username) { throw new RuntimeException("Step not yet implemented"); } @When("the user types password $password") public void theUserTypesPassword(String password) { throw new RuntimeException("Step not yet implemented"); } @When("clicks login button") public void clicksLoginButton() { throw new RuntimeException("Step not yet implemented"); } @Then(“the use should be logged in") public void theUserShouldBeLoggedIn() { throw new RuntimeException("Step not yet implemented"); } }
    18. 18. Working Example A Happy Path Order Capture
    19. 19. JUnit Testing using BDD Mockito
    20. 20. Mockito Mockito library enables mocks creation, verification and stubbing. Similar to Jbehave with given, when, then steps.. Enables Behaviour testing of java components i.e Formhandlers, Managers, Repositories.. etc. Mocks all objects a component uses and verifies if it is using it correctly according to the behaviour.
    21. 21. Mockito Example public class RepositoryUpdaterTest { @Mock MutableRepository mockRepository; @Mock MutableRepositoryItem mockRepsitoryItem; @Test public void shouldUpdateRepositoryWithAString() throws Exception { //given String valueToBeCreated ="Test"; RepositoyUpdater repositoyUpdater = new RepositoyUpdater(); repositoyUpdater.setSomeRepository(mockRepository); //when repositoyUpdater.updateRepositoryWithThisString(valueToBeCreated); //Then verify(mockRepository).createItem(valueToBeCreated); } }
    22. 22. Continuous Integration A quick feedback
    23. 23. What we have CI Topology Check in build Pipeline Release Builds Pipeline Check-in best practice
    24. 24. The CI
    25. 25. Check-in Builds Pipeline
    26. 26. Check-in Builds
    27. 27. Static Code Analysis
    28. 28. Sonar Report
    29. 29. Release Build Pipeline
    30. 30. Release Builds
    31. 31. Deployment Pipeline
    32. 32. Automated Database ChangeProcess Using DBDeploy
    33. 33. Acceptance Tests
    34. 34. The Status
    35. 35. Check-in Best Practice  CI monitor close vicinity  Checkout when CI is green  Just before checkin see if CI is still green  If Red then wait until green, find out why it is red  Do a get when its green  Build locally again with tests.  Then Checkin  Check for CI building your code.  If Red due to your checkin, fix it ASAP  When CI is green after your checkin, then relax
    36. 36. For more information BDD : http://dannorth.net/introducing-bdd/ Jbehave : http://jbehave.org/ Mockito : http://mockito.googlecode.com/svn/tags/latest/j avadoc/org/mockito/Mockito.html Jbehave Code generator : http:/www.mazataz.com/resources.html
    37. 37. Questions?

    ×