| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
|
|
|
|
| |
param of 1. Fixes #557.
|
|\ |
|
| |
| |
| |
| | |
Closes #554.
|
|/
|
|
|
|
| |
no record is found using url_title.
Closes #553.
|
|
|
|
| |
visible to everyone, so can be served up from a file cache without authentication.
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Gemfile.lock
script/handle-mail-replies
script/handle-mail-replies.rb
spec/controllers/request_controller_spec.rb
|
| |
| |
| |
| | |
Otherwise we issue PURGEs every time, for example, we send out email alerts.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
files. Closes #428"
This reverts commit 506af7a640f63b17000ccfc5e1344bbc3039c913.
See issue #428 for a discussion
|
| | |
|
| | |
|
| |
| |
| |
| | |
requested the attention, not the user who made the original request.
|
| |
| |
| |
| |
| | |
Since users must now be logged-in to report requests, the tests
need to reflect this.
|
|/
|
|
|
| |
The wording that was changed by e3cfe550fe835c68b25d693abd40aedd954913b3
turns out to be relied on by one of the tests.
|
| |
|
| |
|
|
|
|
| |
Fixes #454
|
|
|
|
| |
purge.
|
|
|
|
| |
collection (e.g. `@user.info_requests.each`)
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
spec/controllers/request_controller_spec.rb
|
| |\
| | |
| | | |
Small fixes
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes #446. See issue for details.
|
| | |
|
| |
| |
| |
| | |
Closes #428
|
| |
| |
| |
| | |
Fixes #421.
|
| |
| |
| |
| | |
Next step: making it asynchronous, e.g. with a queue of things to purge via a cron job.
|
| |
| |
| |
| | |
Closes #428
|
|/
|
|
| |
Fixes #421.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\ |
|