qa club kiev #17 measuring quality by volodymyr prymakov

97
Measuring Quality Release Readiness Criteria and Quality Reporting

Upload: qa-club-kiev

Post on 12-Jul-2015

2.520 views

Category:

Education


2 download

TRANSCRIPT

Page 1: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

Measuring QualityRelease Readiness Criteria and Quality Reporting

Page 2: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

22

11 Years general working experience in IT/QA (30+ projects)

----------

•QA Consultant at Ciklum Interactive

•QA Manager (Manual)

•Automated Testing Manager

•Load Testing Manager

•Project Manager

----------

•Hobbies: Job, Wife and 2 children, Sport

----------

Skype: vladimir.primakov

Linkedin: ua.linkedin.com/in/vladimirprimakov/

Email: [email protected]

Some Words About Me

Volodymyr Prymakov (Vladimir Primakov)

Page 3: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

33

The presentation will cover the following items:

• Release Readiness criteria as a part of a master test plan, their types and details. (~ 30 min)

• Release readiness criteria appliance and areas of influence. (~ 5 min)

• Quality report and quality metrics + their connection to release readiness criteria. (~ 15 min)

• Concluding release readiness. (~1 min)

• Questions (~ 10 min)

Presentation’s Structure

Presentation Plan

Page 4: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

44

Release Readiness Criteria as a part of Master Test Plan

Release Readiness Criteria

Master Test Plan

Page 5: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

55

Categories of Release Readiness Criteria

Analyzing Quality

(RESULTS)Catching Quality

(ACTIVITIES)

1. New Functionality Testing

2. Regression Testing

3. Test Environments Testing

4. Unit & Integration testing

5. Special Types of Testing

Page 6: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

66

Any Ideas?

Criteria for New Functionality Testing

Page 7: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

77

Short Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% Features of Any Priority

Detailed Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 8: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

88

Short Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% Features of Any Priority

Detailed Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 9: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

99

Short Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% Features of Any Priority

Detailed Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 10: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1010

Short Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% Features of Any Priority

Detailed Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 11: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1111

Short Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% Features of Any Priority

Detailed Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 12: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1212

Short Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% Features of Any Priority

Detailed Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 13: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1313

Short Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% Features of Any Priority

Detailed Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 14: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1414

Expanded Example

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High (Blocker/Critical)

Detailed Exploratory testing

100% 0%

Medium (Major) Detailed Exploratory testing

100% 0%

Low (Normal/Trivial) Happy path Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Page 15: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1515

Test Deepness

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High (Blocker/Critical)

Detailed Exploratory testing

100% 0%

Medium (Major) Detailed Exploratory testing

100% 0%

Low (Normal/Trivial) Happy path Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Test Deepness

Page 16: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1616

Test Deepness

Criteria for New Functionality Testing

TEST DEEPNESS / DETALIZATION

Test Case Based Thought Out Test

Detailed Exploratory Test

Happy Path Exploratory test

Smoke test

Nothing

Page 17: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1717

Test Coverage

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High (Blocker/Critical)

Detailed Exploratory testing

100% 0%

Medium (Major) Detailed Exploratory testing

100% 0%

Low (Normal/Trivial) Happy path Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Test Coverage

Page 18: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1818

Test Coverage

Criteria for New Functionality Testing

Test Coverage

Test Coverage is 71 %, But should be 100%

Page 19: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

1919

MaximumFail Rate %

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High (Blocker/Critical)

Detailed Exploratory testing

100% 0%

Medium (Major) Detailed Exploratory testing

100% 0%

Low (Normal/Trivial) Happy path Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Fail Rate %

Page 20: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2020

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

High (Blocker / Critical) 0 0 0 * *

Medium (Major) 0 0 0 * *

Low (Normal/Trivial) 0 0 * * *

PASS CRITERIA

*if too many bugs are in place for the functionality – the bugs number can be considered for any specific case separately

Page 21: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2121

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

High (Blocker / Critical) 0 0 0 * *

Medium (Major) 0 0 0 * *

Low (Normal/Trivial) 0 0 * * *

PASS CRITERIA

*if too many bugs are in place for the functionality – the bugs number can be considered for any specific case separately

Page 22: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2222

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

High (Blocker / Critical) 0 0 0 * *

Medium (Major) 0 0 0 * *

Low (Normal/Trivial) 0 0 * * *

PASS CRITERIA

*if too many bugs are in place for the functionality – the bugs number can be considered for any specific case separately

Page 23: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2323

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

High (Blocker / Critical) 0 0 0 * *

Medium (Major) 0 0 0 * *

