Age | Commit message (Collapse) | Author | Files | Lines |
|
Checking Return status code after each step can be wrapped by Exception
catching
Also, the return code is not as informative as exception
Change-Id: Ic15791d1b8ee47e10cbae8bad46a2cb90ac2b46e
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
Few bug fix in rally code along with unit tests.
Change-Id: Id39a5089ca6fce8aac5ba89eb61d31b02a5e9a98
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
the return shall only deal with test executed or not
it shall not return the criteria through a return statement
the criteria is managed with the criteria field
previous patch https://gerrit.opnfv.org/gerrit/#/c/27807
corrected the fact that we should not return the status of the test
which was preventing Failed results to be pushed
but it removed the return needed statement
JIRA: FUNCTEST-714
Change-Id: I3d4c609467837e4ce2353c67c0b8ea95e21ebd84
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: FUNCTEST-685
Change-Id: Id0d0bcf55451832d9aeb22c3e6b9c21aea4e0911
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
this problem was due to the fact that we add exit condition
EX_ERROR when the result was FAIL
EX_ERROR shall be used as exit condition when there is an
execution error, i.e the test case cannot be run
if it can be run, there is no execution error
the result can be PASS or FAIL, but from the CI, execution is OK
JIRA: FUNCTEST-714
Change-Id: Id434bb9aa88b50277c40c717259304f26f7b3966
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: FUNCTEST-541
Change-Id: Ife04f58dc31ca9ba6316cc31577f81a6bf0e0405
Signed-off-by: helenyao <yaohelan@huawei.com>
|