These are notes I took while getting the current version of the test suite to work with bedework.
I've zipped up a copy of most of the affected files.
Added this after line 54 in propfindItems.py - I think it dealt with errors that caused exceptions - produced more useful messages
if value is None:
return False, " Could not parse XML value: None"
if value == "":
return False, " Could not parse XML value: zero len"
Where there were delays in the tests they were sometimes not long enough. I added a variable to the server config and used that. It's probably over-long
<!-- delay inserted (usually after PUT) to allow background scheduling
processes to run -->
<substitution>
<key>$schedDelay:</key>
<value>14</value>
</substitution>
Added/changed some delays (used token to set delay length) to
In reports.xml I'd previously added a load of DEPTH: 1 headers - they may be needed again. Note done yet.
Running all the tests leads to a lot of failures. Turns out user02 is left with a read only privilege on the home which affects everything below it. acl.xml doesn't clean up user2 home afterwards.
douglm@… originally submitted this as ticket:517
These are notes I took while getting the current version of the test suite to work with bedework.
I've zipped up a copy of most of the affected files.
Added this after line 54 in propfindItems.py - I think it dealt with errors that caused exceptions - produced more useful messages
Where there were delays in the tests they were sometimes not long enough. I added a variable to the server config and used that. It's probably over-long
Added/changed some delays (used token to set delay length) to
In reports.xml I'd previously added a load of DEPTH: 1 headers - they may be needed again. Note done yet.
Running all the tests leads to a lot of failures. Turns out user02 is left with a read only privilege on the home which affects everything below it. acl.xml doesn't clean up user2 home afterwards.
Added
to the end stuff with 99.xml being
Not altogether what I want but deals with the issue.