The CubicWeb framework provides the cubicweb.devtools.testlib.CubicWebTC test base class .
Tests shall be put into the mycube/test directory. Additional test data shall go into mycube/test/data.
It is much advised to write tests concerning entities methods, actions, hooks and operations, security. The CubicWebTC base class has convenience methods to help test all of this.
In the realm of views, automatic tests check that views are valid XHTML. See Automatic views testing for details. Since 3.9, bases for web functional testing using windmill are set. See test cases in cubicweb/web/test/windmill and python wrapper in cubicweb/web/test_windmill/ if you want to use this in your own cube.
Most unit tests need a live database to work against. This is achieved by CubicWeb using automatically sqlite (bundled with Python, see http://docs.python.org/library/sqlite3.html) as a backend.
The database is stored in the mycube/test/tmpdb, mycube/test/tmpdb-template files. If it does not (yet) exists, it will be built automatically when the test suit starts.
Warning
Whenever the schema changes (new entities, attributes, relations) one must delete these two files. Changes concerned only with entity or relation type properties (constraints, cardinalities, permissions) and generally dealt with using the sync_schema_props_perms() fonction of the migration environment need not a database regeneration step.
We start with an example extracted from the keyword cube (available from http://www.cubicweb.org/project/cubicweb-keyword).
from cubicweb.devtools.testlib import CubicWebTC
from cubicweb import ValidationError
class ClassificationHooksTC(CubicWebTC):
def setup_database(self):
req = self.request()
group_etype = req.execute('Any X WHERE X name "CWGroup"').get_entity(0,0)
c1 = req.create_entity('Classification', name=u'classif1',
classifies=group_etype)
user_etype = req.execute('Any X WHERE X name "CWUser"').get_entity(0,0)
c2 = req.create_entity('Classification', name=u'classif2',
classifies=user_etype)
self.kw1 = req.create_entity('Keyword', name=u'kwgroup', included_in=c1)
self.kw2 = req.create_entity('Keyword', name=u'kwuser', included_in=c2)
def test_cannot_create_cycles(self):
# direct obvious cycle
self.assertRaises(ValidationError, self.kw1.set_relations,
subkeyword_of=self.kw1)
# testing indirect cycles
kw3 = self.execute('INSERT Keyword SK: SK name "kwgroup2", SK included_in C, '
'SK subkeyword_of K WHERE C name "classif1", K eid %s'
% self.kw1.eid).get_entity(0,0)
self.kw1.set_relations(subkeyword_of=kw3)
self.assertRaises(ValidationError, self.commit)
The test class defines a setup_database() method which populates the database with initial data. Each test of the class runs with this pre-populated database. A commit is done automatically after the setup_database() call. You don’t have to call it explicitely.
The test case itself checks that an Operation does it job of preventing cycles amongst Keyword entities.
create_entity is a useful method, which easily allows to create an entity. You can link this entity to others entities, by specifying as argument, the relation name, and the entity to link, as value. In the above example, the Classification entity is linked to a CWEtype via the relation classifies. Conversely, if you are creating a CWEtype entity, you can link it to a Classification entity, by adding reverse_classifies as argument.
Note
commit() method is not called automatically in test_XXX methods. You have to call it explicitely if needed (notably to test operations). It is a good practice to call clear_all_caches() on entities after a commit to avoid request cache effects.
You can see an example of security tests in the Step 1: configuring security into the schema.
It is possible to have these tests run continuously using apycot.
Since unit tests are done with the SQLITE backend and this does not support multiple connections at a time, you must be careful when simulating security, changing users.
By default, tests run with a user with admin privileges. This user/connection must never be closed.
Before a self.login, one has to release the connection pool in use with a self.commit, self.rollback or self.close.
The login method returns a connection object that can be used as a context manager:
with self.login('user1') as user:
req = user.req
req.execute(...)
On exit of the context manager, either a commit or rollback is issued, which releases the connection.
When one is logged in as a normal user and wants to switch back to the admin user without committing, one has to use self.restore_connection().
Usage with restore_connection:
# execute using default admin connection
self.execute(...)
# I want to login with another user, ensure to free admin connection pool
# (could have used rollback but not close here
# we should never close defaut admin connection)
self.commit()
cnx = self.login('user')
# execute using user connection
self.execute(...)
# I want to login with another user or with admin user
self.commit(); cnx.close()
# restore admin connection, never use cnx = self.login('admin'), it will return
# the default admin connection and one may be tempted to close it
self.restore_connection()
Warning
Do not use the references kept to the entities created with a connection from another !
When running tests potentially generated e-mails are not really sent but is found in the list MAILBOX of module cubicweb.devtools.testlib.
You can test your notifications by analyzing the contents of this list, which contains objects with two attributes:
Let us look at simple example from the blog cube.
from cubicweb.devtools.testlib import CubicWebTC, MAILBOX
class BlogTestsCubicWebTC(CubicWebTC):
"""test blog specific behaviours"""
def test_notifications(self):
req = self.request()
cubicweb_blog = req.create_entity('Blog', title=u'cubicweb',
description=u'cubicweb is beautiful')
blog_entry_1 = req.create_entity('BlogEntry', title=u'hop',
content=u'cubicweb hop')
blog_entry_1.set_relations(entry_of=cubicweb_blog)
blog_entry_2 = req.create_entity('BlogEntry', title=u'yes',
content=u'cubicweb yes')
blog_entry_2.set_relations(entry_of=cubicweb_blog)
self.assertEquals(len(MAILBOX), 0)
self.commit()
self.assertEquals(len(MAILBOX), 2)
mail = MAILBOX[0]
self.assertEquals(mail.subject, '[data] hop')
mail = MAILBOX[1]
self.assertEquals(mail.subject, '[data] yes')
It is easy to write unit tests to test actions which are visible to user or to a category of users. Let’s take an example in the conference cube.
class ConferenceActionsTC(CubicWebTC):
def setup_database(self):
self.conf = self.create_entity('Conference',
title=u'my conf',
url_id=u'conf',
start_on=date(2010, 1, 27),
end_on = date(2010, 1, 29),
call_open=True,
reverse_is_chair_at=chair,
reverse_is_reviewer_at=reviewer)
def test_admin(self):
req = self.request()
rset = req.execute('Any C WHERE C is Conference')
self.assertListEquals(self.pactions(req, rset),
[('workflow', workflow.WorkflowActions),
('edit', confactions.ModifyAction),
('managepermission', actions.ManagePermissionsAction),
('addrelated', actions.AddRelatedActions),
('delete', actions.DeleteAction),
('generate_badge_action', badges.GenerateBadgeAction),
('addtalkinconf', confactions.AddTalkInConferenceAction)
])
self.assertListEquals(self.action_submenu(req, rset, 'addrelated'),
[(u'add Track in_conf Conference object',
u'http://testing.fr/cubicweb/add/Track'
u'?__linkto=in_conf%%3A%(conf)s%%3Asubject&'
u'__redirectpath=conference%%2Fconf&'
u'__redirectvid=' % {'conf': self.conf.eid}),
])
You just have to execute a rql query corresponding to the view you want to test, and to compare the result of pactions() with the list of actions that must be visible in the interface. This is a list of tuples. The first element is the action’s __regid__, the second the action’s class.
To test actions in submenu, you just have to test the result of action_submenu() method. The last parameter of the method is the action’s category. The result is a list of tuples. The first element is the action’s title, and the second element the action’s url.
This is done automatically with the cubicweb.devtools.testlib.AutomaticWebTest class. At cube creation time, the mycube/test/test_mycube.py file contains such a test. The code here has to be uncommented to be usable, without further modification.
The auto_populate method uses a smart algorithm to create pseudo-random data in the database, thus enabling the views to be invoked and tested.
Depending on the schema, hooks and operations constraints, it is not always possible for the automatic auto_populate to proceed.
It is possible of course to completely redefine auto_populate. A lighter solution is to give hints (fill some class attributes) about what entities and relations have to be skipped by the auto_populate mechanism. These are:
Warning
Take care to not let the imported AutomaticWebTest in your test module namespace, else both your subclass and this parent class will be run.
The CubicWebTC class uses the cubicweb.devtools.ApptestConfiguration configuration class to setup its testing environment (database driver, user password, application home, and so on). The cubicweb.devtools module also provides a RealDatabaseConfiguration class that will read a regular cubicweb sources file to fetch all this information but will also prevent the database to be initalized and reset between tests.
For a test class to use a specific configuration, you have to set the _config class attribute on the class as in:
from cubicweb.devtools import RealDatabaseConfiguration
from cubicweb.devtools.testlib import CubicWebTC
class BlogRealDatabaseTC(CubicWebTC):
_config = RealDatabaseConfiguration('blog',
sourcefile='/path/to/realdb_sources')
def test_blog_rss(self):
req = self.request()
rset = req.execute('Any B ORDERBY D DESC WHERE B is BlogEntry, '
'B created_by U, U login "logilab", B creation_date D')
self.view('rss', rset)
Sometimes a small component cannot be tested all by itself, so one needs to specify other cubes to be used as part of the the unit test suite. This is handled by the bootstrap_cubes file located under mycube/test/data. One example from the preview cube:
card, file, preview
The format is:
It is also possible to add a schema.py file in mycube/test/data, which will be used by the testing framework, therefore making new entity types and relations available to the tests.
CubicWeb provides some literate programming capabilities. The cubicweb-ctl tool shell command accepts differents format files. If your file ends with .txt or .rst, the file will be parsed by doctest.testfile with CubicWeb Migration API enabled in it.
Create a scenario.txt file into test/ directory and fill with some content. Please refer the doctest.testfile documentation.
Then, you can run it directly by:
$ cubicweb-ctl shell <cube_instance> test/scenario.txt
When your scenario file is ready, put it in a new test case to be able to run it automatically.
from os.path import dirname, join
from logilab.common.testlib import unittest_main
from cubicweb.devtools.testlib import CubicWebTC
class AcceptanceTC(CubicWebTC):
def test_scenario(self):
self.assertDocTestFile(join(dirname(__file__), 'scenario.txt'))
if __name__ == '__main__':
unittest_main()
If you want to set up initial conditions that you can’t put in your unit test case, you have to use a KeyboardInterrupt exception only because of the way doctest module will catch all the exceptions internally.
>>> if condition_not_met:
... raise KeyboardInterrupt('please, check your fixture.')
Using extra arguments to parametrize your scenario is possible by prepend them by double dashes.
Please refer to the cubicweb-ctl shell –help usage.
Important
Your scenario file must be utf-8 encoded.
The pytest utility (shipping with logilab-common, which is a mandatory dependency of CubicWeb) extends the Python unittest functionality and is the preferred way to run the CubicWeb test suites. Bare unittests also work the usual way.
To use it, you may:
Additionally, the -x option tells pytest to exit at the first error or failure. The -i option tells pytest to drop into pdb whenever an exception occurs in a test.
When the -x option has been used and the run stopped on a test, it is possible, after having fixed the test, to relaunch pytest with the -R option to tell it to start testing again from where it previously failed.
The base class of CubicWebTC is logilab.common.testlib.TestCase, which provides a lot of convenient assertion methods.
A unittest.TestCase extension with some additional methods.
compares two dicts
If the two dict differ, the first difference is shown in the error message :param dict1: a Python Dictionary :param dict2: a Python Dictionary :param msg: custom message (String) in case of failure
compares if two floats have a distance smaller than expected precision.
Parameters: |
|
---|
check if an object is an instance of a class
Parameters: |
|
---|
compare two strings and assert that the text lines of the strings are equal.
Parameters: |
|
---|
compare two strings and assert that the text lines of the strings are equal.
Parameters: |
|
---|
compares two lists
If the two list differ, the first difference is shown in the error message
Parameters: |
|
---|
assert obj is None
Parameter: | obj – Python Object to be tested |
---|
override default failUnlessRaises method to return the raised exception instance.
Fail unless an exception of class excClass is thrown by callableObj when invoked with arguments args and keyword arguments kwargs. If a different type of exception is thrown, it will not be caught, and the test case will be deemed to have suffered an error, exactly as for an unexpected exception.
CAUTION! There are subtle differences between Logilab and unittest2 - exc is not returned in standard version - context capabilities in standard version - try/except/else construction (minor)
Parameters: |
|
---|
compares two sets and shows difference between both
Don’t use it for iterables other than sets.
Parameters: |
|
---|
compare two multiline strings (using difflib and splitlines())
Parameters: |
|
---|
compare two multiline strings (using difflib and splitlines())
Parameters: |
|
---|
compares two iterable and shows difference between both
Parameters: |
|
---|
compares two iterable and shows difference between both
Parameters: |
|
---|
compares two iterable and shows difference between both
Parameters: |
|
---|
compares two iterable and shows difference between both
Parameters: |
|
---|
asserts the XML string is well-formed (no DTD conformance check)
Parameter: | context – number of context lines in standard message (show all data if negative). Only available with element tree |
---|
asserts the XML stream is well-formed (no DTD conformance check)
Parameter: | context – number of context lines in standard message (show all data if negative). Only available with element tree |
---|
override default failUnlessRaises method to return the raised exception instance.
Fail unless an exception of class excClass is thrown by callableObj when invoked with arguments args and keyword arguments kwargs. If a different type of exception is thrown, it will not be caught, and the test case will be deemed to have suffered an error, exactly as for an unexpected exception.
CAUTION! There are subtle differences between Logilab and unittest2 - exc is not returned in standard version - context capabilities in standard version - try/except/else construction (minor)
Parameters: |
|
---|
abstract class for test using an apptest environment
attributes:
configuration initialization hooks.
You may only want to override here the configuraton logic.
Otherwise, consider to use a different ApptestConfiguration defined in the configcls class attribute
parses url and builds the corresponding CW-web request
req.form will be setup using the url’s query string
takes url, uses application’s app_resolver to find the appropriate controller, and publishes the result.
This should pretty much correspond to what occurs in a real CW server except the apache-rewriter component is not called.
This method tests the view vid on rset using template
If no error occurred while rendering the view, the HTML is analyzed and parsed.
Returns: | an instance of cubicweb.devtools.htmlparser.PageInfo encapsulation the generated HTML |
---|