Please run the autopilot-qt autopilot test suite as part of CI

[Thomi Richards]

Please could someone alter the autopilot-qt ci configuration so it runs the autopilot test suite as part of the regular CI runs?

We need this to be run on amd64/trusty for now (We'll work on getting it going on arm later). The actual job to run is a little bit tricky because we need to run it twice - once in 'qt4' mode, and once in 'qt5' mode. The code to run both is as follows:

qmake -qt=qt4
make
cd tests/autopilot
autopilot run libautopilot_qt
cd ../..
make distclean
qmake -qt=qt5
make
cd tests/autopilot
autopilot run libautopilot_qt

Please let me know if you need any more information.

[Francis Ginther (fginther)]

I can't think of anyway to do this without a custom job as it has to be built twice with different qmake parameters. I am starting to see a template for a generic job here, that just pulls in the customization from a bzr branch... If autopilot can be executed with xvfb, then what I have in mind is doable. I know the autopilot-gtk tests use xvfb, so I think this is not an issue.

[Thomi Richards (thomir-deactivatedaccount)]

I don't see any reason why these wouldn't run in xvfb as well. Any chance we can get an approximate timeframe for this? Is it out of the question to have this done before the 14.04 release?

Cheers,

[Francis Ginther (fginther)]

Yes, this is planned to be done before 14.04 although the time frame is very narrow now. I will have more time to devote to this and other projects starting March 24. This is when I plan to start work on the infrastructure changes needed to address this and a couple other new CI requests together.

If this timeline is not sufficient, please let me know. We can look at other autopilot/QA team related tasks and re-prioritize if necessary. There's also the possibility of a quick and dirty solution, but I don't want to do that if possible (s-jenkins is full of quick and dirty solutions that somehow keep sticking around).