Age | Commit message (Collapse) | Author | Files | Lines |
|
It also removes relative (and incomplete) references which could be
defined in modules instead of this global configuration.
Change-Id: Ie20dc3547e49b6224aa8100cd380d37b87ece5a9
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Functest is no longer a git clone.
Change-Id: Ieaceacaa820e9a7a3c64e8c1fbd2a8a9321f234d
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It allows functest to be run directly from a zip file [1].
[1] https://setuptools.readthedocs.io/en/latest/setuptools.html#setting-the-zip-safe-flag
Change-Id: I596a71e8cf2bed6dd79655bd5beeb047876a188c
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
1. Remove get_db_url()
2. If TEST_DB_URL declared in env, update test_db_url in
config_functest.yaml file during env preparation
3. No matter TEST_DB_URL declared in env or not,
Result_DB = CONST.__getattribute__("results_test_db_url")
JIRA: FUNCTEST-763
Change-Id: I20da7ef98bbcc56731e0ff7061b05c1dde6cbfc3
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I6fa0f6f449270199cc4d5b2c88e171091bf92773
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It calculates via the full path of env.py.
Change-Id: Ief958833f5116cdb116d0153d85a0ae03063ec5c
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
Logs are only disabled when the unit tests are run from cmdline.
It allows running them via pytest_suite_runner.py and printing
their results to functest.log.
You should notice that the unit test must disable the logger of the
tested TestCase (e.g. testcase.TestCase.logger.disabled = 1). Otherwise
false logs will be printed in console.
Change-Id: Ic171e4575c8bab2e52db1897ae026b61a03b6247
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
After the introduction of is_successful method
in TestCase class, this is not needed anymore.
Change-Id: I70f6f9e10495601cd5443467347b97efe27b81a3
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
So far, the test cases are storing a string "PASS" "FAIL"
in the self.result variable.
The way the new framework works is with INT Values.
Change-Id: I45e8693327740faadd8254b21569adfb2cefa6c8
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
It also adds this support to its dependencies.
Change-Id: I0534f0c7b0e15a9ee89f522f314cf5200874454c
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It converts all criteria values to the corresponding percent in
functest/ci/testcases.yaml.
Result is expected to be equal or greater than criteria. If both are 0,
result is considered as false.
It is compatible with the old behavior but warns to update.
It will allow a safer remove.
It also fixes a bug in test_tempest to allow merging [1] and
tier_handler.py which required that type criteria was str.
[1] https://gerrit.opnfv.org/gerrit/#/c/27949/
Change-Id: Ib6edcfa3103b7d51b0bdc83119f1cea2a8be9fbc
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It mainly avoids mixing input and output.
Criteria is now an input set in functest/ci/testcases.yaml and then
must be passed as __init__() args (which will be proposed in an
additional change).
Then it also renames the related TestCase method to
check_result().
Change-Id: Ifc3c8e3ea6cde7e3edf7174bed4bf2bf0894e8e3
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Every feature/testcase now allows receiving the data defined in
testcases.yaml as args (name is renamed to case_name).
From the time being, only project and case names are handled. Next
pending patches will add criteria, cmd and repo to this list.
It keeps the default values for case names except for features which
will be aggregated into Feature.
Change-Id: Id742d100b8183d7f10894c24ae6879d1b2b60ac9
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
a first fix had been done
but the version was retrieved 2 times with the regex
this patch removes the second regex and re-use get_version
the associated unit tests has been removed because even
if the build_tag is badly formated, it will not prevent
the results to be pushed with version = unknown
JIRA: FUNCTEST-765
Change-Id: I2cbe8ba1dd7278c3f3510a47c667c433f65e00f8
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
- fix regex issue
- add unit test to cover weekly and dummy build tags
- remove useless logs
JIRA: FUNCTEST-765
Change-Id: I7a8d40b4662f4557cd080669da46fb1c32d2ad6d
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
So far DB url was retrieved from configuration file
If you want to use the CI chain (jenkins, testapi, test DB,
functest, ..) then you have a problem
calling functest will systematically point to the configuration
from the repo
Supporting env variable allow to avoid post processing in the
configuration file and as a consequence offer the possibility
to create a local DB to host local results
Change-Id: Ie64b8b265827d7f5724c7066a8c173de8cf012e2
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
when using Functest out of CI, such env variables may not be set
This shall not result in Error messages
JIRA: FUNCTEST-716
Change-Id: I86d2023145480dfa9c8d593ea274acbd9e431ef7
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: FUNCTEST-690
The detailed benefits are listed in the JIRA description.
1. Refactored the functest_logger to make use of configuration file
2. Avoided configuring the logging every time a logger is initialized
3. Applied separate logging configuration fo unit test by removing
saving log to file
Change-Id: I6e27eaba727ae6d704f0301f15359dc3ea7b2f97
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
It avoids creating a dummy functest.log for unit testing.
Change-Id: Ib163d5d58284822b1904444fb60b08e92ee0ab9b
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
JIRA: FUNCTEST-683
Change-Id: I181d98847b2ca94ce84a670239b8a958bfae44cd
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|