Low (Normal/Trivial) 0 0 * * *

PASS CRITERIA

Page 24: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2424

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

Features of Any Priority 0 0 * * *

PASS CRITERIA (short and not so strict)

Page 25: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2525

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

Features of Any Priority 0 0 * * *

PASS CRITERIA (short and not so strict)

Status: FAIL RATE %

Blocked

Page 26: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2626

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

Features of Any Priority 0 0 * * *

PASS CRITERIA (short and not so strict)

Status: FAIL RATE %

Blocked

Failed Release Readiness Criteria

Page 27: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2727

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

Features of Any Priority 0 0 * * *

PASS CRITERIA (short and not so strict)

Status: FAIL RATE %

Blocked

Failed Release Readiness Criteria

Status: Pass Rate %

Failed With Acceptable Bugs

Page 28: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2828

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

Features of Any Priority 0 0 * * *

PASS CRITERIA (short and not so strict)

Status: FAIL RATE %

Blocked

Failed Release Readiness Criteria

Status: Pass Rate %

Failed With Acceptable Bugs

Page 29: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

2929

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

Features of Any Priority 0 0 * * *

PASS CRITERIA (short and not so strict)

Status: FAIL RATE %

Blocked

Failed Release Readiness Criteria

Status: Pass Rate %

Failed With Acceptable Bugs

Page 30: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3030

Fail Rate %

Criteria for New Functionality Testing

Functionality PriorityMaximum Allowable Bugs Number

(Story, Improvement, New Feature)

BlockerBugs

CriticalBugs

Major Bugs

Normal Bugs

Trivial Bugs

Features of Any Priority 0 0 * * *

PASS CRITERIA (short and not so strict)

Status: FAIL RATE %

Blocked

Failed Release Readiness Criteria

Status: Pass Rate %

Failed With Acceptable Bugs

Passed

Page 31: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3131

Fail Rate %

Criteria for New Functionality Testing

Test Coverage

Fail Rate is 29%, But should be 0%

Page 32: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3232

Test Environment Coverage

Criteria for New Functionality Testing

Test Environment Priority

Coverage of Test Environments

Tested Functionality Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High (Blocker/Critical)

Detailed Exploratory testing

100% 0%

Medium (Major) Detailed Exploratory testing

100% 0%

Low (Normal/Trivial) Happy path Exploratory testing

100% 0%

High 100% (all high priority test environments)

All priorities Happy path Exploratory testing

100% 0%

Medium Please See test environments related criteria

Low Please See test environments related criteria

Test Environments Coverage

Page 33: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3333

Test Environment Coverage

Criteria for New Functionality Testing

Test EnvironmentsType OS Browser/Device Resolution Priority

PC Win 7 Chrome 1920*1080 Highest

PC Win 8 (metro) IE 10 1920*1080

HighMac MacOS Firefox 1920*1080

iPad iOs7 iPad 4 2048*1536

Mac MacOS Safari 2880*1800

MediumPC Win 7 IE 11 1366*768

iPad iOs7 iPad 2 1024*768

PC Linux Firefox 1366*768Low

Page 34: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3434

Test Environment Coverage

Criteria for New Functionality Testing

Test EnvironmentsType OS Browser/Device Resolution Priority

PC Win 7 Chrome 1920*1080 Highest

PC Win 8 (metro) IE 10 1920*1080

HighMac MacOS Firefox 1920*1080

iPad iOs7 iPad 4 2048*1536

Mac MacOS Safari 2880*1800

MediumPC Win 7 IE 11 1366*768

iPad iOs7 iPad 2 1024*768

PC Linux Firefox 1366*768Low

There is only 1 highest

priority environment so the

coverage, which it gives for

the priority, is 100%.

Page 35: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3535

Test Environment Coverage

Criteria for New Functionality Testing

Test EnvironmentsType OS Browser/Device Resolution Priority

PC Win 7 Chrome 1920*1080 Highest

PC Win 8 (metro) IE 10 1920*1080

HighMac MacOS Firefox 1920*1080

iPad iOs7 iPad 4 2048*1536

Mac MacOS Safari 2880*1800

MediumPC Win 7 IE 11 1366*768

iPad iOs7 iPad 2 1024*768

PC Linux Firefox 1366*768Low

1 environment of 3 high priority

environments gives ~ 33% coverage.

All these environments together

gives 100% coverage for the priority.

Page 36: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3636

Test Environment Coverage - Example

Criteria for New Functionality Testing

Page 37: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3737

What Else?

Criteria for New Functionality Testing

Page 38: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3838

What Else?

