1×10 rola QA w tworzeniu Atlassian JIRA

63 %
38 %
Information about 1×10 rola QA w tworzeniu Atlassian JIRA
Technology

Published on February 14, 2014

Author: 3camp

Source: slideshare.net

Description

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

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 ● Developers, Product Managers, Designers, QAs, Agile Team Leads ● Values

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

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 + automation) ● Developers, QA PPR A VED O

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! ● Yes they can and should. They just need guidance how to do it.

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

Metaphor TESTERS 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 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 by orig. DEV

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 ● We have more and more customers ● Product is more and more complex

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

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

Tests?

Questions?

Add a comment

Related presentations

Related pages

1×10 rola QA w tworzeniu Atlassian JIRA on Vimeo

Michał Kujałowicz - Spartez - 1×10 rola QA w tworzeniu Atlassian JIRA ... Did you know? Upgrade your uploading by following our recommended video ...
Read more

Atlassian Jira | LinkedIn

View 37275 Atlassian Jira posts, ... I got requirement for Administrating "Atlassian JIRA" Atlassian tools in ... 1×10 rola QA w tworzeniu Atlassian JIRA ...
Read more

Atlassian Jira | LinkedIn

1×10 rola QA w tworzeniu Atlassian JIRA. 571 visualizaciones . H2Kinfosys. JIRA Introduction | JIRA Tutorial | Atlassian JIRA Training |... 586 ...
Read more

2013.10.26 – Szczecin – Targi Kariera IT | Praca Dla ...

PRELEKCJE: 1x10 - rola QA Engineer w tworzeniu Atlassian JIRA Formy ... 1×10 – rola QA Engineer w tworzeniu ... szansę zaistnienia w ...
Read more

Tech.3camp zaprasza do PPN-T - my3miasto.pl

Michał Kujałowicz – Spartez – 1×10 rola QA w tworzeniu Atlassian JIRA. Jakub Marchwicki – Young Digital Planet – Teorie poznawcze dla hackerów.
Read more

Networking IT już w sobotę w Szczecinie - my tam będziemy ...

1×10 – rola QA Engineer w tworzeniu Atlassian JIRA – Michał Kujałowicz. Inżynieria wymagań w metodykach zwinnych ...
Read more

Targi pracy | Praca Dla Absolwenta | Strona 2.

1×10 – rola QA Engineer w tworzeniu Atlassian JIRA; Formy współpracy z pracownikami i zleceniobiorcami z uwzględnieniem specyfiki branży IT;
Read more

Atlassian/jira | LinkedIn

View 37290 Atlassian/jira posts, presentations, ... Senior Atlassian Tools Administrator (JIRA, Confluence) at National Library of Medicine (via MSC)
Read more