blob: dbd03e3f18b98703060ae43e6c1b4c18cf889822 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
====================
Testing and Coverage
====================
.. module:: gstudio.tests
.. highlightlang:: console
Writing tests is important, maybe more important than coding.
And this for a lot of reasons, but I'm not here to convince you about
the benefits of software testing, some prophets will do it better than me.
* http://en.wikipedia.org/wiki/Software_testing
* https://docs.djangoproject.com/en/dev/topics/testing/
Of course Gstudio is tested using the `unittest`_ approach.
All the tests belong in the directory :file:`gstudio/tests/`.
.. _lauching-test-suite:
Launching the test suite
========================
If you have :ref:`run the buildout script<running-the-buildout>` bundled in
Gstudio, the tests are run under `nose`_ by launching this command: ::
$ ./bin/test
But the tests can also be launched within a Django project with the default
test runner: ::
$ django-admin.py test gstudio --settings=gstudio.testsettings
Using the ``./bin/test`` script is usefull when you develop because the tests
are calibrated to run fast, but testing Gstudio within a Django project even
if it's slow, can prevent some integration issues.
If you want to make some speed optimizations or compare with your tests
results, you can check the actual execution time of the tests at this URL:
http://django-blog-gstudio.com/documentation/xunit/
.. _coverage:
Coverage
========
Despite my best efforts, some functionnalities are not yet tested, that's why
I need your help !
As I write these lines the **121** tests in Gstudio cover **96%** of the code
bundled in Gstudio. A real effort has been made to obtain this percentage,
for ensuring the quality of the code.
I know that a coverage percent does not represent the quality of the tests,
but maintaining or increasing this percentage ensures the quality of
Gstudio and his future evolutions.
You can check the actual coverage percent at this URL:
http://django-blog-gstudio.com/documentation/coverage/
I hope that you will write some tests and find some bugs. :)
.. _`unittest`: http://docs.python.org/library/unittest.html
.. _`nose`: http://somethingaboutorange.com/mrl/projects/nose/
|