Criteria for New Functionality Testing

Page 39: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

3939

DEFINTION OF DONE (EXAMPLE)

User story reviewed & adjusted correspondingly

Unit-test created and passed

Integration test created and passed

Pear review passed

UX-review passed

Manual Test Passed

End User Test Passed…

Definition of Done

Criteria for New Functionality Testing

Page 40: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4040

Criteria for Regression Testing

Page 41: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4141

Criteria for Regression Testing

Test Deepness

Page 42: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4242

Criteria for Regression Testing

Test Coverage

Test Deepness

Page 43: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4343

Criteria for Regression Testing

Test Coverage

Test Deepness

Fail Rate

Page 44: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4444

Criteria for Regression Testing

Test Coverage

Test Deepness

Fail Rate

Test Environments

Page 45: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4545

Example

Criteria for Regression Testing

Test Environment Priority

Coverage of Test Environments

Tested Scenario Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High Detailed Exploratory testing

100% 0%

Medium (That might be affected by recent product changes)

Happy path Exploratory testing

100% 0%

Other Medium Happy path Exploratory testing

50% 0%

High See test environments related criteria

Medium See test environments related criteria

Low See test environments related criteria

Page 46: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4646

Example

Criteria for Regression Testing

Test Environment Priority

Coverage of Test Environments

Tested Scenario Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High Detailed Exploratory testing

100% 0%

Medium (That might be affected by recent product changes)

Happy path Exploratory testing

100% 0%

Other Medium Happy path Exploratory testing

50% 0%

High See test environments related criteria

Medium See test environments related criteria

Low See test environments related criteria

Page 47: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4747

Example

Criteria for Regression Testing

Test Environment Priority

Coverage of Test Environments

Tested Scenario Priority

Minimum Test Deepness

Minimum Functionality Coverage

MaximumFail Rate %

The Highest one 100% High Detailed Exploratory testing

100% 0%

Medium (That might be affected by recent product changes)

Happy path Exploratory testing

100% 0%

Other Medium Happy path Exploratory testing

50% 0%

High See test environments related criteria

Medium See test environments related criteria

Low See test environments related criteria

Page 48: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4848

Criteria for Test Environment TestingPossible Test Environment Ingredients

Internet Speed Antivirus, Firewalls

Plugins

Integration with other

applications and API

User Rights

RuntimesExternal Devices

Screen Resolutions and Modes

Hardware and Software Platforms and Modes

Web-browsers

Mobile Software Platforms

Mobile Software Platforms

External Libraries

Hardware

Characteristics and

Capacity

Robots (HD,

Software,

Capabilities)

Page 49: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

4949

Criteria for Test Environment Testing

Product-wide Test Deepness

Page 50: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5050

Criteria for Test Environment Testing

Product-wide Test

Deepness

Full Regression

Full Regression for

functionality of certain

priority

Main product Flows test /

User Acceptance Test /

Cover test

Selective Regression

Smoke Test

Page 51: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5151

Criteria for Test Environment Testing

Coverage of

Test Environments

Product-wide Test Deepness

Page 52: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5252

Criteria for Test Environment Testing

Coverage of

Test Environments

Product-wide Test Deepness

Fail Rate

Page 53: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5353

Criteria for Test Environment Testing

Test Environment Priority Target (functionality) Minimum Test Deepness

Minimum Coverage of Test environments

MaximumFail Rate %

Highest Please see the release readiness-criteria for new functionality and oldfunctionality

High New functionality Please see release readiness-criteria for newfunctionality

Old (Regression-related) functionality

Selective Regression and/or Main product Flows test

100% 0%

Medium New and Old (Regression-related) functionality

Product-wide Smoke test

75%* 0%

Low New and Old (Regression-related) functionality

Product-wide Smoke test

50%* 0%

Example

*Not covered environments may be covered next release and so on

Page 54: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5454

Criteria for Test Environment Testing

Test Environment Priority Target (functionality) Minimum Test Deepness

Minimum Coverage of Test environments

MaximumFail Rate %

Highest Please see the release readiness-criteria for new functionality and oldfunctionality

High New functionality Please see release readiness-criteria for newfunctionality

Old (Regression-related) functionality

Selective Regression and/or Main product Flows test

100% 0%

Medium New and Old (Regression-related) functionality

Product-wide Smoke test

75%* 0%

Low New and Old (Regression-related) functionality

Product-wide Smoke test

50%* 0%

Example

*Not covered environments may be covered next release and so on

Page 55: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5555

Criteria for Test Environment Testing

