...
Ubuntu 16.04.2 LTS (Xenial) for x86_64
- Ubuntu 14.04 LTS (Trusty) for x86_64
- CentOS-7-1611 for x86_64
...
% cd $DOVETAIL_HOME/dovetail/results
/* local file */
1. local file
a) Log Log file: dovetail.log
/* review the dovetail.log to see if all important information has been captured - in default mode without DEBUG */
/* the end of the log file has a summary of all test case test results */
Additional Additional log files may be of interests: refstack.log, opnfv_yardstick_tcXXX.out ...
Exampleb) Example: Openstack refstack test case example
can can see the log details in refstack.log, which has the passed/skipped/failed test cases result, the failed test cases have rich debug information
for for the users to see why this test case fails.
c) Example: OPNFV Yardstick test case example
for yardstick tool, its log is stored in yardstick.log
for each test case result in Yardstick, the logs are stored in opnfv_yardstick_tcXXX.out, respectively.
/* 2. OPNFV web interface */
wait for the complement of LF, test community, etc.
...
2.4.3 Running Individual Test Cases or for Special Cases
Refstack 1. Refstack client to run Defcore testcases
a) By default, for Defcore test cases run by Refstack-client, which are consumed by DoveTail, are run followed with automatically generated configuration file, i.e., tempest.conf.
In some circumstances, the automatic configuration file may not quite satisfied with the SUT, DoveTail provide a way for users to set its configuration file according to its own SUT manually,
besides, the users should define Defcore testcase file, i.e., defcore.txt, at the same time. The steps are shown as,
when "Installing Dovetail Docker Container" method is used,
% % sudo mkdir /home/opnfv/dovetail/userconfig
% % cd /home/opnfv/dovetail/userconfig
% touch tempest.conf defcore.txt
% vim tempest.conf
% vim defcore.txt
the recommend way to set tempest.conf is shown in https://aptira.com/testing-openstack-tempest-part-1/
the recommended way to edit defcore.txt is to open https://refstack.openstack.org/api/v1/guidelines/2016.08/tests?target=compute&type=required&alias=true&flag=false and copy all the test cases into defcore.txt.
Then use “docker run” to create a container,
% sudo docker run --privileged=true -it -v <openrc_path>:<openrc_path> \
-v /home/opnfv/dovetail/results:/home/opnfv/dovetail/results \
-v /home/opnfv/dovetail/userconfig:/home/opnfv/dovetail/userconfig \
-v /var/run/docker.sock:/var/run/docker.sock \
--name <DoveTail_Container_Name> (optional) \
opnfv/dovetail:<Tag> /bin/bash
there is a need to adjust the CVP_1_0_0 testsuite, for dovetail, defcore.tc001.yml and defcore.tc002.yml are used for automatic and manual running method, respectively.
Inside the dovetail container,
% % cd /home/opnfv/dovetail/compliance
% vim CVP_1_0_0.yml
to to add defcore.tc002 and annotate defcore.tc001.
% % cd $DOVETAIL_HOME/dovetail
% % mkdir userconfig
% % cd userconfig
% % touch tempest.conf defcore.txt
% % vim tempest.conf
% % vim defcore.txt
recommended way to set tempest.conf and defcore.txt is same as above in "Installing Dovetail Docker Container" method section.
For Defcore test cases manually running method, there is a need to adjust the compliance_set test suite,
for dovetail, defcore.tc001.yml and defcore.tc002.yml are used for automatic and manual running method, respectively.
% cd $DOVETAIL_HOME/dovetail/compliance
% vim CVP_1_0_0.yml
to add defcore.tc002 and annotate defcore.tc001
3 Dovetail Client CLI Manual
...