diff options
| author |   Morgan Richomme <morgan.richomme@orange.com> | 2017-10-09 05:45:30 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@opnfv.org> | 2017-10-09 05:45:30 +0000 |
| commit | 8cfad846a7393e63dae25e0f02ad08a242c2ffbd (patch) | |
| tree | 087f62af67c54009d1e30a4568d5e03661cfa326 /docs/images/reporting_danube_page.png | |
| parent | 5990c83bc1f8cca40469d231a0929ba39490bf01 (diff) | |
Update git submodules
* Update docs/submodules/releng from branch 'master'
- Merge "Change score calculation for functest reporting"
- Change score calculation for functest reporting
the goal is not to penalize scenario with few iteration due to
CI pipeline constraints
until now the top score was calculated on the base on 4 iterations, it means
whatever the number of iterations, we always consider the possible top score
based on at least 4 iterations
each case can get
- 3 points (last 4 iterations PASS)
- 2 points (more than 1 PASS over the last 10 days but 1 FAIL of the last 4)
- 1 point (at least 1 PASS over the last 10 days)
- no point (never work)
so if we consider a scenario with 10 cases, the top score is
30 = 10*3 (max points)
the coefficient to calculate the top score is not the number of iterations
- 1 iteration => possible top score 10
- 2 iterations => top score 20
- 3 iterations => top score 20
- 4 or more iterations => top score 30
previously top score was systematically 30
https://wiki.opnfv.org/plugins/servlet/mobile#content/view/6828617
Change-Id: I01102bc00766b7f5b58e73befa7d5328fcc895cc
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
Diffstat (limited to 'docs/images/reporting_danube_page.png')
0 files changed, 0 insertions, 0 deletions