Anuket Project

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Since dovetail project differ from those testing projects, such as (FUNCTEST, YARDSTICK), it is necessary to list terms used in project and give a detailed description to avoid confusion.

Here is the table  showing current terms in project.

If you feel any word is unclear , you can put it into this table, so we can review and discuss these terms constantly

Welcome recommendations and comments.

 

termreferencedescriptionrecommendstatuscomments
certificationcertification file name in directory cert/management unit, collection of test case. dovetail tool runs only one certification at a time.  

Recommend not using the word certification, nor cert, in our tools or documents.

(to use "compliance" instead of "certification"? MatthewLi)

scenarioinput parameter for dovetail toolactually the same meaning as certification, seems like a redundant term  

Lets not use the term scenario.  Can we adopt "test suite" instead?

(agree, should think out name to replace this "scenario", since in OPNFV, "scenario" has special meaning MatthewLi)

test casetest case file in directory testcase/running unit, definition of a test case in dovetail, may contains multiple sub test cases from upstream projects   
sub test casetest case definition filesrepresent test cases from upstream projects (FUNCTEST/YARDSTICK/...)  propose removing this term.  "test activity" maybe.
scriptstest case definition filesdovetail leverages some upstream projects to run tests, such as (FUNCTEST/YARDSTICK/...),  scripts includes a list of attributes concerning a certain upstream project,  like 'type', 'testcase' and 'sub_testcase_list'  propose using "test source"
script test caseparameter name in conf/dovetail_config.ymla sub set of test cases from upstream projects ( FUNCTEST/YARDSTICK/... ), one script test case  may contain several sub test cases  

how does this differ from "test suite", is this a "test area"?

(I'm not sure the initial idea of this name, but in current implementation, it means test case from other projects; for example, in dovetail.ipv6.tc001.yml , script test case is 'tempest_smoke_serial' which is smoke tier test case in functest )

System Under Test (SUT)The target of the test cases.The defined functional entity to be evaluated during the execution of the test suite described.  The SUT should be consistently scoped for any given test suite.   
INSTALLER_IPconfig item in functest_config.ymlAny ip address that can access the OPENSTACK APIs is OK, could be the external ip address of OPENSTACK  

"SUT_IP" may be a candidate

(agree SUT_IP, MatthewLi)

INSTALLER_TYPEconfig item in functest_config.ymlIt's used to indicated that which installer is used to deploy the SUT, dovetail may get rid of it until testing projects do not depend on it any more  ("SUT_TYPE" maybe MatthewLi)
compliance_set     
proposed_tests     
test area     

 

compliance_set

 

      
proposed_tests     
  • No labels