50
Adventures in QA Dirk Haun ACCU Conference 2010

Adventures in QA

Embed Size (px)

DESCRIPTION

Adventures of a developer who suddenly found himself in the role of head of QA. Presentation as held at ACCU 2010 (I think - had to recreate it from the last draft after I lost my laptop on the Eurostar in the ensuing volcanic chaos on the way back from Oxford).

Citation preview

Page 1: Adventures in QA

Adventures in QA

Dirk HaunACCU Conference 2010

Page 2: Adventures in QA

Prelude

Page 3: Adventures in QA

About me

• For the longest time: Developer in C, C++

• Surprise career move to QA

• Amateur in QA

Page 4: Adventures in QA

Company Profile

• Document conversion

• Large scale

• Highly portable C

• Some Java

Page 5: Adventures in QA

Important Features

• Performance

• Resources

• Quality

• Usability (in progress)

• not so much: Security

Page 6: Adventures in QA

Motivation

Page 7: Adventures in QA

"Das ging dochschon mal?!"

Page 8: Adventures in QA

"But this usedto work?!"

Page 9: Adventures in QA

My First Regression Test Suite

Page 10: Adventures in QA

Career

Page 13: Adventures in QA

The Job

Page 20: Adventures in QA

Infrastructure

Page 24: Adventures in QA

Intermission

Some feedback from my helpful audience

Page 25: Adventures in QA

Ideas from the Audience

• Partioning - find the essential tests

• Reduce release frequency for some of the platforms

• Try differential pricing per platform

Page 26: Adventures in QA

Ideas from the Audience

• Don‘t just set up rules (guidelines, directives), but explain why

• How do new people learn the rules? Try storytelling or mentoring

• Test the rules

Page 27: Adventures in QA

Ideas from the Audience

• Get stakeholders involved, e.g. customers

• Get an outsider‘s view, e.g. from a consultant

Page 28: Adventures in QA

Changes

Page 34: Adventures in QA

"Every new featureshould have a test"

Page 35: Adventures in QA

"This featurehas to be

in the next version"

Page 36: Adventures in QA

Continuous Integration

Page 37: Adventures in QA

Breaking the Build

• acting on failed tests

• figuring out who broke the build

• time-consuming

• whose responsibility is it?

• running the unit tests before committing

Page 40: Adventures in QA

Outlook

Page 42: Adventures in QA

Does everybody "get" it yet?

Page 44: Adventures in QA

(Some)Lessons Learned

Page 45: Adventures in QA

Test Communitiesdo exist

Page 46: Adventures in QA

Change takes time- a lot of time

Page 47: Adventures in QA

QA needs a"holistic" approach

Page 48: Adventures in QA

Test automation- The Holy Grail?

Page 49: Adventures in QA

The End?

Page 50: Adventures in QA

Credits

• Photos via flickr.com, thanks to: Hopkinsii, lotyloty, seier+seier, Alex Polezhaev, Horia Varlan, Caterina Fake, Steve Jurvetson, Stig Nygaard, Steve Punter, Peter Dutton, paul posadas, Erik Pitti, Nick J Webb, Bill Gantz, Jukka Zitting, Kevin Dooley, Jean-Pierre Dalbéra, Matti Mattila, Rebecca Krebs, mollybob, Matt Brown, Bob Bobster, James Bowe, Bhumika Guglani, manuki

• Photos and names are links - click them!