aboutsummaryrefslogtreecommitdiffstats
path: root/run_tests.sh
AgeCommit message (Collapse)AuthorFilesLines
2016-06-01rename test suite scriptMatthewLi1-1/+1
JIRA: YARDSTICK-279 Change-Id: I70accc9a79b59447c907057c386f14f6a4f38346 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-05-23move /ci into /tests directoryMatthewLi1-1/+1
JIRA: YARDSTICK-269 Change-Id: I2b552aded888fa9d8f8ddd8d902b3d7f6d31a607 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-01-11Implementation of yardstick-tc006 in YardstickVincenzo Riccobene1-0/+2
Includes - Yardstick Scenario for integration with ApexLake - Yardstick Task .yaml file - Documentation JIRA: YARDSTICK-219 Change-Id: Iabde8fa63f346cf1e4a02691f22d1761de79a239 Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
2015-10-28part 2 :add coverage report in Jenkins for Yardstickkubi1-1/+12
this part is focus on script on run coverage test,not only show missing lines but also show diff between your patch and master, actually,it produce a html for coverage,but now ,it just on your local machine extra missing lines is 10-lines,final target is 4-lines JIRA:YARDSTICK-108 Change-Id: I550dff51d6f89562447e12127646155325e38a4a Signed-off-by: kubi <jean.gaoliang@huawei.com>
2015-09-25Add functional tests in verify and mergekubi1-1/+12
As Ana said ,"The first functional test should be as simple as a "Hello world", it shall be possible to run the "Hello world" test without using OpenStack." so i just finish functional test framework and do functional test for subcommand "runner"and"scenario" without using Openstack. JIRA:YARDSTICK-103 Change-Id: I673ae61f9922536a685d32ae62e5ad5165472f9d Signed-off-by: kubi <jean.gaoliang@huawei.com>
2015-08-13Make run_tests.sh verbose and enable unit testsKristian Hunt1-10/+29
By default output from run_tests is verbose. This enables seeing the error messages in Jenkins' console output when a job fails. Output can alternatively be captured to a log file using an -f flag. Example invocation for logging output to a file: $ ./run_tests.sh -f Running of unittest from run_test.sh is enabled. JIRA: YARDSTICK-102 YARDSTICK-104 Change-Id: I3be7d7873cf75247980d97c3fbdf0bfdbabe53ad Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
2015-06-15add unit test for pingJo¶rgen Karlsson1-2/+1
Running of unittest from run_test.sh is NOT enabled. JIRA:- Change-Id: I741d63e8ab37570c3cf67353fafc7f5210382219 Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
2015-05-28fix run_tests.shHans Feldt1-1/+1
Since we have no tests yet, just run flake8 Change-Id: I623d96c924524b2992175d345e176b7fd743413d JIRA: - Signed-off-by: Hans Feldt <hans.feldt@ericsson.com>
2015-05-21fix run_tests exit statusHans Feldt1-0/+2
previously run_tests always returned 0 no matter the result. It can now be hooked up to a gerrit gate job. Change-Id: I2c4bccec71c179fd2b1b965613c34179da830ac5 JIRA: - Signed-off-by: Hans Feldt <hans.feldt@ericsson.com>
2015-05-13add README and scripts for build and testHans Feldt1-0/+38
README.rst is work in progress and probably not proper rst format yet but should still contain valuable information. run_tests.sh is a script that runs unit and style tests on the code. It can be used as a gate check in gerrit. Similar scripts are standard practice in other open source projects. JIRA: - Change-Id: I5e586b346ff45f1151960a0e7fda2fe6072422c0 Signed-off-by: Hans Feldt <hans.feldt@ericsson.com>