Agile Mëtteg series - Session 5

Agile testing
Agile Mëtteg – 15 July 2010

Agile Mëtteg in 2010
Complete Agile Mëtteg calendar on
www.agilepartner.net/agility_seminars.html
15 July 2010
Agile Mëtteg - Agile Testing
2

OBJECTIVES & AGENDA
Objectives
This session will focus on a Agile Testing and provide you with practical examples and techniques to help your team understand what is behind this approach.
Agenda
Introduction of Agile Partner
The attendees
What is agile testing? And why? And how?
Unit testing
Behaviour Driven Development
Test Driven Development
Acceptance testing
Q&A
15 July 2010
Agile Mëtteg - Agile Testing
3

AGILE PARTNER SERVICES
15 July 2010
Agile Mëtteg - Agile testing
4
IS users Services
1
Custom Software Development & Maintenance
Our core business to answer customer needs
IS services
Thanks to our expertise we can support IT team to reach their productivity & quality objectives (Assessment, Coaching, Support, Training, Resource delegation…)
IS Solutions
Take benefit from commercial or Open Source platform to answer as quick as possible to specific needs
IS users services
We can support Product & Services owners to work closely with the IT team (Assessment, Coaching, Support, Training, Resource delegation…)
4
Software Development & SoftwareMaintenance
2
ISSolutions
IS Services
Agility
Agility
3
1
2
3
4
Agility

NEXT TRAININGS & CERTIFICATIONS
15 July 2010
5
-15%
Complete calendar on: http://www.agilepartner.net/training/training_calendar.html

Let’s get acquainted
July 15th, 2010
Agile Mëtteg – Agile Testing
6

PRESENTATION OF THE ATTENDEES
Who are you ?
What is your role ?
What do you know about agility ?
What are your expectations ?
July 15th, 2010
Agile Mëtteg – Agile Testing
7

AGENDA
Agenda
What is agile testing? And why? And how?
Unit testing
Acceptance testing
15 July 2010
8

WHAT IS SOFTWARE TESTING?
Definition:
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.
(Wikipedia)
15 July 2010
9

WHAT IS SOFTWARE TESTING?
Definition:
Software testing is a way to measure the quality of the product using tests.
(Stephan Zimmer & Eric Ferrot)
15 July 2010
10

MEASURING QUALITY
Measuring quality using tests:
tests to find defects
functional / non-functional testing
a LOT of kinds of tests
15 July 2010
11

15 July 2010
12
SO WHAT IS AGILE TESTING ?… AND WHY?… AND HOW?

Traditional / Waterfall approach
Testing is done after the development
WHAT IS AGILE TESTING?
15 July 2010
13

Agile approach
Testing is part of the development process
15 July 2010
14
Iteration 1
Iteration 2
Iteration n
No specific order

15 July 2010
15
Programmer
Traditional / Waterfall approach
Testing is done after the development
Clear separation of roles
Domain Expert
Tester

Agile approach
A whole team
15 July 2010
16
Programmer
Programmer
Domain Expert
Tester
Tester

Agile testing places an increased portion of the testing in the hands of the developers
Wait… WHAT?!?!
I’m a programmer not a tester
It’s trivial I don’tneed a test
I don’t have time for testing
My code isverydifficult to test
15 July 2010
17

WHY AGILE TESTING?
WHY should developers write tests?
Fear / Confidence
Do you dare to change the code?
 Tests = safety net
It places developers as users
 Better usability
It makes the code testable
 Better design
15 July 2010
18

WHY AGILE TESTING?
A better design
“How good the design is doesn't matter near as much as whether the design is getting better or worse.
If it is getting better, day by day, I can live with it forever.
If it is getting worse, I will die.”
(Kent Beck )
15 July 2010
19

AGILE TESTING… HOW?
Agile testing… HOW?
Unit testing
Acceptance testing
15 July 2010
20

BUT FIRST…
15 July 2010
21

LET US INTRODUCE YOU TO…
15 July 2010
22
TIME MASTER TIM!

AGILE TESTING… HOW?
DINO LEGS
A real project
A new feature:
„The Crystal Quest“
15 July 2010
23
http://dinolegs.blogspot.com/

UNIT TESTING
15 July 2010
24

UNIT TESTING
Definitions
Unit :
Smallest testable part of an application
Unit test :
A method to test a unit
15 July 2010
25

UNIT TESTING
Some bad things about unit tests:
Expensive to write and expensive to maintain
You can test too much
You can test the wrong things
Possibility to get false sense of security when all tests pass
No integration tests
15 July 2010
26

UNIT TESTING
Why write unit tests?
More confidence in the code
Avoid regression
Tests themselves are documentation
Encourages better software design: minimal interfaces and modularity
15 July 2010
27

UNIT TESTING
The „3A“ pattern
Arrange
Act
Assert
15 July 2010
28

UNIT TESTING
F.I.R.S.T.
Fast
Independent
Repeatable
Self-Validating
Timely
[Clean Code – Robert C. Martin]
15 July 2010
29

