Open Stack

Hi folks,

Sorry I didn't make the meeting this morning :-(

We touched on testing at the mid-cycle and again it came up in the meeting
this morning. We identified two issues:

1. Our integration test suite cannot grow to too many more tests because
they take too long to run (and get auto-killed). We could increase the
amount of time allowed for them, but we agreed that we shouldn't do this.
2. We don't have enough higher-level (integration leve) test coverage for
our newer angular interfaces.

These two are obviously at odds :-)

What we agreed on, I think, is that we're going to:

1. Reduce the granularity of the integration tests - use them to broadly
test whether an interface works at all when presented to a browser,
2. Replace many single interface tests with a fewer tests that poke at many
interfaces (thus removing the significant per-test overhead) - even
potentially having a single test that attempts to access every panel (as a
guard against gross Javascript incompatibilities or configuration issues
breaking panels),
3. Move the integration tests to tempest, and
4. Write some "django unit test suite" functional tests for our angular
code that tests more than just the single units we currently test (ie. mock
at a more remote level, checking that broader interactions work).

Does this sound about right?


     Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160721/284d972c/attachment.html>