1x10
QA Engineer Role in JIRA
About me
●

In Software Quality / Testing
since 2005

●

Senior QA

●

JIRA Team

●

Quality validation enthusiast
●

Partner

● Involved in development of core Atlassian
products
● Commercial, Open-Source add-ons,
customizations
● Devel...
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
...
Develo
f 15 peop
Team o

le

pers, P
M, UX D
esigner

, QA

@
Enterprise

features

Platform

JIRA Imp

orters Plu

gin
Agile teams in general
●

Developers

●

Developers, Manual testers, Automation

●

Developers, Testers (manual +
automati...
QA Engineer

TESTER
QUALITY ASSURANCE
ENGINEER
QUALITY ASSISTANCE
ENGINEER
QA

to
QA

1 x 10
to
Who is doing the testing then?
●

It is Developers’ responsibility.
Both manual and automatic.
What? Developers can’t test...
Metaphor
SOFTWARE DEVELOPMENT

DEVS

CUSTOMER VALUE

TECHNICAL DEBT, HACKS, FEATURES YOU DO NOT KNOW OF, ...

DEVELOPMENT ...
Metaphor
TESTERS

QASSISTANTS
Those other things
● Quality and risk thinking
● Test tools, test environments
● Customer insight
● Prevention, data-drive...
JIRA Deliveries
● Download
○ 2-3 Major Releases per year
○ Bugfix delivery every 2 weeks

● OnDemand
○ New features + bugf...
Old world
2, 3 times a year….
before delivery…..

New world
every two weeks ….

but later ….
Agile process

2 weeks
New story / feature

Story in sprint
backlog
New story / feature

Individual
preparation
New story / feature

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

IMPL.
&
TEST

Implementation
& Testing
Concurrent
activities
Automated tests
Testing notes
All tests ...
New story / feature

IMPL.
&
TEST

QA Demo
Not test session
Gain QA
confidence
Assess if more
tests are
necessary
New story / feature

IMPL.
&
TEST

Result of QA
Demo
Either Story
DONE
Or Post-Dev
Testing Notes
Or Bugfixing

DONE
New story / feature

IMPL.
&
TEST

DoTing
Developer on
Testing
Tests which
were not
executed earlier

DONE
New story / feature

IMPL.
&
TEST

DONE

DONE

DONE!!!!
Test wisely

“Do not waste
my precious time
with meaningless tests”

Grey-box testing
Adding a user in JIRA
UI

Webwork Actions

User Service

User Manager

Database

REST Endpoint

?
Regression Tests Phase
● THERE IS NO!!!!!!
● All automated regression tests run on every
commit
● Soak period (dogfooding)
Automated Tests
● Unit Tests and QUnits
● Func Tests
● Webdriver Tests
● Visual Regression Tests
Eat your own dogfood!
Bullshit!
I have seen JIRA not working!
How to measure QAssistance effectiveness?
● Development team is bigger and bigger
...
Quality process effectiveness
Number of Critical and Blocker bugs coming
from delivered products

Number new stories imple...
Quality process effectiveness
5
4
3
2
1
1. Hire the best
2. Test Automation and CI
3. Values
4. Belief
5. Honesty- Stick to the DoD

www.scrumalliance.org

Definition of Done
Reference

“The feature must be this good
before i...
Think of having QAssistants
●

Team is interdisciplinary

●

Quality responsibility

●

Quality thinking of the complete t...
Think of becoming a QAssistant
●

Mindset
Solve symptoms, not problems
● Fix one bug, prevent class of bugs
●

●

Software...
Tests?
Questions?
 1×10 rola QA w tworzeniu Atlassian JIRA
 1×10 rola QA w tworzeniu Atlassian JIRA
Upcoming SlideShare
Loading in …5
×

1×10 rola QA w tworzeniu Atlassian JIRA

906 views

Published on

Michał Kujałowicz - Spartez - 1×10 rola QA w tworzeniu Atlassian JIRA

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
906
On SlideShare
0
From Embeds
0
Number of Embeds
82
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

1×10 rola QA w tworzeniu Atlassian JIRA

  1. 1. 1x10 QA Engineer Role in JIRA
  2. 2. About me ● In Software Quality / Testing since 2005 ● Senior QA ● JIRA Team ● Quality validation enthusiast
  3. 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. 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. 5. Develo f 15 peop Team o le pers, P M, UX D esigner , QA @ Enterprise features Platform JIRA Imp orters Plu gin
  6. 6. Agile teams in general ● Developers ● Developers, Manual testers, Automation ● Developers, Testers (manual + automation) ● Developers, QA PPR A VED O
  7. 7. QA Engineer TESTER QUALITY ASSURANCE ENGINEER QUALITY ASSISTANCE ENGINEER
  8. 8. QA to
  9. 9. QA 1 x 10 to
  10. 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. 11. Metaphor SOFTWARE DEVELOPMENT DEVS CUSTOMER VALUE TECHNICAL DEBT, HACKS, FEATURES YOU DO NOT KNOW OF, ... DEVELOPMENT PROCESS
  12. 12. Metaphor TESTERS QASSISTANTS
  13. 13. Those other things ● Quality and risk thinking ● Test tools, test environments ● Customer insight ● Prevention, data-driven decisions, quality education
  14. 14. JIRA Deliveries ● Download ○ 2-3 Major Releases per year ○ Bugfix delivery every 2 weeks ● OnDemand ○ New features + bugfixes every 2 weeks
  15. 15. Old world 2, 3 times a year…. before delivery….. New world every two weeks …. but later ….
  16. 16. Agile process 2 weeks
  17. 17. New story / feature Story in sprint backlog
  18. 18. New story / feature Individual preparation
  19. 19. New story / feature Kick-off meeting Pre-dev testing notes Prevention Risk identification
  20. 20. New story / feature IMPL. & TEST Implementation & Testing Concurrent activities Automated tests Testing notes All tests by orig. DEV
  21. 21. New story / feature IMPL. & TEST QA Demo Not test session Gain QA confidence Assess if more tests are necessary
  22. 22. New story / feature IMPL. & TEST Result of QA Demo Either Story DONE Or Post-Dev Testing Notes Or Bugfixing DONE
  23. 23. New story / feature IMPL. & TEST DoTing Developer on Testing Tests which were not executed earlier DONE
  24. 24. New story / feature IMPL. & TEST DONE DONE DONE!!!!
  25. 25. Test wisely “Do not waste my precious time with meaningless tests” Grey-box testing
  26. 26. Adding a user in JIRA UI Webwork Actions User Service User Manager Database REST Endpoint ?
  27. 27. Regression Tests Phase ● THERE IS NO!!!!!! ● All automated regression tests run on every commit ● Soak period (dogfooding)
  28. 28. Automated Tests ● Unit Tests and QUnits ● Func Tests ● Webdriver Tests ● Visual Regression Tests
  29. 29. Eat your own dogfood!
  30. 30. 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
  31. 31. Quality process effectiveness Number of Critical and Blocker bugs coming from delivered products Number new stories implemented Yearly statistic
  32. 32. Quality process effectiveness
  33. 33. 5 4 3 2 1
  34. 34. 1. Hire the best
  35. 35. 2. Test Automation and CI
  36. 36. 3. Values
  37. 37. 4. Belief
  38. 38. 5. Honesty- Stick to the DoD www.scrumalliance.org Definition of Done Reference “The feature must be this good before it’s good enough”
  39. 39. 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
  40. 40. 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
  41. 41. Tests?
  42. 42. Questions?

×