Commit e2ff718
committed
Report all statuses to qaseio
Previously there was a logic like
> If test passed multiple times - store only first passed status
> But if test failed/skipped - store all such results
It was designed to be used with parametrized fixtures, when multiple pytest
items are related to single case from Qaseio.
But this approach doesn’t work with
https://github.com/pytest-dev/pytest-rerunfailures
When test passed after re-run, by previous logic it was still marked as
failed.
Updated logic forces developers to use single test for single case
and avoid parametrization for single case.1 parent 0329c44 commit e2ff718
2 files changed
Lines changed: 26 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
64 | 64 | | |
65 | 65 | | |
66 | 66 | | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
67 | 90 | | |
68 | 91 | | |
69 | 92 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
248 | 248 | | |
249 | 249 | | |
250 | 250 | | |
251 | | - | |
252 | 251 | | |
253 | | - | |
254 | | - | |
255 | | - | |
| 252 | + | |
| 253 | + | |
256 | 254 | | |
| 255 | + | |
257 | 256 | | |
258 | 257 | | |
259 | 258 | | |
| |||
0 commit comments