[Starlingx-discuss] [dev] StarlingX CI Tests

Dean Troyer dtroyer at gmail.com
Wed Jun 13 15:24:14 UTC 2018


I have an extremely basic Zuul configuration set up in the STX-* repos
that runs some subset of style checkers (pep8, bashate and yamllint).
Getting some actual testing up and running is a high priority.

There are a couple of questions here:

a) Only one of the 'linters' jobs is currently passing, the existing
code base was not written with this specific set of style guidelines
in place.  All of the jobs are non-voting because of this.  The
question of _what_ style guidelines should be used needs to be
answered.  As with most things I am defaulting to common OpenStack
practices here.

b) Real tests are required.  At a bare minimum I think we need to also
have unit testing configured.  Since none of the existing Python
services are published to PyPI we will need to do a bit of extra work
for service dependencies.

As I mentioned above, I am defaulting things that have not been
specifically decided otherwise to use current OpenStack
practices/documentation as a strong guideline.  For testing the
starting point is in the Project Testing Interface[0].

At some point we will need something language-specific for our C code.

dt

[0] https://governance.openstack.org/tc/reference/project-testing-interface.html

-- 

Dean Troyer
dtroyer at gmail.com



More information about the Starlingx-discuss mailing list