>-----Original Message----- >From: Nicolas Zingilé [mailto:[email protected]] >Sent: Friday, July 04, 2014 12:53 AM >To: [email protected] >Cc: Shen, Cathy; Zhang, Xiaolei; Yu, Yucai; Ewan Le Bideau-Canévet; Stéphane >Desneux >Subject: [Tests] Automated tests on Tizen > >Hi all, > >In order to formalize the automated tests execution on a Tizen image we >decided to package the tests in test suites packages. The goal is to add >more transparency on the tests execution of a Tizen image. >Final objective will be to make sure that anyone can run consistent test >suites (in particular the release engineers, the developers and the >integrators). It will improve efficiency of the integration, since it >will be possible to run a test suite and get the results, before to >push/merge the code. > >At the moment, the following information only focuses on the IVI and >Common profiles. Future profiles, based and synced on Tizen Common >should also follow this model. > >### Strategy that will be adopted ### > >- Only automated test cases are packaged. >- Tests that are not specific to a profile will be packaged in a Common >test suite package >- Tests that are specific to a profile will be packaged in a dedicated >test suite package >- An unique launcher (common-suite-launcher) will allow to launch one or >several test suites >- No dependency between the test suites > >Example : Launch the sanity tests on the IVI profile >Since IVI is based on Common we have to launch the common-sanity-suite >and then the ivi-sanity-suite to get the full sanity of the IVI profile : > >common-suite-launcher launch common-sanity-suite ivi-sanity-suite > >### Actual status of the test suites available in Tizen ### > >For the moment 6 test suites packages are available in Tizen : > >common-sanity-suite >common-graphics-suite >common-multimedia-suite >common-crosswalk-suite >common-connectivity-suite (not functional yet) >ivi-multimedia-tests (will be removed, duplicate of common-multimedia-suite) Clarification: we need revisit the test cases in multimedia and common-multimedia-suite, add the missing but applicable cases to common-multimedia-suite, then remove ivi-multimedia-tests package.
>ivi-dist-bat-tests (will be reorganized and re-packaged in >ivi-sanity-suite) >ivi-connectivity-tests (will be removed: duplicate of >common-connectivity-suite) Clarification: test cases in ivi-connectivity-tests will be contributed to common-connectivity-suite, then remove ivi-connectivity-tests package since there is no ivi specific test cases. > >### Pending work ### > >There's some work to do before that all the test suites are fully >functional on both IVI and Common profiles : > >- review installation path of the test suites >- enhance the common-suite-launcher tool >- open a separate git project for ivi-sanity-suite >- review the test cases and the packaging of all test suites > >You can already execute a test suite on the Tizen Common image, >following this wiki page : https://wiki.tizen.org/wiki/Common_QA > >Regards, > >Nicolas Z. > >-- >--- >Nicolas Zingilé >Intel OTC - Vannes FR _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
