Automatically Detecting Flaky Tests Plan

2019-02-15

Load local surefire result to cache

End

Details

design

N

2019-02-20

Instantiate

1. Background2. Analisys 3. Solution

Figure 5 : Implement Details For Detecting The Flaky Test

Initial the ExecutionListener

@Override

plan

projectFailed

...

Y

2019-02-08

Finally

Build

Code change?

afterSessionStart

Flaky Tests Clue Provider

projectSucceeded

afterSessionEnd

Run unit tests

MavenLifecycleParticipant

1. Technology selection for the tool2. Development 3. System integration test

Requirement Analysis

Marked as flaky test and save in DB

Load local surefire result in cache

（Work Breakdown Structure）

Local has surefile record?

Start

Same test result?

Detect flaky tests

sessionStarted

afterProjectsRead

Pre-load

1. Collect relevant informatio2. Design technical proposal 3. Feasibility analysis

Build The Tool

Conceiving Feasibility Plan

Write The Report

2019-02-11

Clean the surefire result from cache

Figure 4 : Work Flow of the Flaky Tests Clue Provider

1. Purpose2. Target3. WBS

1.Check if the test class has code change from git2.Check if the test result same with the cache3.No code change + has history result + different test result then mark as flaky test

ExecutionListener