Test Environment Priority Target (functionality) Minimum Test Deepness

Minimum Coverage of Test environments

MaximumFail Rate %

Highest Please see the release readiness-criteria for new functionality and oldfunctionality

High New functionality Please see release readiness-criteria for newfunctionality

Old (Regression-related) functionality

Selective Regression and/or Main product Flows test

100% 0%

Medium New and Old (Regression-related) functionality

Product-wide Smoke test

75%* 0%

Low New and Old (Regression-related) functionality

Product-wide Smoke test

50%* 0%

Example

*Not covered environments may be covered next release and so on

Page 56: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5656

Criteria for Unit & Integration Testing

Test Coverage

Fail RateGUI-LESS

Functionality

GUI

Functionality*

Unit & Integration Testing

Test Coverage

Fail Rate

*Criteria may be not so strict, because GUI functionality can be also manually tested

Page 57: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5757

Criteria for Unit & Integration TestingExample

Integration Testing or Unit-TestingPriority of functionality

Minimum Functionality Coverage

MaximumFailRate %

High 100% 0%*

Medium 0% 0%*

*Depends on severity of the problems found in

integration/unit testing

Page 58: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5858

Criteria for Special Types of testing

Type of testing* Sufficient?

(yes/no)

Passed? Conclusions

Load/Performance

testing (client/server

side)

NOT READY

Security Testing NOT READY

UX-Testing READY

(Accessibility Testing) NOT READY

GENERAL CONCLUSSION: NOT READY

* Usually has separate release readiness criteria, but in any case it should be sufficient

and passed.

Special types of testing, which are obligatory to be conducted and passed

Page 59: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

5959

Release readiness criteria appliance and areas of influence

Page 60: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6060

Release readiness criteria appliance and areas of influence

Release readiness criteria

Defines testing activities and product quality sufficient for release

Influences testing strategy, testing approaches, and activities needed

Defines QA Resources requirements

Defines Quality reporting structure and content

Helps making conclusion about release readiness

Page 61: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6161

Page 62: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6262

For those who don’t sleep yet

thank you for being cheerful!

Page 63: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6363

Quality Reporting and its connection to release readiness criteria

Quality Reporting

Page 64: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6464

1. Number of Bugs and their severity

2. New Functionality Testing & Results

3. Regression Testing & Results

4. Test Environments Testing & Results

5. Unit & Integration testing & Results

6. Special Types of Testing & Results

7. Concluding Release Readiness

Quality Report Structure

Quality Reporting

Page 65: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6565

1. Number of Bugs and their severity

2. New Functionality Testing & Results

3. Regression Testing & Results

4. Test Environments Testing & Results

5. Unit & Integration testing & Results

6. Special Types of Testing & Results

7. Concluding Release Readiness

Quality Report Structure

Quality Reporting

Page 66: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6666

All Not Closed Bugs

Number of Bugs and their severity

Page 67: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6767

All Not Closed Bugs

Number of Bugs and their severity

Page 68: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6868

All Not Closed Bugs – By Component

Number of Bugs and their severity

Page 69: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

6969

All Not Closed Bugs – Not-Assigned to any Sprint

Number of Bugs and their severity

Page 70: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7070

Number of Bugs and their severityAll Not Closed Bugs – Not-Assigned to any Sprint

Page 71: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7171

Bugs List (for All not-closed bugs) – That fails release readiness criteria

Number of Bugs and their severity

Bugs List (for All not-closed bugs) – That fails release readiness criteria

Assigned to sprints

Not-Assigned to sprints

Page 72: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7272

Number of Bugs and their severity

Make a separate release readiness conclusion for this criterion type

Page 73: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7373

New Functionality Statuses (From Tasks Management System)

New Functionality Testing & Results

Features Statuses (Current release)

Page 74: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7474

New Functionality Statuses (From Tasks Management System)

New Functionality Testing & Results

Features Statuses (Current release)

Not-Resolved Features By Components(Current release)

Page 75: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7575

New Functionality Statuses (From Tasks Management System)

New Functionality Testing & Results

1

Test Environments

Page 76: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7676

New Functionality Statuses (From Tasks Management System)

New Functionality Testing & Results

1

2

Page 77: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7777

New Functionality Statuses (From Tasks Management System)

New Functionality Testing & Results

1

2

3

Page 78: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7878

New Functionality Statuses (From Tasks Management System)

New Functionality Testing & Results

1

2

3

4

Page 79: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

7979

New Functionality Statuses (From Tasks Management System)

New Functionality Testing & Results

1

2

3

4

Failed Functionalities Details (Optionally)

