On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier <[email protected]> wrote: > We don"t run slow tests because the QA team think that they don't bring > enough value to be executed, every time and everywhere. The idea is that if > some specific slow tests are of some interest to some specific openstack > projects, those projects can change the config of their jobs to enable these > tests.
But since it's not executed anywhere in tempest gate, even as non-voting (?), it's effectively dead code that may be long broken without anyone knowing. Of course there are consumers of the tests downstream, but for those consumers it's a tough call to start depending on the tests if they are not sanity checked by tempest itself. Wouldn't it make sense to have some job in tempest gate that would execute those tests (maybe just them to speed up such a job? maybe non-voting? maybe even as periodic? but there should be something that keeps it green in long run). Ihar __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
