Re: [Gramps-devel] Gramps-devel Digest, Vol 86, Issue 18

[Vassilii K. <vas...@ta...>]

Amazing, thank you very much!!!
VKh

On 31.07.2013 01:19, Nick Hall wrote:
> Vassilii,
>
> The unit tests should now work.  You can run them from the top-level
> Gramps directory with:
>
> GRAMPS_RESOURCES=. python -m unittest <test module>
>
> for example:
>
> GRAMPS_RESOURCES=. python -m unittest gramps.gen.lib.test.date_test
>
> A full list of tests is available on the wiki:
>
> http://www.gramps-project.org/wiki/index.php?title=Testing_Gramps#unit_tests_in_the_main_tree
>
> To run all unit tests use:
>
> GRAMPS_RESOURCES=. python -m unittest discover -p '*_test.py'
>
> You can get more output by adding the -v flag:
>
> GRAMPS_RESOURCES=. python -m unittest discover -p '*_test.py' -v
>
> Some of the unit tests will work with python3, but not all of them.  I
> couldn't find bindings for libxml2.
>
>
> Nick.
>
>
> On 28/07/13 09:56, Vassilii Khachaturov wrote:
>> On 27.07.2013 23:10, gra...@li... wrote:
>>> Since python v2.7 the unittest module has the ability to discover unit
>>> tests.  We just need to ensure they conform to a standard naming
>>> convention and are importable.  So we may not even need the RunAllTests
>>> script.
>>>
>>> It is easy to add a custom command to distutils.  There is already a
>>> "check" command which checks the meta-data, but a "test" command is a
>>> good idea.
>>>
>>> Let me know if you want me to add it.
>>>
>>> Nick.
>> Sounds like a good plan, let's just revive the unit tests first and
>> separate the interactive ones, so that a fully automated run is possible.
>> (I've added this to the wiki).
>>
>> V.
>>