First structure, then tool; but do not over structure€¦ · Level 5: Optimization, Defect Prevention and Quality Control Level 4: Management and Measurement Level 3: Integration

First structure, then tool; but do not over structure

Eurostar 1 December Maurice Siteur

© 2004 Capgemini - All rights reservedCOP avond testtools / 2 Capgemini Nederland

Program

Introduction

Measuring the structure of a test process

Moment to start with tooling

Can tooling help you to improve/structure your test process?

Conclusion


Introduction

Maurice Siteur20 years experience (13 in testing)Test manager/coach/consultantAuthor of book: ‘Testing and Test tools’ (Dutch)

Capgemini NetherlandsTechnology, Consulting, Outsourcing150 dedicated testersAnd a lot moreOwn test courses


Measuring structure

TPITMM

SPICECMM


TPI

ScaleKey Area

0 1 2 3 4 5 6 7 8 9 10 11 12 13

1.Test strategy A B C D

2. Life cycle model A B

3. Moment of involvement A B C D

4. Estimating and planning A B C

5. Test specification techniques A B

6. Static test techniques A B

7. Metrics A B C D

8. Test tools A B C9. Test environment A B C

10. Office environment A

11. Commitment and motivation A B C

12. Test functions and training A B C

13. Scope of methodology A B C

14. Communication A B C

15. Reporting A B C D

16. Defect management A B C

17. Testware management A B C D

18. Test process management A B C

19. White-box tests A B C

20. Review A B


TMM

Level 5: Optimization, Defect Prevention andQuality Control

Level 4: Management and Measurement

Level 3: Integration

Level 2: Phase Definition

Level 1: Initial

- Test process optimization- Quality control- Application of process data for defect prevention

- Software quality evaluation- Test measurement program- Organization-wide review program

- Control test process- Integrate testing into the software lifecycle- Software test organization

- Basic testing techniques/ methods/ planning- Develop testing and debugging goals


The message is

First structure then tool


BUT, I do want to sleep while I amworking!

Like Garfield I like sleeping and Lasagna

Tools can do a lot more than I can do (quantity and quality)

Tools can do it faster and consistent

Repetitive work is boring; testing should be exiting


Moment to start with tooling

You know when …I want to be your coach, not your consultant

When Testing manually again and again is not possible anymoreIt is impossible to get an overview of the bugsYou want to do a volume test….

Do not just buy a tool!Prepare your organization for it!


Can tools help you structure

Sure!You can support chaos with tools

You can put it on the shelf and tell people you use it


Structure

More structure

Not structured


Example – Unit testing

Introduction of Junit or Robot

Improves the quality of the codeAssuming you make good test cases

Makes low level regression testing possible


Example - Static analysis

Automatic review of your codeManual reviews tend to be difficult

C and Java are popular

It reveals stupid mistakes that can save a lot of time in testing

Early testing, really helps

1 2 4 730

80

270

0

50

100

150

200

250

300

DS FO TO PT ST AC EX

(Böhm)


Quality up front

Static analysis and unit testing improve the code

More time for testing left overLess time needed for getting it working

Which gives time for more structure


Example - Defect management

Having an administrationCentralized, can be used by everybody

What information do you want to have?

Try to have one tool/database for the whole project/organisation


Example - Test design

Even with a tool the possibilities are numerousStandardized output is likely to achieve

Link to test execution and defect managementLink to requirements

Not every test technique fits in wellBoth manual and automatic testing with the same test design


Example - Capture/playback

Tools that first spring to mindWith these tools you should be able to ‘sleep’

Not easy to implement/maintainDon’t automate everything!

Why and why not/business case.Number of rerunsNumber of test casesExternal requirementsFull regression testLevel of change during application life cycle!


Over structure

You do not need a complete TPI compliant structured process

Otherwise you will never start

You do need some kind of business case/profits to be gained

External resources can help you out


Conclusion

Yes you can ….

Be careful

Do not over structureDo not wait too long, but take your time

Chaos can always happenReturn to an earlier step, when things go wrong

Do not blame the tool!


Sleep Sleep tighttightThink of me

Documents

First structure, then tool; but do not over structure€¦ · Level 5: Optimization, Defect Prevention and Quality Control Level 4: Management and Measurement Level 3: Integration