Agile .NET Development with BDD and Continuous Integration

Agile .NET Development with BDD and Continuous IntegrationHanoi .NET Group

Agile .NET Developmentwith BDD and Continuous Integration

Hanoi .NET Group – Meetup #6


AgendaIntroduction to BDD – Behavior Driven DevelopmentIntroduction to Specification by ExampleIntroduction to CI – Continuous IntegrationPractices of Continuous IntegrationTools to UseDemosWhat’s NextQ&A


Introduction to BDD – Behavior Driven DevelopmentBehavior-driven development (BDD) is a software development process that emerged from test-driven development (TDD).While in TDD the focus is on writing tests that single out units of the application, BDD is focused on writing tests on the behavior of the application.


Introduction to BDD – Behavior Driven DevelopmentBDD style testing framework

xBehaveWriting user level stories in a form comprehensible by anyone.Typically use a story defined in a DSL close to English and then map this story to a test written in code by the developers.Well-known example: SpecFlow, NBehave

xSpecWriting tests in code using an approach that favors testing behavior and functionality by developers .Usually closer to unit tests in both appearance and granularity but feature some differences.Well-known example: Nspec, StoryQ


Introduction to BDD – Behavior Driven Development#BDD in a tweet:

Using examples at multiple levels to create a shared understanding and surface uncertainly to deliver software that matters

Dan North @tastapod




Dan North @tastapod




Dan North @tastapod




Dan North @tastapod


Introduction to Specification by ExampleWikipedia

Specification by example (SBE) is 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


Introduction to Specification by Example


Introduction to Specification by Example


Introduction to Continuous IntegrationContinuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day.Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly

(Source: http://www.martinfowler.com/articles/continuousIntegration.html)


Introduction to Continuous Integration


Introduction to Continuous Integration


Practices of Continuous Integration

Build

Quality Management

Development

ContinuousIntegration

1 - Maintain a Single Source Repository4 - Everyone Commits To the Mainline Every Day5 - Every Commit Should Build the Mainline on an Integration Machine

2 - Automate the Build3 - Make Your Build Self-Testing6 - Fix Broken Builds Immediately7 - Keep the Build Fast8 - Test in a Clone of the Production Environment9 - Make it Easy for Anyone to Get the Latest Executable

10 - Everyone can see what’s happening

(Source: http://www.martinfowler.com/articles/continuousIntegration.html)


Tools to UseGit is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency


Tools to UseGit Workflow

(Source: A successful Git branching model – Vincent Driessen)


Tools to UseJenkins CI

Jenkins is an open source continuous integration tool written in Java. The project was forked from Hudson after a dispute with Oracle.


Tools to Use


Tools to UseSonarQube

SonarQube is an open source quality management platform, dedicated to continuously analyze and measure source code quality.


Tools to Use

(Source: http://nemo.sonarqube.org/)


What’s NextContinuous Integration and Delivery


What’s NextContinuous Integration and Delivery with Docker


Demos


Q&A


Technology

Agile .NET Development with BDD and Continuous Integration