Page History

...

These are collected in the following files from a Marvin test run:

• test_data.py -> test_data.py_contents
• marvin_cfg file -> env_data
• nose test output (in JSON) -> results
• additional test run metadata -> test_metadata

File names are unimportant, as they are simply containers for the data which is then uploaded to the Elasticsearch DB

testrun_uuid ties all of the data together.

additional test run metadata

{
  "testrun": {
    "testrun_uuid": "$TESTRUN_UUID",
    "results": [{
      "classname": "tests.smoke.test_global_settings:TestUpdateConfigWithScope",
      "type": "success",
      "name": "test_UpdateConfigParamWithScope",
      "time": 0.18374300003051758
    }],
    "test_data.py_contents": "%23+Licensed+to+the+Apache+Software+Foundation+%28ASF%29+under+on......",
    "test_metadata": {
      "{
 "testrun_uuid": "fa000763-24bd-44fc-a5c6-feb82c892ca",
 "base_cloudstack_version": "4.10",
      "pr_id": "null",
      "rc_num": "null",
      "marvin_tags": "advanced",
      "marvin_hypervisor": "kvm",
      "hypervisor_version": "CentOS 6",
      "hypervisor_minor_version": "",
      "mgmt_server_os": "CentOS 7",
      "mgmt_server_os_ver": "7.3",
      "testrun_date": ""
}

test_data.py

test_data.py is stored (currently) simply for completeness.  As there are more than 1000 elements, it cannot be stored as a json object. The contents of the file is therefore URL encoded and stored in a single element

...

    }
    "env_data": ""

  }
}