summaryrefslogtreecommitdiff
path: root/scripts/qemuimage-tests
Commit message (Collapse)AuthorAgeFilesLines
* qemuimagetest: Rename test scenario file from poky-image-sdk to ↵Jiajun Xu2011-02-105-0/+0
| | | | | | poky-image-sato-sdk Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* qemuimagetest: Use same image during sanity testing instead of copying a new ↵Jiajun Xu2011-01-2024-43/+29
| | | | | | | | | | | | | | | | | image for each case To reduce the time on sanity testing, we remove variable SHARE_IMAGE and use a new variable TEST_SERIALIZE in local.conf. It is by default set to 1. Poky will copy and boot the to-be tested image for only once. It will not remove or kill the image and test cases will be serialized executed against the same image. If it is set to 0, image is always be copied for each cases, which takes much time. I had a experiment that latest qemuppc sato only takes 7 minutes to finish 9 sanity test cases, which takes more than 20 minutes before. I also removed sanity case "boot" from sato/sdk/lsb because the other cases for these targets already cover the check point of "boot". Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* qemuimagetest: Use the same image in sanity testing to fix the timeout issue ↵Jiajun Xu2011-01-1424-24/+29
| | | | | | | | | | | | | | | on autobuilder Fixes [BUGID #595] Because of the QEMU booting slowness issue(see bug #646 and #618), autobuilder may suffer a timeout issue when running sanity test. We introduce variable SHARE_IMAGE here to fix the issue. It is by default set to 1. Poky will copy latest built-out image and keep using it in sanity testing. If it is set to 0, latest built-out image will be copied and tested for each case, which will take much time. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* qemuimagetest: Remove connman test for lsb image and fix one warning in ↵Jiajun Xu2011-01-065-5/+0
| | | | | | | | | | Test_Create_Qemu There is no connman in LSB image. So we need to remove connman test from it. And when we check if ip address fetched by Test_Fetch_Target_IP is valid, we should use "==" operator for string comparison. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* qemuimagetest: Add basic function check for connmanJiajun Xu2011-01-0217-0/+122
| | | | | | | | Add one case for connman sanity test. We check if connmand is running in background after booting and if there is always one connmand process running even connmand is executed by several times. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* qemuimagetest: Add basic function check for gcc/g++/make command in targetJiajun Xu2011-01-027-0/+194
| | | | | | Add one case for compile tools sanity test in target, including gcc/g++/make. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* qemuimagetest: Add basic function check for rpm commandJiajun Xu2011-01-0217-0/+112
| | | | | | Add one case for rpm query sanity test. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* qemuimagetest: Add basic function check for zypper commandJiajun Xu2011-01-0218-0/+179
| | | | | | Add two cases for zypper sanity test. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* Add sanity test scenarios for -lsb imagesScott Garman2010-12-075-0/+25
| | | | Signed-off-by: Scott Garman <scott.a.garman@intel.com>
* imagetest-qemu: Add sanity test cases for scp/shutdown in targetJiajun Xu2010-11-1416-3/+171
| | | | | | | scp test is to check if file copying via network work or not in target. shutdown test is to check if target can be poweroff with qemu process off. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* imagetest-qemu: Add test case for dmesg check in targetJiajun Xu2010-11-1012-5/+89
| | | | | | | | Add a test case for error log check with command dmesg in target. The case introduces a new folder in target, "/opt/test", which holds test scripts running in target. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* test: Add scenario file for each target and support single case runningJiajun Xu2010-08-2712-0/+20
| | | | | | | | | | | | | | | | Different test cases are needed for different targets. A folder "scenario" is created under scripts/qemuimage-tests to hold scenario files for different targets. Single case running is supported now. User can run single case together with a whole test suite by setting variable TEST_SCEN in local.conf. By default test cases in sanity suite will be ran. If you want to run other test suite or specific test case(e.g. bat or boot test case under sanity suite), list them like following. TEST_SCEN = "sanity bat sanity:boot" Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
* Enable build dir outside of the poky directoryJoshua Lock2010-07-212-3/+2
| | | | | | | | | | | | | | | | | | You need to first set up the build directory by sourcing the poky build script, after that builds can be run in that directory so long as bitbake is in $PATH removing the need to source the init script for each build. i.e: $ . poky-init-build-env ~/my-build $ bitbake some-image <<later, in a different shell>> $ cd ~/my-build $ export PATH=/path/to/bitbake/bin:$PATH $ bitbake an-image This patch also removes use of OEROOT in recipes, etc. Signed-off-by: Joshua Lock <josh@linux.intel.com>
* test: add automation framework and sanitytestJiajun Xu2010-07-152-0/+71
Automation test is disabled by default. User need set TESTCLASS to qemu in conf/local.conf and run bitbake command "bitbake poky-image-xxx" or "bitbake poky-image-xxx -c qemuimagetest" to trigger it. Currently only the sanity test with two testcases are added. To run the test, user need prepare a testing environment: 1) "expect" should be installed on system 2) NOPASSWD should be set for user to run bitbake Signed-off-by Jiajun Xu <jiajun.xu@intel.com>