1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
|
%global _empty_manifest_terminate_build 0
Name: python-flaky-tests-detection
Version: 1.3.0
Release: 1
Summary: Github actions plugin to check flakiness of tests by calculating fliprates.
License: Apache License 2.0
URL: https://github.com/F-Secure/flaky-tests-detection
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/de/33/f6e1d27d107416507ba2259b290969eb5fe90650b6f5a19f5fae5147e708/flaky-tests-detection-1.3.0.tar.gz
BuildArch: noarch
Requires: python3-pandas
Requires: python3-junitparser
Requires: python3-seaborn
Requires: python3-matplotlib
Requires: python3-pytest
Requires: python3-pytest-cov
Requires: python3-black
Requires: python3-mypy
Requires: python3-semantic-release
%description
# Flaky tests detection
<center><img src="https://github.com/F-Secure/flaky-tests-detection/blob/master/docs/imgs/Flaky-test-detection.png" width="120px" height="120px"/></center>
Visualize tests whose state changes most often. During software development, it is often common that some tests start to randomly fail,
but finding those tests is a tedious and time consuming problem. Flaky tests detection solves that problem by processing historical xunit test
results and checks which tests changes state most often. Flaky tests detection is available as Github Action plugin and
[Python package](https://pypi.org/project/flaky-tests-detection/). For usage, see [example](https://github.com/F-Secure/flaky-test-ci)
at the `actions` page.
Implementation is based on ["Modeling and ranking flaky tests at Apple"](https://dl.acm.org/doi/10.1145/3377813.3381370) by Kowalczyk, Emily & Nair, Karan & Gao, Zebao & Silberstein, Leo & Long, Teng & Memon, Atif.
## Features
* Prints out top test names and their latest calculation window scores (normal fliprate and exponentially weighted moving average fliprate that take previous calculation windows into account).
* Calculation grouping options:
* `n` days.
* `n` runs.
* Heatmap visualization of the scores and history.
## Parameters
### Data options (choose one)
* `--test-history-csv`
* Give a path to a test history csv file which includes three fields: `timestamp`, `test_identifier` and `test_status`.
* `--junit-files`
* Give a path to a folder with `JUnit` test results.
### Calculation options
* `--grouping-option`
* `days` to use `n` days for fliprate calculation windows.
* `runs` to use `n` runs for fliprate calculation windows.
* `--window-size`
* Fliprate calculation window size `n`.
* `--window-count`
* History size for exponentially weighted moving average calculations.
* `--top-n`
* How many top highest scoring tests to print out.
### Heatmap generation
* `--heatmap`
* Turn heatmap generation on.
* Two pictures generated: normal fliprate and exponentially weighted moving average fliprate score.
* Same parameters used as with the printed statistics.
### Full examples
* Precomputed `test_history.csv` with daily calulations. 1 day windows, 7 day history and 5 tests printed out.
* `--test-history-csv=example_history/test_history.csv --grouping-option=days --window-size=1 --window-count=7 --top-n=5`
* `JUnit` files with calculations per 5 runs. 15 runs history and 5 tests printed out.
* `--junit-files=example_history/junit_files --grouping-option=runs --window-size=5 --window-count=3 --top-n=5`
* Precomputed `test_history.csv` with daily calculations and heatmap generation. 1 day windows, 7 day history and 50 tests printed and generated to heatmaps.
* `--test-history-csv=example_history/test_history.csv --grouping-option=days --window-size=1 --window-count=7 --top-n=50 --heatmap`
## Install module
* `make install`
## Install module and development packages
* `make install_dev`
## Run pytest
* `make run_test`
## Acknowledgement
The package was developed by [F-Secure Corporation][f-secure] and [University of Helsinki][hy] in the scope of [IVVES project][ivves]. This work was labelled by [ITEA3][itea3] and funded by local authorities under grant agreement “ITEA-2019-18022-IVVES”
[ivves]: http://ivves.eu/
[itea3]: https://itea3.org/
[f-secure]: https://www.f-secure.com/en
[hy]: https://www.helsinki.fi/en/computer-science
%package -n python3-flaky-tests-detection
Summary: Github actions plugin to check flakiness of tests by calculating fliprates.
Provides: python-flaky-tests-detection
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-flaky-tests-detection
# Flaky tests detection
<center><img src="https://github.com/F-Secure/flaky-tests-detection/blob/master/docs/imgs/Flaky-test-detection.png" width="120px" height="120px"/></center>
Visualize tests whose state changes most often. During software development, it is often common that some tests start to randomly fail,
but finding those tests is a tedious and time consuming problem. Flaky tests detection solves that problem by processing historical xunit test
results and checks which tests changes state most often. Flaky tests detection is available as Github Action plugin and
[Python package](https://pypi.org/project/flaky-tests-detection/). For usage, see [example](https://github.com/F-Secure/flaky-test-ci)
at the `actions` page.
Implementation is based on ["Modeling and ranking flaky tests at Apple"](https://dl.acm.org/doi/10.1145/3377813.3381370) by Kowalczyk, Emily & Nair, Karan & Gao, Zebao & Silberstein, Leo & Long, Teng & Memon, Atif.
## Features
* Prints out top test names and their latest calculation window scores (normal fliprate and exponentially weighted moving average fliprate that take previous calculation windows into account).
* Calculation grouping options:
* `n` days.
* `n` runs.
* Heatmap visualization of the scores and history.
## Parameters
### Data options (choose one)
* `--test-history-csv`
* Give a path to a test history csv file which includes three fields: `timestamp`, `test_identifier` and `test_status`.
* `--junit-files`
* Give a path to a folder with `JUnit` test results.
### Calculation options
* `--grouping-option`
* `days` to use `n` days for fliprate calculation windows.
* `runs` to use `n` runs for fliprate calculation windows.
* `--window-size`
* Fliprate calculation window size `n`.
* `--window-count`
* History size for exponentially weighted moving average calculations.
* `--top-n`
* How many top highest scoring tests to print out.
### Heatmap generation
* `--heatmap`
* Turn heatmap generation on.
* Two pictures generated: normal fliprate and exponentially weighted moving average fliprate score.
* Same parameters used as with the printed statistics.
### Full examples
* Precomputed `test_history.csv` with daily calulations. 1 day windows, 7 day history and 5 tests printed out.
* `--test-history-csv=example_history/test_history.csv --grouping-option=days --window-size=1 --window-count=7 --top-n=5`
* `JUnit` files with calculations per 5 runs. 15 runs history and 5 tests printed out.
* `--junit-files=example_history/junit_files --grouping-option=runs --window-size=5 --window-count=3 --top-n=5`
* Precomputed `test_history.csv` with daily calculations and heatmap generation. 1 day windows, 7 day history and 50 tests printed and generated to heatmaps.
* `--test-history-csv=example_history/test_history.csv --grouping-option=days --window-size=1 --window-count=7 --top-n=50 --heatmap`
## Install module
* `make install`
## Install module and development packages
* `make install_dev`
## Run pytest
* `make run_test`
## Acknowledgement
The package was developed by [F-Secure Corporation][f-secure] and [University of Helsinki][hy] in the scope of [IVVES project][ivves]. This work was labelled by [ITEA3][itea3] and funded by local authorities under grant agreement “ITEA-2019-18022-IVVES”
[ivves]: http://ivves.eu/
[itea3]: https://itea3.org/
[f-secure]: https://www.f-secure.com/en
[hy]: https://www.helsinki.fi/en/computer-science
%package help
Summary: Development documents and examples for flaky-tests-detection
Provides: python3-flaky-tests-detection-doc
%description help
# Flaky tests detection
<center><img src="https://github.com/F-Secure/flaky-tests-detection/blob/master/docs/imgs/Flaky-test-detection.png" width="120px" height="120px"/></center>
Visualize tests whose state changes most often. During software development, it is often common that some tests start to randomly fail,
but finding those tests is a tedious and time consuming problem. Flaky tests detection solves that problem by processing historical xunit test
results and checks which tests changes state most often. Flaky tests detection is available as Github Action plugin and
[Python package](https://pypi.org/project/flaky-tests-detection/). For usage, see [example](https://github.com/F-Secure/flaky-test-ci)
at the `actions` page.
Implementation is based on ["Modeling and ranking flaky tests at Apple"](https://dl.acm.org/doi/10.1145/3377813.3381370) by Kowalczyk, Emily & Nair, Karan & Gao, Zebao & Silberstein, Leo & Long, Teng & Memon, Atif.
## Features
* Prints out top test names and their latest calculation window scores (normal fliprate and exponentially weighted moving average fliprate that take previous calculation windows into account).
* Calculation grouping options:
* `n` days.
* `n` runs.
* Heatmap visualization of the scores and history.
## Parameters
### Data options (choose one)
* `--test-history-csv`
* Give a path to a test history csv file which includes three fields: `timestamp`, `test_identifier` and `test_status`.
* `--junit-files`
* Give a path to a folder with `JUnit` test results.
### Calculation options
* `--grouping-option`
* `days` to use `n` days for fliprate calculation windows.
* `runs` to use `n` runs for fliprate calculation windows.
* `--window-size`
* Fliprate calculation window size `n`.
* `--window-count`
* History size for exponentially weighted moving average calculations.
* `--top-n`
* How many top highest scoring tests to print out.
### Heatmap generation
* `--heatmap`
* Turn heatmap generation on.
* Two pictures generated: normal fliprate and exponentially weighted moving average fliprate score.
* Same parameters used as with the printed statistics.
### Full examples
* Precomputed `test_history.csv` with daily calulations. 1 day windows, 7 day history and 5 tests printed out.
* `--test-history-csv=example_history/test_history.csv --grouping-option=days --window-size=1 --window-count=7 --top-n=5`
* `JUnit` files with calculations per 5 runs. 15 runs history and 5 tests printed out.
* `--junit-files=example_history/junit_files --grouping-option=runs --window-size=5 --window-count=3 --top-n=5`
* Precomputed `test_history.csv` with daily calculations and heatmap generation. 1 day windows, 7 day history and 50 tests printed and generated to heatmaps.
* `--test-history-csv=example_history/test_history.csv --grouping-option=days --window-size=1 --window-count=7 --top-n=50 --heatmap`
## Install module
* `make install`
## Install module and development packages
* `make install_dev`
## Run pytest
* `make run_test`
## Acknowledgement
The package was developed by [F-Secure Corporation][f-secure] and [University of Helsinki][hy] in the scope of [IVVES project][ivves]. This work was labelled by [ITEA3][itea3] and funded by local authorities under grant agreement “ITEA-2019-18022-IVVES”
[ivves]: http://ivves.eu/
[itea3]: https://itea3.org/
[f-secure]: https://www.f-secure.com/en
[hy]: https://www.helsinki.fi/en/computer-science
%prep
%autosetup -n flaky-tests-detection-1.3.0
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-flaky-tests-detection -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Mon May 15 2023 Python_Bot <Python_Bot@openeuler.org> - 1.3.0-1
- Package Spec generated
|
