openstack
/
nova
Code Issues Proposed changes
nova/nova/tests/functional/regressions
History
jichenjc eda0c1cdf0 Add functional regression test for bug 1552888 
Add this functional test to avoid further regress issue

Related-Bug: 1552888

Change-Id: I1b8843132394c39324c19bc46dded974625775a9
 		2016-02-23 16:21:31 +08:00
..
README.rst add a place for functional test to block specific regressions 2016-02-24 18:14:27 +00:00
__init__.py add a place for functional test to block specific regressions 2016-02-24 18:14:27 +00:00
test_bug_1522536.py add a place for functional test to block specific regressions 2016-02-24 18:14:27 +00:00
test_bug_1541691.py add regression test for bug #1541691 2016-02-24 20:21:43 -05:00
test_bug_1548980.py Add functional regression test for list deleted instances on v2.16 2016-02-25 09:50:52 -05:00
test_bug_1552888.py Add functional regression test for bug 1552888 2016-02-23 16:21:31 +08:00

README.rst

Tests for Specific Regressions

When we have a bug reported by end users that we can write a full stack reproduce on, we should. And we should keep a regression test for that bug in our tree. It can be deleted at some future date if needed, but largely should not be changed.

Writing Regression Tests

  • These should be full stack tests which inherit from nova.test.TestCase directly. (This is to prevent coupling with other tests).
  • They should setup a full stack cloud in their setUp via fixtures
  • They should each live in a file which is named test_bug######.py

Writing Tests Before the Bug is Fixed

TODO describe writing and landing tests before the bug is fixed as a reproduce.