Age | Commit message (Collapse) | Author | Files | Lines |
|
we were used to count the number of PASS of the last 4 runs
it works 80% of the cases
4 runs
4 OK => 3 points
3 OK => 3 points
2 OK => 2 points
1 OK => 1 point
0 => 0
it is different from the normal score calculation
4 OK => 3 points
3 OK => 2 points
2 OK => 2 points
1 OK => 1 point
0 => 0
Change-Id: Ib8df2c294e0036246176c181b7a7ac290ebea07e
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
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>
|
|
To keep consistent with other testing project,
yardstick should change criteria value from 'SUCCESS' to 'PASS'
Change-Id: I8d8779927a74749e7c43df4e55e1888c49cbbbaf
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Since scenario data do not have a field named architecture,
So I choose pod_name for now.
For example:
pod_name: arm-pod5
I assume that it is based arm architecture
Change-Id: I92159a5e08b1ed80701494483fd9922dbd459193
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
fix some pep8 errors in other projects
Change-Id: Iea68b0d495f7fbe892ec866fb70b8354ad9ff3c2
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>
|