The Testing Strategy

The Testing Strategy

Domenico Musto

2012 October

Who am I?

25/10/12 www.agiletour.com

About me


Not about me


What do I do?
C#
.NET Team leading
Web REST
Ruby
Automation Testing Agile

@mimmozzo domenico.musto@gmail.com

Today we talk about..
• Differences between types of tests
• Tests and developers
• Tests and QA


..we don't talk about..
• Testing frameworks
• Libraries


The Agile Testing Quadrant


Technology facing


Types of tests
• Unit
• Functional
• Load
• Soak


Unit tests
• They test units of code in isolation
• Interaction between components
• Describe the behaviour
• Drive the design
• Fast execution


Be careful
• Test just public interfaces
• Do not abuse of mocking


Adding a new class is not the trigger for a new test.
The trigger is the implementation of a new requirement.


Functional tests
• They test the interaction with components
outside the context of our application
• They assure integration
• They might be slow


public class When_getting_an_object_from_the_db
{
static int _objectId;
static DbWrapper _sut;
static object _object;

Establish that_there_is_an_object = ()=>
{
_objectId = 100;
ManuallyAddAnObjectInTheDb(_objectId);
}
Because we_get_the_object = ()=> _object = _sut.Get(_objectId);
It should_get_the_object = ()=> _object.ShouldNotBeNull();
}


public class When_storing_an_object_in_the_db
{
static int _objectId;
static DbWrapper _sut;
static object _object;

Establish we_have_an_object_to_save = ()=>
{
_objectId = 100;
}
Because we_save_the_object = ()=> _object = _sut.Save(_objectId);
It should_store_the_object = ()=> _sut.Get(_objectId).ShouldNotBeNull();
}


Be careful
• Do not mix tests
• Use context builders for data fixture


Load tests
• Feedback on performance
• Feedback on volume limit
• Complicated to write
• Slow execution


Soak tests
• Discover technologic issues
• Slow execution


Business facing


Types of tests
• End to end
• Integration
• Exploratory


End to end tests
• They test the whole scope of a feature
• They are acceptance tests
• Understandable from non-techincal persons
• Slow execution


They are not (only) interface tests.


Integration tests
when the end to end aren't brave enough
• They test pieces of the application
• They test the integration
• Slow execution


Exploratory tests
• Manual
• Look for feature limit


Let's implement a feature


The actors of the development process

• Developers
• QA
• Customer


The story

As a user of huddle I would like to add comments to
tasks to collaborate better with my colleagues


df


The feature is ready


What about the tests ?!?!?!


When do I need to do end to end tests ?


Test plan


Test plan
• Acceptance tests
• Functional tests
• Integration tests
• Unit tests


Trade-off


Quality attributes
• Availability
• Modifiability
• Performance
• Security

• Testability
• Usability


The test pyramid


QA Team


QAs are part of the dev team


The reputation of the tests, of the build server and of
the development environment


The deployment


Thanks. Q&A

@mimmozzo domenico.musto@gmail.com


The Testing Strategy

Recommended

Recommended

More Related Content

What's hot

What's hot (6)

Similar to The Testing Strategy

Similar to The Testing Strategy (20)

More from mimmozzo_

More from mimmozzo_ (9)

Recently uploaded

Recently uploaded (20)

The Testing Strategy