1 / 14

Two Things You Must Have for Lasting Agility

Two Things You Must Have for Lasting Agility. Automated Acceptance Testing and Continuous Delivery Larry Apke Agile Expert www.agile-doctor.com larry@agile-doctor.com. My Definition of Successful Agility.

cece
Télécharger la présentation

Two Things You Must Have for Lasting Agility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Two Things You Must Have for Lasting Agility Automated Acceptance Testing and Continuous Delivery Larry Apke Agile Expert www.agile-doctor.com larry@agile-doctor.com

  2. My Definition of Successful Agility The ability to consistently and predictably deliver high-quality software that the end user can easily understand and use into a production-like environment every iteration. Consistent – every iteration Predictable – over 90% story completion High Quality – fully tested with no end user compromising defects Usable– the end user knows how to, and can, efficiently use the functionality

  3. Symptoms of Unsuccessful Agility Consistency problems Predictability problems Quality problems Usability problems

  4. Automated Acceptance Testing Sometimes described with different terms: TDD – Test Driven Development ATDD – Automated Test Driven Development BDD – Behavioral Driven Development Specification by Example AMDD – Agile Model Driven Development Executable specifications EDD - Example Driven Development AAT - Agile Acceptance Testing

  5. Specification by Example A collaborative approach to defining requirements and business-oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements. It is applied in the context of Agile software development methods, in particular Behavior driven development. This approach is particularly successful for managing requirements and functional tests on large-scale projects of significant domain and organisational complexity. Wikipedia.

  6. Automated Acceptance TestingHow does it differ? Specifications are written in terms of behavior or by using examples Given…When…Then (Initial Context…Event…Result) Referred to as scenarios Focuses the conversation at the right level and becomes something that business and developers can understand Scenarios become the framework for automated tests The tests that are generated/written from scenarios fail when run Code is written / refactored until tests pass and it meets code quality standards

  7. Automated Acceptance TestingBDD Examples Write the Story Feature: Calculator In order to avoid silly mistakes As a math idiot I want to be able to add, subtract, multiply and divide numbers

  8. Automated Acceptance TestingBDD Examples Write the Scenarios Scenario: 1. Add two numbers Given I have entered +50 into the calculator And I have entered +70 into the calculator When I press calculate Then the result should be 120 on the screen

  9. Automated Acceptance TestingSpecFlow Example Code and Passing the Tests Code Coverage Feature Files

  10. Next Step Add Continuous Delivery How long does it take for one line of code that is changed to flow through the delivery chain? How long should it take? Some companies release to production multiple times per day – Flickr, Facebook, Twitter, LinkedIn – are held up as examples

  11. Continuous Delivery Automated Testing Every code check in is a release candidate Broken builds are fixed immediately There is a deployment pipeline that takes release candidates from one level to the next ie Dev, QA, UAT, Production There are different levels of testing along the pipeline based on increasing confidence Highly automated – one button deploy

  12. Continuous Delivery Always use version control Check in everything – “have everything that can possibly change at any point in the life of the project stored in a controlled manner” – Jez Humble – Continuous Delivery Check in to trunk Manage dependencies and configuration through automated scripts Build your environments automatically from scratch

  13. Questions

  14. Recommended Reading/Research Specification By Example - How successful teams deliver the right software Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation The Cucumber Book: Behaviour-Driven Development for Testers and Developers Dan North – Introducing BDD - http://dannorth.net/introducing-bdd/ Fitnesse - http://fitnesse.org/

More Related