UNIT TESTING
„The act of writing a unit test is more an act of design than of verification“
(Robert C. Martin)
15 July 2010
30

UNIT TESTING
A lot of existing unit testing…
xUnit (NUnit, Junit, csUnit, …), MSTest, Pex, Visual Studio UTF, etc.
…and mocking frameworks
Moq, Rhino Mocks, Moles, TypeMock, JMock, etc.
15 July 2010
31

TEST DRIVEN DEVELOPMENT (TDD)
15 July 2010
32

15 July 2010
33
Unit Test
What is TDD?
Difference to unit testing
Write the unit test
Code
FIRST!

What is TDD?
Difference to unit testing
Write the unit test FIRST!
« Red – Green – Refactor » pattern
15 July 2010
34

Red – Green – Refactor
Make it failwrite the test first
Make it workwrite the simplest implementation
Make it betterrefactor without changing the behavior
15 July 2010
35

TEST DRIVEN DESIGN (TDD)
TDD is not only about testing
Also called Test Driven Design
TDD is a methodology that helps creating a good design when developing code.
15 July 2010
36

TEST DRIVEN DESIGN (TDD)
TDD is not only about testing
Also called Test Driven Design
TDD consequences
YAGNI
DRY
Law of Demeter
Single responsibility principle
Interface segregation principle
Inversion of control
15 July 2010
37
GOOD DESIGN !

DEMO
15 July 2010
38

ACCEPTANCE TESTING
15 July 2010
39

ACCEPTANCE TESTING
Unit testing tells us that the code is meeting the programmer‘s expectations
Unit testing is essential but not sufficient
Acceptance tests are specifications for the
desired behaviour and functionality of a system.
Customer oriented
About the what and not the how
Usually black box system tests
Integration tests character
15 July 2010
40

ACCEPTANCE TESTING
Implementing acceptance tests
 means automation
Examples of automation tools:
Framework for Integrated Test (Fit) is an open-source tool for automated acceptance test
Fitnesse is a webserver, a wiki and an automated testing tool based on Fit
15 July 2010
41

ACCEPTANCE TESTING
DEMO
15 July 2010
42

BEHAVIOUR DRIVEN DEVELOPMENT (BDD)
15 July 2010
43

BEHAVIOUR DRIVEN DEVELOPMENT
Behaviour Driven Development (BDD)
Evolution of TDD introduced by Dan North
Using terminology focused on the behavioural aspects of the system rather than testing
 Unit ≠ behaviour
 Focus on why the code should be created
 Business value > Code
 Specification > Test
15 July 2010
44

Outside-in methodology
 from the known to the unknown
Helps the developer to think YAGNI
 Leads to better design
 BDD = Behaviour Driven Design
Don‘t forget about the roots (TDD)
 Red – Green – Refactor
15 July 2010
45

Programmer
Ubiquitous language
based on the business domain
Common vocabulary between participants
Minimizes translation
Avoids miscommunication
Makes it easier to validate early
Domain Expert
Tester
15 July 2010
46

Story framework
Each feature is captured in a „story“, which defines the scope of the feature along with its acceptance criteria
Feature
Feature: Title
As a [role]
I want [feature]
so that [benefit]
Feature: Crystal quest
As a player
I want to collect time crystals
so that I am able to complete the crystal quest
15 July 2010
47

Scenario / Acceptance criteria
Scenario:Title
Given some initial context,
And some additional context,
When an event occurs,
Then ensure some outcomes
Scenario 1:Tim loses a crystal
Given a Tim is on screen
And a crystal is on screen,
When Tim dies,
Then the crystal disappears
And Tim‘s player score is decreased by 20
Scenario 2:Tim collects a crystal
Given Tim is on screen
And a crystal is on screen,
When Tim touches the crystal,
Then the crystal disappears
And a nice music is played
And Tim‘s player score is increased by 100
15 July 2010
48

Several existing tools for automation
JBehave, NBehave, JSpec, NSpec, CppSpec, PHPSpec, SpecFlow, RSpec, Cucumber, …
 Executable specification
 Quick feedback and regression testing
 Requirements are tests
 Tests are documentation
15 July 2010
49

DEMO
15 July 2010
50

SUMMARY
15 July 2010
51

SUMMARY
Some things to remember about Agile Testing:
Whole-team approach: roles not that strictly separated as in traditional approach
Building a testable architecture leads to a better design
... and don‘t forget!
Setup a working environment
15 July 2010
52

QUESTIONS
53
15 July 2010

NEXT TRAININGS & CERTIFICATIONS
15 July 2010
54
Complete calendar on: http://www.agilepartner.net/training/training_calendar.html

RESOURCES
Agile Partner: www.agilepartner.net
Agile Interest Group Luxembourg:www.aiglu.org
Agile Alliance: www.agilealliance.org
Scrum alliance: www.scrumalliance.org
Scrum.org
15 July 2010
55

CONTACTS
Thank You
15 July 2010
56

Agile Mëtteg series - Session 5

by Agile Partner S.A.

Accessibility

Categories

Upload Details

Usage Rights

1 Embed 9

Statistics