Laura Perales

Before continuous integration

Before continuous integration

We have…

We want…

We need…

QA

3 2

1

DEV2 3

time

21

PROD

… chaos

… an agile development cycle

… a process!

Code process

1 week 1 week

INTEGRATION

INTEGRATION

Project 1

Project 2

Project 3

Project 4

Project 5

PROD

ReverseIntegration

Integration test

1 week

CODE COMPLETE CODE FREEZE CODE COMPLETE CODE FREEZE

Building process

Branch 1

Branch 2

Branch 3

Code Repository

1

1

2

3

2

3

Builds Test environments

TEST

AUTOMATION

SCM

We want …- … to improve quality in our products

- … more time for less obvious test

The QA team…- … has low programming skills

- … is tired of executing repetitive tests

- … feels the pressure of time to market

What do we need?- 24h of automatic tests

How to begin?

Finding resources to implement it...

... without compromising the current roadmap…

... but keeping the knowhow inside

the company.

SUPPORT

MANAGEMENT

SUPPORT IS THE KEY

Add the project to the calendar.

Assign resources focused 100% on the implementation and convince your marketing fellows.

Try to keep it in-house.

- Obstacles -

- Solutions-

FLEXIBILITY

Choosing suitable tools...

... with a tight budget…

... but the system has to be maintainable.

FLEXIBILITY IS THE KEY!

Don’t adapt the team to the tool, choose a tool accordingly to the skills of the ones who will use it ...

... use trial versions, open source applications...

... cheap tools can become expensive when trying to maintain the tests.

- Obstacles -

- Solutions-

Stages

Stage 2: Tools Evaluation- Search

- Compare

Stage 3: Kick off- Automation of real test cases

- Model review

- Proof of concept

- Buy or download!

Stage 1: Definition- Requirements

- Consider Maintainability

Stages

Stage 5: Transfer- Transfer to QA team

- Pilot test using a real project

- Testers maintain the scripts

- SCM maintains the infrastructure

Stage 6: Maintainability & Monitoring

Stage 4: Infrastructure- Software configuration

- Automatic launch

- Test Report generation

- Link with building process

Cost vs Value

Implementing continuous integration means…

Interdepartmental teamwork- Departments who participate in early stages of a project have to be

committed

No need of big economical investment- Use “FLEXIBILITY”: flexible tool and/or flexible team

Taking advantage of time and not wasting time- Testing within continuous integration is agile

“Shelfware” fear will not materialise: - maintainability is properly supported and planned

- implementation is SUPPORTED by other departments

------------------------------------------------------------------

laura.perales@infojobs.net