openstack/nova

History

Rajesh Tailor 9ebf9a5aa5 Trivial-Fix: Fix typos Change-Id: I09a87b7a13cf551f18ef1fb27aa9f5406baebab4		2016-06-13 06:41:08 +00:00
..
__init__.py	add a place for functional test to block specific regressions	2016-02-24 18:14:27 +00:00
README.rst	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	Fixes unexpectedly passing functional test.	2016-04-15 17:21:19 +02:00
test_bug_1548980.py	Don't lazy-load instance.services if the instance is deleted	2016-02-25 10:06:39 -05:00
test_bug_1552888.py	Trivial-Fix: Fix typos	2016-06-13 06:41:08 +00:00
test_bug_1554631.py	Add functional test for OverQuota	2016-03-11 22:13:03 +00:00
test_bug_1558866.py	Config options: remove import_opts from completed section	2016-05-13 15:57:32 +07:00
test_bug_1568208.py	Fix generation of Guru Meditation Report	2016-04-13 17:00:32 +03: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.