I tried the latest maintenance version from svn #22782 on Win:
cd "D:\Gramps4.0nativPy2.7.3\test"
C:\Python27\python "-v 3"
having still this result:
test_buffer_recall (ErrorReportAssistant_Test.ErrorReportAssistantTest)
Test that simple recall of messages works. ... ERROR
test_window (GtkHandler_Test.GtkHandlerTest)
Test that the window appears. ... ok
test_buffer_recall (RotateLogger_Test.RotateHandlerTest)
Test that simple recall of messages works. ... ok
test_buffer_rotation (RotateLogger_Test.RotateHandlerTest)
Test that buffer correctly rolls over when capacity is reached. ... ok

ERROR: test_buffer_recall (ErrorReportAssistant_Test.ErrorReportAssistantTest)
Test that simple recall of messages works.
Traceback (most recent call last):
  File ".\GrampsLogger\", line 60, in test_buffer_recall
  File "..\gramps\gui\logger\", line 81, in __init__
  File "..\gramps\gui\logger\", line 267, in build_page1

  File "..\gramps\gui\logger\", line 178, in _reset_error_details
AttributeError: 'str' object has no attribute 'get_record'

Ran 4 tests in 1.872s

FAILED (errors=1)
The message box appears. I choose CANCEL.
What's to do?

- Helge
Am 31.07.2013 00:19, schrieb Nick Hall:

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:

To run all unit tests use:

GRAMPS_RESOURCES=. python -m unittest discover -p '*'

You can get more output by adding the -v flag:

GRAMPS_RESOURCES=. python -m unittest discover -p '*' -v

Some of the unit tests will work with python3, but not all of them.  I 
couldn't find bindings for libxml2.


On 28/07/13 09:56, Vassilii Khachaturov wrote:
On 27.07.2013 23:10, 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

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.

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).


See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
Gramps-devel mailing list

Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
Gramps-devel mailing list