1x10 - qa engineer role in jira

1x10 QA Engineer Role in JIRA

Michał Kujałowiczmichal.kujalowicz@spartez.com

Poznań Testing and Quality Group - 23.01.2014

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

● Developers, Product Managers, Designers, QAs, Agile Team Leads

● Values

~ 50 000 Customers

OnDemand and Download

Tracker for teams building

awesome products

Now also supporting their customers

Developers, PM, UX Designer, QATeam of 15 people

Enterprise features Platform JIRA Importers Plugin

@

Agile teams in general

● Developers

● Developers, Manual testers, Automation

● Developers, Testers (manual + automation)

● Developers, QAAPPROVED

QA Engineer

TESTER

QUALITY ASSURANCE ENGINEER

QUALITY ASSISTANCE ENGINEER

to

QA

to

QA

1 x 10

● 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.

Who is doing the testing then?

MetaphorDEVS DEVELOPMENT PROCESS

CUSTOMER VALUE

SOFTWARE DEVELOPMENT

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

MetaphorTESTERS QASSISTANTS

Those other things

● Quality and risk thinking● Test tools, test environments● Customer insight

● Prevention, data-driven decisions, quality education

JIRA Deliveries

● Download○ 2-3 Major Releases per year○ Bugfix delivery every 2 weeks

● OnDemand○ New features + bugfixes every 2 weeks

Old world2, 3 times a year….before delivery…..

New worldevery 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

Implementation & Testing

Concurrent activities

Automated tests

Testing notes

All tests by orig. DEV

IMPL.&TEST

New story / feature

QA Demo

Not test session

Gain QA confidence

Assess if more tests are necessary

IMPL.&TEST

New story / feature

Result of QA Demo

Either Story DONE

Or Post-Dev Testing Notes

Or Bugfixing

IMPL.&TEST

DONE

New story / feature

DoTing

Developer on Testing

Tests which were not executed earlier

IMPL.&TEST

DONE

New story / feature

DONE!!!!IMPL.&TEST

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 Manager

User Service

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

● We have more and more customers

● Product is more and more complex

A try

Number of Critical and Blocker bugs coming from delivered products

Number new stories implemented

Yearly statistic

A try

1

2

3

4

5

1. Hire the best

2. Test Automation and CI

3. Values

4. Belief

5. Honesty

www.scrumalliance.org

Definition of D

one R

eference

- Stick to the DoD

“The feature must be this good before it’s good enough”

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

Think of becoming a QAssistant● Mindset

● Software testing experience

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

● Soft-skills● Code understanding, automation

● White-box, Grey-box testing

● BTCYS

Tests?

Questions?