Age | Commit message (Collapse) | Author | Files | Lines |
|
- adapt existing framework to new testcases.yaml format (dependencies)
- simplify Tier management
- unblacklist juju_epc
- add new testcases
Change-Id: I085bff327f9eca856879616215dc6bae83435e7c
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|
|
* Add new testcases in Master (possible to black list for reporting if needed)
* use the version to get the list of testcases according to the version
Change-Id: I7999e66c18ebd73db896d0e27bde9a4a3d67f297
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|
|
if no order >= 2 tier exist, test case weather is not generated
if order >= 2 tier not the last one, test case weather will lose
the test cases which come after order >= 2 tier
Change-Id: Idb78926db773b161df1ba74f26429f5f6b764afb
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
as architecture is not considered as a constraints (unlike scenario or
installer) we need to work on the build tag to retrieve the data
but it is not possible to use regex directly in the API
so retrieveing the accurate results require extra processing
* based on build_tag, filter the results properly per scenario
* build a table build_tag time for a given scenario
* keep only the last 4 results
* evaluation criteria field
It would simplified if architecture could be declared as a constraint
then querying the resuls will not change and not require intermediate
steps
JIRA: FUNCTEST-880
Change-Id: Id4fe4f56babf0964d41e299905c804e0d837c3d7
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
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>
|
|
minor pylint fix in functest/reporting-status
Change-Id: Ibfd4f0da1475c34c40a3d9e00530f8f15eb3c7dc
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
+ minor fixes
* unknown => real test case names
* pylint corrections
Change-Id: I75446e4006d41fe1bb25106420910025afa01489
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
fix some pep8 errors in other projects
Change-Id: Iea68b0d495f7fbe892ec866fb70b8354ad9ff3c2
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
In fuel we may deal with x86 or aarch64 architecture
We generate dedicated reporting page
- fuel@x86
- fuel@aarch64
However when there is no results for one of the architecture
the test on the number of architecture lead to a bug
Change-Id: I9906bd6078c8493587dc667eb23399a1e8311e77
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Testing reporting provides
- static reporting pages [1] (jinja2)
- landing pages including test case catalogue [2] (angular)
It consumes the Test API to build web pages providing status for
the testing projects (so far functest, yardstick, storperf and
qtip).
Dockerization has been initiated [3]. The goal is to replace the
static page hosted on testresults.opnfv.org by a docker regenerated
and redeployed when reporting code is changed
But the docker and more generally the testing reporting directory
must be refactored to
- manage dependencies properly
- leverage tox (py27, docs, pylint, pep8)
This patch
- setups tox (py27, pep8, pylint, docs)
- integrate the requirement management
- fix pep8 errors
- introduce 1 dummy unit test
This patch does not
- fix pylint errors
- create any doc
[1]: http://testresults.opnfv.org/reporting2/display/index.html
[2]: http://testresults.opnfv.org/reporting2/reporting/index.html
[3]: https://gerrit.opnfv.org/gerrit/#/c/36735/
Change-Id: I4613de7ca7036d6c6bbb8f58ade492b1d673599b
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|