Page 80: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8080

New Functionality Testing & Results

Make a separate release readiness conclusion for this criterion type

Page 81: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8181

Regression testing results for the highest priority environment

Regression Testing & Results

By Components

Page 82: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8282

Regression testing results for the highest priority environment

Regression Testing & Results

Failed Functionalities Details (Optionally)

Page 83: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8383

Regression Testing & Results

Make a separate release readiness conclusion for this criterion type

Page 84: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8484

Test Environments Testing & Results

Test plans for test environments of different priorities

Page 85: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8585

Test Environments Testing & Results

Make a separate release readiness conclusion for this criterion type

Page 86: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8686

GUI-less functionality

Unit & Integration testing & Results

Type of testing Coverage Fail Percentage Conclusions

Unit-test 50% 0% READY

Integration test 100% 0% READY

GENERAL RELEASE READINESS CONCLUSSION: READY

Page 87: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8787

GUI-less functionality

Unit & Integration testing & Results

Type of testing Coverage Fail Percentage Conclusions

Unit-test 50% 0% READY

Integration test 100% 0% READY

GENERAL RELEASE READINESS CONCLUSSION: READY

Page 88: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8888

GUI-less functionality

Unit & Integration testing & Results

Type of testing Coverage Fail Percentage Conclusions

Unit-test 50% 0% READY

Integration test 100% 0% READY

GENERAL RELEASE READINESS CONCLUSSION: READY

Page 89: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

8989

GUI-less functionality

Unit & Integration testing & Results

Type of testing Coverage Fail Percentage Conclusions

Unit-test 50% 0% READY

Integration test 100% 0% READY

GENERAL RELEASE READINESS CONCLUSSION: READY

Page 90: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9090

Special Types of Testing & Results

Type of testing* Sufficient?

(yes/no)

Passed? Conclusions

Load/Performance

testing (client/server

side)

NOT READY

Security Testing NOT READY

UX-Testing READY

(Accessibility Testing) NOT READY

GENERAL RELEASE READINESS CONCLUSSION: NOT READY

* Usually has separate release readiness criteria, but in any case it should be sufficient

and passed.

Page 91: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9191

Special Types of Testing & Results

Type of testing* Sufficient?

(yes/no)

Passed? Conclusions

Load/Performance

testing (client/server

side)

NOT READY

Security Testing NOT READY

UX-Testing READY

(Accessibility Testing) NOT READY

GENERAL RELEASE READINESS CONCLUSSION: NOT READY

* Usually has separate release readiness criteria, but in any case it should be sufficient

and passed.

Page 92: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9292

Special Types of Testing & Results

Type of testing* Sufficient?

(yes/no)

Passed? Conclusions

Load/Performance

testing (client/server

side)

NOT READY

Security Testing NOT READY

UX-Testing READY

(Accessibility Testing) NOT READY

GENERAL RELEASE READINESS CONCLUSSION: NOT READY

* Usually has separate release readiness criteria, but in any case it should be sufficient

and passed.

Page 93: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9393

Special Types of Testing & Results

Type of testing* Sufficient?

(yes/no)

Passed? Conclusions

Load/Performance

testing (client/server

side)

NOT READY

Security Testing NOT READY

UX-Testing READY

(Accessibility Testing) NOT READY

GENERAL RELEASE READINESS CONCLUSSION: NOT READY

* Usually has separate release readiness criteria, but in any case it should be sufficient

and passed.

Page 94: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9494

Concluding Release Readiness

Criterion Status

1. Number of Bugs and their severityNOT READY

2. New Functionality Testing & ResultsREADY

3. Regression Testing & ResultsREADY

4. Test Environments Testing & ResultsNOT READY

5. Unit & Integration testing & ResultsREADY

6. Special Types of Testing & ResultsNOT READY

GENERAL CONCLUSSION: NOT READY

Page 95: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9595

Concluding Release Readiness

Criterion Status

1. Number of Bugs and their severityNOT READY

2. New Functionality Testing & ResultsREADY

3. Regression Testing & ResultsREADY

4. Test Environments Testing & ResultsNOT READY

5. Unit & Integration testing & ResultsREADY

6. Special Types of Testing & ResultsNOT READY

GENERAL CONCLUSSION: NOT READY

Page 96: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9696

Instruments Facilitating Quality Reporting

CSV

CSV

As Gadgets, iFrames,

Screenshots, Links

plugins

Page 97: QA Club Kiev #17 Measuring quality by Volodymyr Prymakov

9797

Thank you! ;)

QUESTIONS?