1. The document discusses a lean approach to quality assurance using automated testing, code reviews, and dogfooding rather than traditional QA. 2. It emphasizes the importance of automated testing, code reviews, strict branching workflows, and dogfooding code to catch bugs early. 3. Quality is baked in through practices like continuous integration, enforcing builds, and code reviews before merging code rather than relying primarily on separate QA teams.

1. Quality without QA
A lean approach to less bugs
Tim Pettersen • Developer Provocateur • Atlassian • @kannonboy

2. Facts
800+
Developers

3. :

4. Quality
Assurance
Assistance &
analysis

5. n. koâla tēa
Quality

6. AWARENESS
LEADS
PROSPECTS
SALES

7. AWARENESS
LEADS
PROSPECTS
SALES

8. DOGFOODING
MANUAL QA
buggy code your team writes
less buggy code that ships
AUTOMATED TESTS
CODE REVIEW
fast and
cheap
slow and/or
expensive

9. Baked In
Quality
Photo: Simon Law

10. feature/JIRA-123
stable master branch
isolated feature work
master
Branching workflow
Merge is blocked until..
1. CI builds passing?
2. At least 2 reviewers approved?
3. All rework complete?

11. atlassian.com/git
Want to get Git right?

12. Automated Tests

13. Comic: Randall Munroe http://xkcd.com/303/

14. Comic: Randall Munroe http://xkcd.com/303/
“I’m running the tests”

15. Types of Tests
junit
W
ebDriver
slowfast
run as pre-commit hook
qunit(headless)
checkstyle
“wired”junitREST
no product needed require a live product instance

16. automatically triggered
Building branches
maste
always build master

17. ~500Kbuilds per month

18. Testing with Git (webinar)
Sarah Goff-Dupont,
CI Extraordinaire
tinyurl.com/superci

19. Build enforcement

20. human judgement needed
?
“what-evs”
bad API decision
O(n!) algorithm
technical debt
Build enforcement

21. Code
Review
Photo: Yogi (Flickr)

22. Better
Code
Shared
Knowledge
Team
Ownership

23. G =
1
R+1
Developer guilt

24. Team
Ownership

25. Better
Code
Shared
Knowledge
Team
Ownership

26. Code reviews take
negative time

27. Reviews and releases
10
20
30
40
Daily Weekly Monthly Quarterly Yearly
Code Review No Code Review
Source: Atlassian Git Survey 2013

28. Tim’s
for
Pull
Requests
TOP
TEN
TIPS

29. 1. One issue, one pull request
= !

30. 2. Minimum TWO approvals before merge
3. Have 1.5x - 2.5x that number reviewers

31. 4. Use git blame / git guilt to find reviewers

32. 5. Avoid flamewars!
negotiate,
arbitrate
or
escalate

33. 6. Stuck in review?
Make Tuesday & Thursday inbox zero days

34. 7. @mention specialists

35. 8. Raise issues for TODOs
// TODO fix this hack
// TODO fix this (JRA-1773)

36. obvious
code
code
comments
PR
comments
> >
9. Move comments into code

37. 10. Build a team policy, as a team
…and enforce it!

38. DOGFOODING
MANUAL QA
AUTOMATED TESTS
CODE REVIEW

39. Dogfooding?

40. feature/JIRA-123
stable master branch
isolated feature work
master
Continuous
Deployment

41. Extreme Dogfooding

42. Dogfooding is
an important tool
to help you catch
regressions
You need both
Automated Tests
and Code Review
Git branching
greatly helps
isolation, stability
& testing

43. Quality
Assurance
Assistance &
analysis

44. So what does QA do?
• QA leadership
• Training
• Feature kick-offs
• Tooling
• Analysis

45. Analysis

46. Analysis

47. Tell me more about QA!
How the JIRA team keeps
quality at speed
tinyurl.com/jiraqa

48. Tim Pettersen • Developer Provocateur • Atlassian • @kannonboy
Thank you!