| Commit message (Collapse) | Author | Age | Lines |
|
|
|
| |
Fixes #446. See issue for details.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue #409 seems to be another problem of the same type as #408,
though with the important difference that the bug in this case
is in the test suite rather than the code under test.
RequestMailer sends alert emails warning of overdue requests.
However it does not specify the order that these messages are
sent in, but runs over the overdue requests in whatever order
they are returned by a database query (that does not have an
order by clause). Therefore it is not safe for the test code
to assume that the alert mails will have been sent in a particular
order: just as with #408 it seems that they were *usually* sent
in the order assumed by the test code, but occasionally not --
which would result in sporadic test failures.
Closes #409.
|
|
|
|
| |
Really, what was that about?
|
|
|
|
| |
Corrected diagnosis, test & fix for issue #351. Fixes #351.
|
|
|
|
|
|
|
|
|
| |
The ad hoc specification of fixtures has been an ongoing source
of bugs in the tests. The straw that broke the camel’s back is
that 7c6eb09 requires the fixtures to be loaded in order (i.e.
children before their parents), and it would have been a painful
process to reorder all the dozens of different fixture lists,
but the test system ought to be more reliable this way.
|
|
|
|
|
|
| |
Add the capability to specify a limit to the number of requests a
user can make per day, which can be turned off for specific users
in the admin interface.
|
|
|
|
|
|
| |
Add some more test data, and fix the tests to accommodate both this
new test data and the fact that raw emails are now correctly loaded
into the test environment.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously there was just one raw email, and the test code relied
on that fact. Generalise it to handle multiple raw emails.
This change causes a number of tests to fail, because it exposes
failures that should have happened when the second raw email was
added but were masked by the fact that the text of this second
raw email was never loaded. These failures will be fixed in the
next commit.
|
|
|
|
|
|
| |
Might as well be consistent about clearing the test censor rules in an ensure block.
This would only mean that an exception in one test is less likely to cause unrelated
failures in another.
|
|
|
|
|
| |
This is a test for what I thought issue #370 might be. However this
test is passing, so it isn’t that.
|
|
|
|
|
|
|
|
| |
Previously many of the tests made assumptions about the global
structure of the test data set: the total number of requests, for
example, or the names of all public bodies. This makes it difficult
to add to the test data. This change is intended to make the test
data easier to extend by eliminating such global assumptions.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
app/controllers/request_controller.rb
|
| |
| |
| |
| | |
Another contribution to #361.
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
There were some order-dependent test failures that turned out to
be caused by the fact that the RoutingFilters were cleared and
not subsequently restored, by some tests.
|
| | | |
|
| |/
|/|
| |
| | |
the exception constructor are wrong.
|
|/
|
|
| |
large databases, the sorting of such large batches causes an extreme slowdown).
|
| |
|
| |
|
| |
|
|
|
|
| |
errors ad hoc as I find them that result from the workaround code. Fixes #328 (for good, I hope).
|
|
|
|
| |
issue #343.
|
|
|
|
| |
#344.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #328
|
| |
|
| |
|
|
|
|
| |
field on incoming_messages. Currently mails are always parsed just-in-time, but could be parsed as a queue in the future.
|
|\
| |
| |
| |
| | |
Conflicts:
app/controllers/request_controller.rb
|
| |
| |
| |
| | |
Fixes #310.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Conflicts:
spec/controllers/request_controller_spec.rb
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Allow specs to run independently
|
| |/ |
|
|/
|
|
| |
being treated as one for the purposes of caching. Fixes #290.
|
| |
|
|\ |
|
| |
| |
| |
| | |
The existing bug wasn't catched by the tests, because it only fails when running in dev: otherwise all the classes are loaded before the search is done, and acts_as_xapian can find the provided 'request_collapse' argument, even if the PublicBody class doesn't define it, since all the init options end up together in acts_as_xapian.
|
|/ |
|
|
|
|
| |
option, and on the next page, give the user the opportunity to change the recipient from the default (the last valid sender of a message) to any other valid recipient. Closes #35.
|
| |
|