From e28c18f6565fdd6a0e0bc34c58d74cf78438433d Mon Sep 17 00:00:00 2001 From: Luz Cazares Date: Fri, 29 Apr 2016 08:53:04 -0700 Subject: [PATCH] Remove negative test framework documentation We have a conclusion to remove the description of negative test framework during Austin summit, details at: https://etherpad.openstack.org/p/newton-qa-negative-testing Change-Id: Ia3d36b8d1c8e9721b88dbc35bc350af822b8dc6f --- HACKING.rst | 28 +--------------------------- 1 file changed, 1 insertion(+), 27 deletions(-) diff --git a/HACKING.rst b/HACKING.rst index 4095c4b899..45bd6a2e37 100644 --- a/HACKING.rst +++ b/HACKING.rst @@ -157,33 +157,7 @@ not there even if the cloud was configured with it. Negative Tests -------------- -Newly added negative tests should use the negative test framework. First step -is to create an interface description in a python file under -`tempest/api_schema/request/`. These descriptions consists of two important -sections for the test (one of those is mandatory): - - - A resource (part of the URL of the request): Resources needed for a test - must be created in `setUpClass` and registered with `set_resource` e.g.: - `cls.set_resource("server", server['id'])` - - - A json schema: defines properties for a request. - -After that a test class must be added to automatically generate test scenarios -out of the given interface description:: - - load_tests = test.NegativeAutoTest.load_tests - - @test.SimpleNegativeAutoTest - class SampleTestNegativeTestJSON(, test.NegativeAutoTest): - _service = 'compute' - _schema = - -The class decorator `SimpleNegativeAutoTest` will automatically generate test -cases out of the given schema in the attribute `_schema`. - -All negative tests should be added into a separate negative test file. -If such a file doesn't exist for the particular resource being tested a new -test file should be added. +TODO: Write the guideline related to negative tests. Test skips because of Known Bugs --------------------------------