1 ******************************
2 OPNFV FUNCTEST developer guide
3 ******************************
14 Functest is a project dealing with functional testing.
15 Functest produces its own internal test cases but can also be considered
16 as a framework to support feature project testing.
17 Functest developed a test API and defined a test collection framework
18 that can be used by any OPNFV project.
20 Therefore there are many ways to contribute to Functest. You can:
22 * Develop new internal test cases
23 * Integrate the tests from your feature project
24 * Develop the framework to ease the integration of external test cases
25 * Develop the API / Test collection framework
26 * Develop dashboards or automatic reporting portals
28 This document describes how, as a developer, you may interact with the
29 Functest project. The first section details the main working areas of
30 the project. The Second part is a list of "How to" to help you to join
31 the Functest family whatever your field of interest is.
34 ========================
35 Functest developer areas
36 ========================
39 Functest High level architecture
40 ================================
42 Functest is project delivering a test container dedicated to OPNFV.
43 It includes the tools, the scripts and the test scenarios.
45 Functest can be described as follow::
47 +----------------------+
49 | +--------------+ | +-------------------+
51 | | Tools | +------------------+ OPNFV |
52 | | Scripts | | | System Under Test |
53 | | Scenarios | +------------------+ |
54 | | | | Management | |
55 | +--------------+ | +-------------------+
59 +----------------------+
61 Functest internal test cases
62 ============================
63 The internal test cases in Colorado are:
69 * tempest_smoke_serial
71 * tempest_full_parallel
75 By internal, we mean that this particular test cases have been
76 developped and/or integrated by functest contributors and the associated
77 code is hosted in the Functest repository.
78 An internal case can be fully developped or a simple integration of
79 upstream suites (e.g. Tempest/Rally developped in OpenStack are just
80 integrated in Functest).
81 The structure of this repository is detailed in `[1]`_.
82 The main internal test cases are in the testcases subfolder of the
83 repository, the internal test cases are:
85 * Controllers: odl, onos, ocl
86 * OpenStack: healthcheck, vping_ssh, vping_userdata, tempest_*, rally_*
89 If you want to create a new test case you will have to create a new
90 folder under the testcases directory.
92 Functest external test cases
93 ============================
94 The external test cases are inherited from other OPNFV projects,
95 especially the feature projects.
97 The external test cases are:
113 Note that security_scan has been bootstraped in Functest but is
114 considered as an external test case as it gets its own repository.
116 The code to run these test cases may be directly in the repository of
117 the project. We have also a **features** sub directory under testcases
118 directory that may be used (it can be usefull if you want to reuse
125 Functest can be considered as a framework.
126 Functest is release as a docker file, including tools, scripts and a CLI
127 to prepare the environement and run tests.
128 It simplifies the integration of external test suites in CI pipeline
129 and provide commodity tools to collect and display results.
131 Since Colorado, test categories also known as tiers have been created to
132 group similar tests, provide consistant sub-lists and at the end optimize
133 test duration for CI (see How To section).
135 see http://artifacts.opnfv.org/functest/docs/userguide/index.html for
139 Test collection framework
140 =========================
142 The OPNFV testing group created a test collection database to collect
143 the test results from CI:
146 http://testresults.opnfv.org/test/swagger/spec.html
148 Authentication: opnfv/api@opnfv
150 Any test project running on any lab integrated in CI can push the
151 results to this database.
152 This database can be used to see the evolution of the tests and compare
153 the results versus the installers, the scenarios or the labs.
158 The Test result management can be summarized as follows::
160 +-------------+ +-------------+ +-------------+
162 | Test | | Test | | Test |
163 | Project #1 | | Project #2 | | Project #N |
165 +-------------+ +-------------+ +-------------+
168 +-----------------------------------------+
170 | Test Rest API front end |
171 | http://testresults.opnfv.org/test |
173 +-----------------------------------------+
176 | +-------------------------+
178 | | Test Results DB |
181 | +-------------------------+
184 +----------------------+
188 +----------------------+
192 The Test API is used to declare pods, projects, test cases and test
193 results. Pods are the pods used to run the tests.
194 The results pushed in the database are related to pods, projects and
195 cases. If you try to push results of test done on non referenced pod,
196 the API will return an error message.
198 An additional method dashboard has been added to post-process
199 the raw results in release Brahmaputra (deprecated in Colorado).
201 The data model is very basic, 4 objects are created:
212 "details": <URL description of the POD>,
213 "creation_date": "YYYY-MM-DD HH:MM:SS",
214 "name": <The POD Name>,
215 "mode": <metal or virtual>,
216 "role": <ci-pod or community-pod or single-node>
223 "name": <Name of the Project>,
224 "creation_date": "YYYY-MM-DD HH:MM:SS",
225 "description": <Short description>
232 "name":<Name of the test case>,
233 "project_name":<Name of belonged project>,
234 "creation_date": "YYYY-MM-DD HH:MM:SS",
235 "description": <short description>,
236 "url":<URL for longer description>
243 "case_name": <Reference to the test case>,
244 "project_name": <Reference to project>,
245 "pod_name": <Reference to POD where the test was executed>,
246 "installer": <Installer Apex or Compass or Fuel or Joid>,
247 "version": <master or Colorado or Brahmaputra>,
248 "start_date": "YYYY-MM-DD HH:MM:SS",
249 "stop_date": "YYYY-MM-DD HH:MM:SS",
250 "build_tag": <such as "jenkins-functest-fuel-baremetal-daily-master-108">,
251 "scenario": <Scenario on which the test was executed>,
252 "criteria": <PASS or FAILED>,
259 The API can described as follows. For detailed information, please go to
261 http://testresults.opnfv.org/test/swagger/spec.html
263 Authentication: opnfv/api@opnfv
265 Please notes that POST/DELETE/PUT operations for test or study purpose via
266 swagger website is not allowed, because it will change the real data in
271 +--------+--------------------------+-----------------------------------------+
272 | Method | Path | Description |
273 +========+==========================+=========================================+
274 | GET | /versions | Get all supported API versions |
275 +--------+--------------------------+-----------------------------------------+
280 +--------+----------------------------+-----------------------------------------+
281 | Method | Path | Description |
282 +========+============================+=========================================+
283 | GET | /api/v1/pods | Get the list of declared Labs (PODs) |
284 +--------+----------------------------+-----------------------------------------+
285 | POST | /api/v1/pods | Declare a new POD |
286 | | | Content-Type: application/json |
288 | | | "name": "pod_foo", |
289 | | | "mode": "metal", |
290 | | | "role": "ci-pod", |
291 | | | "details": "it is a ci pod" |
293 +--------+----------------------------+-----------------------------------------+
294 | GET | /api/v1/pods/{pod_name} | Get a declared POD |
295 +--------+----------------------------+-----------------------------------------+
299 +--------+----------------------------+-----------------------------------------+
300 | Method | Path | Description |
301 +========+============================+=========================================+
302 | GET | /api/v1/projects | Get the list of declared projects |
303 +--------+----------------------------+-----------------------------------------+
304 | POST | /api/v1/projects | Declare a new test project |
305 | | | Content-Type: application/json |
307 | | | "name": "project_foo", |
308 | | | "description": "whatever you want" |
310 +--------+----------------------------+-----------------------------------------+
311 | DELETE | /api/v1/projects/{project} | Delete a test project |
312 +--------+----------------------------+-----------------------------------------+
313 | GET | /api/v1/projects/{project} | Get details on a {project} |
315 +--------+----------------------------+-----------------------------------------+
316 | PUT | /api/v1/projects/{project} | Update a test project |
318 | | | Content-Type: application/json |
320 | | | <the field(s) you want to modify> |
322 +--------+----------------------------+-----------------------------------------+
327 +--------+----------------------------+-----------------------------------------+
328 | Method | Path | Description |
329 +========+============================+=========================================+
330 | GET | /api/v1/projects/{project}/| Get the list of testcases of {project} |
332 +--------+----------------------------+-----------------------------------------+
333 | POST | /api/v1/projects/{project}/| Add a new test case to {project} |
334 | | cases | Content-Type: application/json |
336 | | | "name": "case_foo", |
337 | | | "description": "whatever you want" |
338 | | | "url": "whatever you want" |
340 +--------+----------------------------+-----------------------------------------+
341 | DELETE | /api/v1/projects/{project}/| Delete a test case |
343 +--------+----------------------------+-----------------------------------------+
344 | GET | /api/v1/projects/{project}/| Get a declared test case |
346 +--------+----------------------------+-----------------------------------------+
347 | PUT | /api/v1/projects/{project}?| Modify a test case of {project} |
349 | | | Content-Type: application/json |
351 | | | <the field(s) you want to modify> |
353 +--------+----------------------------+-----------------------------------------+
357 +--------+----------------------------+------------------------------------------+
358 | Method | Path | Description |
359 +========+============================+==========================================+
360 | GET | /api/v1/results | Get all the test results |
361 +--------+----------------------------+------------------------------------------+
362 | POST | /api/v1/results | Add a new test results |
363 | | | Content-Type: application/json |
365 | | | "project_name": "project_foo", |
366 | | | "scenario": "odl-l2", |
367 | | | "stop_date": "2016-05-28T14:42:58.384Z", |
368 | | | "trust_indicator": 0.5, |
369 | | | "case_name": "vPing", |
370 | | | "build_tag": "", |
371 | | | "version": "Colorado", |
372 | | | "pod_name": "pod_foo", |
373 | | | "criteria": "PASS", |
374 | | | "installer": "fuel", |
375 | | | "start_date": "2016-05-28T14:41:58.384Z",|
376 | | | "details": <your results> |
378 +--------+----------------------------+------------------------------------------+
379 | GET | /api/v1/results? | Get the test results of {case} |
381 +--------+----------------------------+------------------------------------------+
382 | GET | /api/v1/results? | Get the test results of build_tag |
383 | | build_tag={tag} | {tag}. |
384 +--------+----------------------------+------------------------------------------+
385 | GET | /api/v1/results? | Get last {N} records of test results |
387 +--------+----------------------------+------------------------------------------+
388 | GET | /api/v1/results? | Get the test results of scenario |
389 | | scenario={scenario} | {scenario}. |
390 +--------+----------------------------+------------------------------------------+
391 | GET | /api/v1/results? | Get the test results of trust_indicator |
392 | | trust_indicator={ind} | {ind}. |
393 +--------+----------------------------+------------------------------------------+
394 | GET | /api/v1/results? | Get the test results of last days |
395 | | period={period} | {period}. |
396 +--------+----------------------------+------------------------------------------+
397 | GET | /api/v1/results? | Get the test results of {project} |
398 | | project={project} | |
399 +--------+----------------------------+------------------------------------------+
400 | GET | /api/v1/results? | Get the test results of version |
401 | | version={version} | {version}. |
402 +--------+----------------------------+------------------------------------------+
403 | GET | /api/v1/results? | Get the test results of criteria |
404 | | criteria={criteria} | {criteria}. |
405 +--------+----------------------------+------------------------------------------+
406 | GET | /api/v1/results? | get the results on pod {pod} |
408 +--------+----------------------------+------------------------------------------+
409 | GET | /api/v1/results? | Get the test results of installer {inst} |
410 | | installer={inst} | |
411 +--------+----------------------------+------------------------------------------+
412 | GET | /api/v1/results? | Get the results according to combined |
413 | | <query conditions> | query conditions supported above |
414 +--------+----------------------------+------------------------------------------+
415 | GET | /api/v1/results/{result_id}| Get the test result by result_id |
416 +--------+----------------------------+------------------------------------------+
421 +--------+----------------------------+-----------------------------------------+
422 | Method | Path | Description |
423 +========+============================+=========================================+
424 | GET |/dashboard/v1/results? | Get all the dashboard ready results of |
425 | |&project={project} | {case} of the project {project} |
427 +--------+----------------------------+-----------------------------------------+
428 | GET |/dashboard/v1/results? | Get all the dashboard ready results of |
429 | |&project={project} | {case} of the project {project} |
430 | |&case={case} | version {version} |
431 | |&version={version} | |
432 +--------+----------------------------+-----------------------------------------+
433 | GET |/dashboard/v1/results? | Get all the dashboard ready results of |
434 | |&project={project} | {case} of the project {project} |
435 | |&case={case} | since {days} days |
436 | |&period={days} | |
437 +--------+----------------------------+-----------------------------------------+
438 | GET |/dashboard/v1/results? | Get all the dashboard ready results of |
439 | |&project={project} | {case} of the project {project} |
440 | |&case={case} | installed by {installer} |
441 | |&installer={installer} | |
442 +--------+----------------------------+-----------------------------------------+
443 | GET |/dashboard/v1/results? | Get all the dashboard ready results of |
444 | |&project={project} | {case} of the project {project} |
445 | |&case={case} | on POD {pod} |
447 +--------+----------------------------+-----------------------------------------+
448 | GET |/dashboard/v1/results? | Get all the dashboard ready results of |
449 | |&project={project} | {case} of the project {project} |
450 | |&case={case} | and combined by other query conditions |
451 | |&<query conditions> | supported above. |
452 +--------+----------------------------+-----------------------------------------+
453 | GET |/dashboard/v1/projects? | Get all the dashboard ready projects |
454 +--------+----------------------------+-----------------------------------------+
456 The code of the API is hosted in the releng repository `[6]`_.
457 The test API has been dockerized and may be installed locally in your
458 lab. See `[15]`_ for details.
463 Dashboard is used to provide a consistant view of the results collected
465 The results with dashboard method are post-processed from raw results.
466 Please note that dashboard results are not stored. Only raw results are
472 Dashboard url: http://testresults.opnfv.org/dashboard/
476 Since Colorado, it was decided to adopt ELK framework. Mongo DB results
477 are extracted to feed Elasticsearch database (`[7]`_).
479 Dashboard url: http://testresults.opnfv.org/kibana_dashboards/
481 Credentials for a guest account: opnfvuser/kibana
483 A script has been developped to build elasticsearch data set. This
484 script can be found in `[16]`_.
490 An automatic reporting page has been created in order to provide a
491 consistant view of the scenarios.
492 In this page each scenario is evaluated according to test criteria.
493 The code for the automatic reporting is available at `[8]`_.
495 The results are collected from the centralized database every day and,
496 per scenario. A score is calculated based on the results from the last
497 50 days. This score is the addition of single test scores. Each test
498 case has a success criteria reflected in the criteria field from the
501 Considering an instance of a scenario os-odl_l2-nofeature-ha, the
502 scoring is the addition of the scores of all the runnable tests from the
503 categories (tiers healthcheck, smoke, controller and feature)
504 corresponding to this scenario.
507 +---------------------+---------+---------+---------+---------+
508 | Test | Apex | Compass | Fuel | Joid |
509 +=====================+=========+=========+=========+=========+
510 | vPing_ssh | X | X | X | X |
511 +---------------------+---------+---------+---------+---------+
512 | vPing_userdata | X | X | X | X |
513 +---------------------+---------+---------+---------+---------+
514 | tempest_smoke_serial| X | X | X | X |
515 +---------------------+---------+---------+---------+---------+
516 | rally_sanity | X | X | X | X |
517 +---------------------+---------+---------+---------+---------+
518 | odl | X | X | X | X |
519 +---------------------+---------+---------+---------+---------+
520 | promise | | | X | X |
521 +---------------------+---------+---------+---------+---------+
522 | doctor | X | | X | |
523 +---------------------+---------+---------+---------+---------+
524 | security_scan | X | | | |
525 +---------------------+---------+---------+---------+---------+
527 +---------------------+---------+---------+---------+---------+
529 +---------------------+---------+---------+---------+---------+
530 | copper | X | | | X |
531 +---------------------+---------+---------+---------+---------+
533 All the testcases listed in the table are runnable on
534 os-odl_l2-nofeature scenarios.
535 If no result is available or if all the results are failed, the test
537 If it was succesfull at least once but not anymore during the 4 runs,
538 the case get 1 point (it worked once).
539 If at least 3 of the last 4 runs were successful, the case get 2 points.
540 If the last 4 runs of the test are successful, the test get 3 points.
542 In the example above, the target score for fuel/os-odl_l2-nofeature-ha
545 The scenario is validated per installer when we got 3 points for all
546 individual test cases (e.g 18/18).
547 Please note that complex or long duration tests are not considered for
548 the scoring. The success criteria are not always easy to define and may
549 require specific hardware configuration. These results however provide
550 a good level of trust on the scenario.
552 A web page is automatically generated every day to display the status.
553 This page can be found at `[9]`_. For the status, click on Status menu,
554 you may also get feedback for vims and tempest_smoke_serial test cases.
556 Any validated scenario is stored in a local file on the web server. In
557 fact as we are using a sliding windows to get results, it may happen
558 that a successful scenarios is no more run (because considered as
559 stable) and then the number of iterations (4 needed) would not be
560 sufficient to get the green status.
562 Please note that other test cases e.g. sfc_odl, bgpvpn, moon) need also
563 ODL configuration addons and as a consequence specific scenario.
564 There are not considered as runnable on the generic odl_l2 scenario.
573 The installation and configuration of the Functest docker image is
576 The procedure to start tests is described in `[2]`_
579 How can I contribute to Functest?
580 =================================
582 If you are already a contributor of any OPNFV project, you can
583 contribute to functest. If you are totally new to OPNFV, you must first
584 create your Linux Foundation account, then contact us in order to
585 declare you in the repository database.
587 We distinguish 2 levels of contributors:
589 * the standard contributor can push patch and vote +1/0/-1 on any Functest patch
590 * The commitor can vote -2/-1/0/+1/+2 and merge
592 Functest commitors are promoted by the Functest contributors.
595 Where can I find some help to start?
596 ====================================
598 This guide is made for you. You can also have a look at the project wiki
600 There are references on documentation, video tutorials, tips...
602 You can also directly contact us by mail with [Functest] prefix in the
603 title at opnfv-tech-discuss@lists.opnfv.org or on the IRC chan
607 What kind of testing do you do in Functest?
608 ===========================================
610 Functest is focusing on Functional testing. The results must be PASS or
611 FAIL. We do not deal with performance and/or qualification tests.
612 We consider OPNFV as a black box and execute our tests from the jumphost
613 according to Pharos reference technical architecture.
615 Upstream test suites are integrated (Rally/Tempest/ODL/ONOS,...).
616 If needed Functest may bootstrap temporarily testing activities if they
617 are identified but not covered yet by an existing testing project (e.g
618 security_scan before the creation of the security repository)
621 How test constraints are defined?
622 =================================
624 Test constraints are defined according to 2 paramaters:
626 * The scenario (DEPLOY_SCENARIO env variable)
627 * The installer (INSTALLER_TYPE env variable)
629 A scenario is a formal description of the system under test.
630 The rules to define a scenario are described in `[4]`_
632 These 2 constraints are considered to determinate if the test is runnable
633 or not (e.g. no need to run onos suite on odl scenario).
635 In the test declaration for CI, the test owner shall indicate these 2
636 constraints. The file testcases.yaml `[5]`_ must be patched in git to
637 include new test cases. A more elaborated system based on template is
638 planned for next releases
640 For each dependency, it is possible to define a regex::
643 criteria: 'success_rate == 100%'
645 Test suite from Promise project.
647 installer: '(fuel)|(joid)'
650 In the example above, it means that promise test will be runnable only
651 with joid or fuel installers on any scenario.
653 The vims criteria means any installer and exclude onos and odl with
657 criteria: 'status == "PASS"'
659 This test case deploys an OpenSource vIMS solution from Clearwater
660 using the Cloudify orchestrator. It also runs some signaling traffic.
663 scenario: '(ocl)|(nosdn)|^(os-odl)((?!bgpvpn).)*$'
666 How to write and check constaint regex?
667 =======================================
669 Regex are standard regex. You can have a look at `[11]`_
671 You can also easily test your regex via an online regex checker such as `[12]`_.
672 Put your scenario in the TEST STRING window (e.g. os-odl_l3-ovs-ha), put
673 your regex in the REGULAR EXPRESSION window, then you can test your rule
677 How to know which test I can run?
678 =================================
680 You can use the API `[13]`_. The static declaration is in git `[5]`_
682 If you are in a Functest docker container (assuming that the
683 environement has been prepared): just use the CLI.
685 You can get the list per Test cases or by Tier::
687 # functest testcase list
696 tempest_full_parallel
703 ['vping_ssh', 'vping_userdata', 'tempest_smoke_serial', 'rally_sanity']
707 ['doctor', 'security_scan']
709 ['tempest_full_parallel', 'rally_full']
714 How to manually start Functest tests?
715 =====================================
717 Assuming that you are connected on the jumphost and that the system is
718 "Pharos compliant", i.e the technical architecture is compatible with
719 the one defined in the Pharos project::
721 # docker pull opnfv/functest:latest
722 # envs="-e INSTALLER_TYPE=fuel -e INSTALLER_IP=10.20.0.2 -e DEPLOY_SCENARIO=os-odl_l2-nofeature-ha -e CI_DEBUG=true"
723 # sudo docker run --privileged=true -id ${envs} opnfv/functest:latest /bin/bash
726 Then you must connect to the docker container and source the
729 # docker ps (copy the id)
730 # docker exec -ti <container_id> bash
734 You must first check if the environment is ready::
736 # functest env status
737 Functest environment ready to run tests.
740 If not ready, prepare the env by launching::
742 # functest env prepare
743 Functest environment ready to run tests.
745 Once the Functest env is ready, you can use the CLI to start tests.
747 You can run test cases per test case or per tier:
748 # functest testcase run <case name> or # functest tier run <tier name>
753 # functest testcase run tempest_smoke_serial
754 # functest tier run features
757 If you want to run all the tests you can type::
759 # functest testcase run all
762 If you want to run all the tiers (same at the end that running all the
763 test cases) you can type::
765 # functest tier run all
768 How to declare my tests in Functest?
769 ====================================
771 If you want to add new internal test cases, you can submit patch under
772 the testcases directory of Functest repository.
774 For feature test integration, the code can be kept into your own
775 repository. The Functest files to be modified are:
777 * functest/docker/Dockerfile: get your code in Functest container
778 * functest/ci/testcases.yaml: reference your test and its associated constraints
779 * functest/ci/exec_test.sh: run your test from CI and CLI
785 This file lists the repositories (internal or external) to be cloned in
786 the Functest container. You can also add external packages::
788 RUN git clone https://gerrit.opnfv.org/gerrit/<your project> ${repos_dir}/<your project>
793 All the test cases that must be run from CI / CLI must be declared in
796 This file is used to get the constraints related to the test::
798 name: <my_super_test_case>
799 criteria: <not used yet in Colorado, could be > 'PASS', 'rate > 90%'
801 <the description of your super test suite>
803 installer: regex related to installer e.g. 'fuel', '(apex)||(joid)'
804 scenario: regex related to the scenario e.g. 'ovs*no-ha'
807 You must declare your test case in one of the category (tier).
809 If you are integrating test suites from a feature project, the default
810 category is **features**.
816 This file is used to start your test. It is used in CI but also by the
819 You just patch the file in git and add a line::
822 "<my_super_test_case>")
823 python ${FUNCTEST_REPO_DIR}/testcases/features/mycase.py
827 Note you can use python or bash scripts (or any language assuming that
828 the packages have been properly preinstalled but we recommand python or
832 How to select my list of tests for CI?
833 ======================================
835 Functest can be run automatically from CI, a jenkins job is usually
836 called after an OPNFV fresh installation.
837 By default we try to run all the possible tests (see `[14]` called from
838 Functest jenkins job)::
840 cmd="python ${FUNCTEST_REPO_DIR}/ci/run_tests.py -t all ${flags}"
843 Each case can be configured as daily and/or weekly task.
844 When executing run_tests.py, a check based on the jenkins build tag will
845 be considered to detect whether it is a daily and/or a weekly test.
847 in your CI you can customize the list of test you want to run by case or
848 by tier, just change the line::
850 cmd="python ${FUNCTEST_REPO_DIR}/ci/run_tests.py -t <whatever you want> ${flags}"
854 cmd="python ${FUNCTEST_REPO_DIR}/ci/run_tests.py -t healthcheck,smoke ${flags}"
856 This command will run all the test cases of the first 2 tiers, i.e.
857 healthcheck, vping_ssh, vping_userdata, tempest_smoke_serial and
861 How to push your results into the Test Database
862 ===============================================
864 The test database is used to collect test results. By default it is
865 enabled only for CI tests from Production CI pods.
867 The architecture and associated API is described in previous chapter.
868 If you want to push your results from CI, you just have to call the API
869 at the end of your script.
871 You can also reuse a python function defined in functest_utils.py::
873 def push_results_to_db(db_url, case_name, logger, pod_name,version, payload):
875 POST results to the Result target DB
877 url = db_url + "/results"
878 installer = get_installer_type(logger)
879 params = {"project_name": "functest", "case_name": case_name,
880 "pod_name": pod_name, "installer": installer,
881 "version": version, "details": payload}
883 headers = {'Content-Type': 'application/json'}
885 r = requests.post(url, data=json.dumps(params), headers=headers)
890 print "Error [push_results_to_db('%s', '%s', '%s', '%s', '%s')]:" \
891 % (db_url, case_name, pod_name, version, payload), e
899 _`[1]`: http://artifacts.opnfv.org/functest/docs/configguide/index.html Functest configuration guide
901 _`[2]`: http://artifacts.opnfv.org/functest/docs/userguide/index.html functest user guide
903 _`[3]`: https://wiki.opnfv.org/opnfv_test_dashboard Brahmaputra dashboard
905 _`[4]`: https://wiki.opnfv.org/display/INF/CI+Scenario+Naming
907 _`[5]`: https://git.opnfv.org/cgit/functest/tree/ci/testcases.yaml
909 _`[6]`: https://git.opnfv.org/cgit/releng/tree/utils/test/result_collection_api
911 _`[7]`: https://git.opnfv.org/cgit/releng/tree/utils/test/scripts
913 _`[8]`: https://git.opnfv.org/cgit/releng/tree/utils/test/reporting/functest
915 _`[9]`: http://testresults.opnfv.org/reporting/
917 _`[10]`: https://wiki.opnfv.org/opnfv_functional_testing
919 _`[11]`: https://docs.python.org/2/howto/regex.html
921 _`[12]`: https://regex101.com/
923 _`[13]`: http://testresults.opnfv.org/test/api/v1/projects/functest/cases
925 _`[14]`: https://git.opnfv.org/cgit/releng/tree/jjb/functest/functest-daily.sh
927 _`[15]`: https://git.opnfv.org/cgit/releng/tree/utils/test/result_collection_api/README.rst
929 _`[16]`: https://git.opnfv.org/cgit/releng/tree/utils/test/scripts/mongo_to_elasticsearch.py
931 OPNFV main site: http://www.opnfv.org
933 OPNFV functional test page: https://wiki.opnfv.org/opnfv_functional_testing
935 IRC support chan: #opnfv-functest
937 _`OpenRC`: http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html
939 _`Rally installation procedure`: https://rally.readthedocs.org/en/latest/tutorial/step_0_installation.html
941 _`config_test.py` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.py
943 _`config_functest.yaml` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.yaml