summaryrefslogtreecommitdiffstats
path: root/samples/test_suite.yaml
AgeCommit message (Collapse)AuthorFilesLines
2018-05-10Update samples/test_suite.yamlEmma Foley1-1/+2
The sample test suite at sample/test_suite.yaml contained incorrect syntax. It has been updated to add the "default" parameter to "task_args" when running a testcase. JIRA: YARDSTICK-1125 Change-Id: I53409168e47d969317145623df1e2c789396cc32 Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 7b00d64494bdd61f2ab37005de76fa5f6496d45d)
2017-02-17Update missing license headersDeepak S1-0/+8
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2015-10-13Add test suite functionality to task commandsKristian Hunt1-0/+18
This patch proposes a more permanent solution to replace the already existing one (YARDSTICK-106). A test suite is a .yaml file which consists of multiple task files which are meant to run as a one set. Each test case in the test suite has to specify the location of the test .yaml task file and can specify additional task arguments or a task arguments file. It is possible to specify the directory where the task files are located in the suite file. If it is left unspecified then it defaults to tests/opnfv/test_cases according to https://etherpad.opnfv.org/p/yardstick_folders A Command line argument --suite is added to the task command. This argument indicates that the intention is to run a test suite. JIRA: YARDSTICK-107 Change-Id: I69508b3b536dd592b6240a2a32dd5d665e0ac4b4 Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>