This document discusses the role of a QA Engineer in JIRA. It notes that the QA Engineer works with a team of 15 people including developers, product managers, UX designers, and other QAs. It emphasizes that with Agile development, testing is now a shared responsibility of developers rather than being isolated to testers. Developers are expected to write and execute both manual and automated tests as part of development. The document outlines the development and release process at JIRA, with major releases every 2-3 months and bugfix releases every 2 weeks for the on-demand product. It stresses testing early and often through the development cycle rather than relying on testing at the end. Automated regression tests run on every code change to prevent

1. 1x10
QA Engineer Role in JIRA

2. About me
●
In Software Quality / Testing
since 2005
●
Senior QA
●
JIRA Team
●
Quality validation enthusiast

3. ●
Partner
● Involved in development of core Atlassian
products
● Commercial, Open-Source add-ons,
customizations
● Developers, Product Managers, Designers,
QAs, Agile Team Leads
● Values

4. Download
d
emand an
OnD
~
50
00
0
Cu
sto
m
er
s
Now also supporting
their customers
ilding
u
ms b
a
for te ucts
r
acke e prod
Tr
esom
aw

5. Develo
f 15 peop
Team o
le
pers, P
M, UX D
esigner
, QA
@
Enterprise
features
Platform
JIRA Imp
orters Plu
gin

6. Agile teams in general
●
Developers
●
Developers, Manual testers, Automation
●
Developers, Testers (manual +
automation)
●
Developers, QA
PPR
A
VED
O

7. QA Engineer
TESTER
QUALITY ASSURANCE
ENGINEER
QUALITY ASSISTANCE
ENGINEER

8. QA
to

9. QA
1 x 10
to

10. Who is doing the testing then?
●
It is Developers’ responsibility.
Both manual and automatic.
What? Developers can’t test!
●
Yes they can and should.
They just need guidance how
to do it.

11. Metaphor
SOFTWARE DEVELOPMENT
DEVS
CUSTOMER VALUE
TECHNICAL DEBT, HACKS, FEATURES YOU DO NOT KNOW OF, ...
DEVELOPMENT PROCESS

12. Metaphor
TESTERS
QASSISTANTS

13. Those other things
● Quality and risk thinking
● Test tools, test environments
● Customer insight
● Prevention, data-driven decisions, quality
education

15. JIRA Deliveries
● Download
○ 2-3 Major Releases per year
○ Bugfix delivery every 2 weeks
● OnDemand
○ New features + bugfixes every 2 weeks

16. Old world
2, 3 times a year….
before delivery…..
New world
every two weeks ….
but later ….

17. Agile process
2 weeks

18. New story / feature
Story in sprint
backlog

19. New story / feature
Individual
preparation

20. New story / feature
Kick-off meeting
Pre-dev testing
notes
Prevention
Risk
identification

21. New story / feature
IMPL.
&
TEST
Implementation
& Testing
Concurrent
activities
Automated tests
Testing notes
All tests by orig.
DEV

22. New story / feature
IMPL.
&
TEST
QA Demo
Not test session
Gain QA
confidence
Assess if more
tests are
necessary

23. New story / feature
IMPL.
&
TEST
Result of QA
Demo
Either Story
DONE
Or Post-Dev
Testing Notes
Or Bugfixing
DONE

24. New story / feature
IMPL.
&
TEST
DoTing
Developer on
Testing
Tests which
were not
executed earlier
DONE

25. New story / feature
IMPL.
&
TEST
DONE
DONE
DONE!!!!

26. Test wisely
“Do not waste
my precious time
with meaningless tests”
Grey-box testing

27. Adding a user in JIRA
UI
Webwork Actions
User Service
User Manager
Database
REST Endpoint
?

28. Regression Tests Phase
● THERE IS NO!!!!!!
● All automated regression tests run on every
commit
● Soak period (dogfooding)

29. Automated Tests
● Unit Tests and QUnits
● Func Tests
● Webdriver Tests
● Visual Regression Tests

30. Eat your own dogfood!

31. Bullshit!
I have seen JIRA not working!
How to measure QAssistance effectiveness?
● Development team is bigger and bigger
● We have more and more customers
● Product is more and more complex

32. Quality process effectiveness
Number of Critical and Blocker bugs coming
from delivered products
Number new stories implemented
Yearly statistic

33. Quality process effectiveness

34. 5
4
3
2
1

35. 1. Hire the best

36. 2. Test Automation and CI

37. 3. Values

38. 4. Belief

39. 5. Honesty- Stick to the DoD
www.scrumalliance.org
Definition of Done
Reference
“The feature must be this good
before it’s good enough”

41. Think of having QAssistants
●
Team is interdisciplinary
●
Quality responsibility
●
Quality thinking of the complete team
●
Test automation right from scratch
●
QAs not stopping but increasing speed
●
No safety-net thinking

42. Think of becoming a QAssistant
●
Mindset
Solve symptoms, not problems
● Fix one bug, prevent class of bugs
●
●
Software testing experience
●
Soft-skills
●
Code understanding, automation
●
White-box, Grey-box testing
●
BTCYS

43. Tests?

44. Questions?