[QA] Hooking Travis and Gerrit (was: Setting up Travis testing)

[Antoine Musso]

Le 31/10/2014 02:12, Gabriel Wicke a écrit :
<snip>
> Okay, fair enough. We can get by using github PRs & Travis in the meantime,
> but it would be nice to eventually move back into the standard code review &
> CI system.

Hello,

As I understand it RESTBase has integration tests hitting a backend
(Cassandra).  There is a few approaches we can take:

- flags such tests with a tag which would let us skip them entirely on
the Wikimedia Jenkins slaves.  That could be known as fast tests and it
is a good first step.

- whenever it make sense, convert the integration tests to unit tests
that mock Cassandra

- create a dedicated labs instance that is configured like the other
ones but with Cassandra.  Would need a bunch of integration to setup and
teardown Cassandra though and figure out a solution for multiple tests
to use different instances / data set.


Some related examples:

The pywikibot project has integration tests that hit production wikis.
They are flagged and filter out when running tests on the Wikimedia Jenkins.

The analytics Wikimetrics project has some tests that needs a redis
backend, they are as well flagged with 'manual_test' and could be
filtered out as well.

Overall, that is slightly more difficult than using Travis, but doable.




-- 
Antoine "hashar" Musso