[testlib] make a clear distinction between input / output HTTP headers
The get_header() / set_header() API is the same as for CubicWebRequestBase :
- get_header() returns the **request** header
- set_header() / add_header() works on the **response** header
FakeRequest adds two additional methods :
- get_response_header() returns the **reponse** header
- set_request_header() adds a **request** header
FakeRequest now uses the `headers_out` ineherited from CubicWebRequestBase.
It also uses a `_headers_in` attribute
# copyright %(year)s %(author)s, all rights reserved.
# contact %(author-web-site)s -- mailto:%(author-email)s
#
%(long-license)s
"""%(distname)s automatic tests
uncomment code below if you want to activate automatic test for your cube:
.. sourcecode:: python
from cubicweb.devtools.testlib import AutomaticWebTest
class AutomaticWebTest(AutomaticWebTest):
'''provides `to_test_etypes` and/or `list_startup_views` implementation
to limit test scope
'''
def to_test_etypes(self):
'''only test views for entities of the returned types'''
return set(('My', 'Cube', 'Entity', 'Types'))
def list_startup_views(self):
'''only test startup views of the returned identifiers'''
return ('some', 'startup', 'views')
"""
from cubicweb.devtools import testlib
class DefaultTC(testlib.CubicWebTC):
def test_something(self):
self.skipTest('this cube has no test')
if __name__ == '__main__':
from logilab.common.testlib import unittest_main
unittest_main()