References
================
-- Defcore test cases
+- OpenStack interoperability guidelines (version 2016.08)
- https://github.com/openstack/interop/blob/master/2016.08.json
- https://www.openstack.org/brand/interop/
-- Defcore test cases listed using the Rest API from RefStack project
+- OpenStack interoperability test cases excluding object storage
- https://refstack.openstack.org/api/v1/guidelines/2016.08/tests?target=compute&type=required&alias=true&flag=false
-- Refstack client
-
- - https://github.com/openstack/refstack-client
Definitions and abbreviations
=============================
Dependency Description
======================
-The VIM identity operation test area is a part of the DefCore tempest test
-cases run by refstack, then inherited by dovetail. Refstack-client is a command line
-utility that allows you to execute Tempest test runs based on configurations you specify.
-It is the official tool to run Defcore test cases,
-which focuses on testing interoperability between OpenStack clouds.
-
-For Danube based dovetail release, the approved Defcore 2016.08 guidelines is adopted,
-which is valid for Kilo, Liberty, Mitaka and Newton releases of Openstack.
+The VIM identity operations test cases are a part of the OpenStack
+interoperability tempest test cases. For Danube based dovetail release, the
+OpenStack interoperability guidelines (version 2016.08) is adopted, which is
+valid for Kilo, Liberty, Mitaka and Newton releases of Openstack.
Test Descriptions
=================
key_filename: /root/.ssh/id_rsa
-Special Configuration for Running defcore, IPv6 and tempest Test Cases
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Configuration for Running Tempest Test Cases
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-All test cases in test area defcore, ipv6 and tempest are picked up from Tempest.
-For all these test cases, they need some configurations. Most of them
-are done by Dovetail. However, there are still some configurations needed to be
-given by users who know the SUT better. All these additional configurations should
-be in file ``$DOVETAIL_HOME/pre_config/tempest_conf.yaml``. If this file is not given,
-some test cases will be skipped or failed.
+The test cases in the test areas `interop` (OpenStack Interoperability tests),
+`ipv6` and `tempest` are based on Tempest. A SUT-specific configuration of
+Tempest is required in order to run those test cases successfully. The
+corresponding SUT-specific configuration options should be supplied in the file
+``$DOVETAIL_HOME/pre_config/tempest_conf.yaml``.
Create and edit file ``$DOVETAIL_HOME/pre_config/tempest_conf.yaml``.
Here is an example of what this file should contain.
* Additional log files may be of interests: refstack.log, dovetail_ha_tcXXX.out ...
- * Example: defcore test case example
+ * Example: OpenStack Interoperability test cases
- * Can see the log details in ``defcore_logs/dovetail.defcore.tc001.log``,
+ * Can see the log details in ``osinterop_logs/dovetail.osinterop.tc001.log``,
which has the passed, skipped and failed test cases results.
* The skipped test cases have the reason for the users to see why these test cases skipped.