create a jenkins job to run integration tests of gstreamer-bad

Omer and I (fginther) have been discussing this and I have some more notes to add. I also have an action to follow up with jhodapp to get some more info on this.

One question, is this something that belongs in the per-image smoke testing or can it be addressed in some other approach? How much resource and time overhead does it add? Will follow up with Jim on this.

Test executable will be: gstamcvideodec
returns 0 on pass, non-zero otherwise
results are dumped to stdout

Executes on videos in /home/phablet/Videos
Files can be pulled from chinstrap prior to run.
May have the opportunity to stream videos as well.

Setup a jenkins job to run daily until stablized, then move from there.

This should be part of a generic test runner, but we may not get there immediately.

Work on this has been postponed due to higher priority tasks. I expect to start working on this the week of March 24.

A possible starting point to create a prototype:
 1) Build the tests into an ubuntu package in a ppa (armhf enabled). Once the package is available, the upstream merger jobs have a way to acquire it
 2) Clone and modify the mir test job which is doing something similar with phablet-test-run -x to run the tests
 3) Connect the test job to an appropriate project, for example lp:media-hub. The tests are then run on every ci job for media-hub.

Some other work that is in progress (and also postponed) is to improve the way touch tests are provisioned and executed. This piggybacks on the work to test touch apps as click packages.

CI job is setup and apparently running fine. Next step is to fix/skip the failing tests. CI Job -> http://s-jenkins.ubuntu-ci:8080/job/gstreamer-testing-debug/