[Modeling-users] tests failing

[John L. <jl...@gm...>]

I'm getting ready to create test cases for several of the patches that
are emerging from the work I've been doing in the last months; to
avoid regressions, I'm trying to make sure I have everything set up to
run the tests correctly, but several of the tests are failing, both in
0.9-pre-17.1 and current cvs, with the following message:

ValidationException: Validation for key books failed:
- Key is required but value is void
Validation for key OBJECT_WIDE_VALIDATION failed:
- Validation of object <test_EditingContext_Global.Writer_test07
object at 0x40ad3c6c> as a whole failed

the tests are from test_EditingContext_Global.py:
  test_07_savechanges_01
  test_09_savechanges_03
  test_10_saveChanges_04
  test_12_fetchingDoesNotUpdateSnapshot
  test_17b_insertedObject_and_FK_as_classProperty
  test_20_snapshot
  test_22_cancel_delete

apart from these seven errors I get three failures, in

  test_CooperatingObjectStoreNeededNotification.py:
    test_01_initialState
  test_EditingContext_Global.py:
    test_00_insertObject_loads_databaseContexts
    test_08_savechanges_02

and two extra failures in cvs head that seem to be harmless (different
ordering of attributes in a sql statement).

am I doing something wrong? I'm guessing the README is outdated,
because I tried that and it was even worse; I ran
'test_EditingContext_Global.py -r' and
'test_EditingContext_Global_Inheritance.py -r', and then 'run.py -g'.
These two give errors every time, complaining that

DROP INDEX WRITER_pkey
error: Couldn't evaluate expression DROP INDEX WRITER_pkey. Reason:
psycopg.ProgrammingError:ERROR:  cannot drop index writer_pkey because
constraint writer_pkey on table writer requires it
HINT:  You may drop constraint writer_pkey on table writer instead.

Also, one thing that isn't mentioned in the README is that the
database must be created with -E LATIN1, or it will produce an(other)
error.

-- 
John Lenton (jl...@gm...) -- Random fortune:
bash: fortune: command not found