say no to test automation

14
How good quality are your tests? Bart Szulc, JIRA QA

Upload: stowarzyszenie-jakosci-systemow-informatycznych-sjsi

Post on 14-Apr-2017

358 views

Category:

Software


0 download

TRANSCRIPT

Page 1: Say NO to Test Automation

How good quality are your tests?

Bart Szulc, JIRA QA

Page 3: Say NO to Test Automation
Page 4: Say NO to Test Automation

Areas to cover1. $$$2. class IntegrationTestCoverageResolverImpl {3. back to the future

How good quality are your tests

Page 5: Say NO to Test Automation

let’s talk business

Page 6: Say NO to Test Automation

ShriKant Vashishtha - Fair Use

Page 7: Say NO to Test Automation

Expectations1. Capable of assesing affected stakeholders2. Capable of assesing affected capabilities3. Capable of assesing business value impact

How good quality are your tests

4. Always up-to-date, including priorities5. Unambiguous, written in domain language

Page 8: Say NO to Test Automation

let’s talk code

Page 9: Say NO to Test Automation

João Araruna - CC BY-SA 4.0

Page 10: Say NO to Test Automation

Expectations

How good quality are your tests

1. Capable of assesing affected components2. Contracts for dependencies3. Good coverage4. Testing tests with mutants5. Properly prioritized6. Stable, Fast & Balanced7. Defined strategy

Page 11: Say NO to Test Automation

let’s talk future

Page 12: Say NO to Test Automation
Page 13: Say NO to Test Automation

Expectations

How good quality are your tests

1. How often do you run your tests?2. I’m asking about all of them3. How easy it is to determine the change that caused regression?4. Do you have defined goals and metrics?5. Do you analyse each component in isolation and the system as whole?6. Would you be able to select the minimal set of tests that should be executed?7. Do you mind how long it takes to execute your tests?

Page 14: Say NO to Test Automation

Thank you !