| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
| |
Revert a small part of 33f8ef66084bbfb61bf0b4e0f53e1da5e7cc84dc,
which was not intended, so that the behaviour is unchanged if a
xapian database doesn’t exist, say.
|
|
|
|
|
|
| |
This *ought* to fix the problem with the alert-tracks daemon
opening more and more copies of the xapian db till it exhausts
the available file descriptors.
|
|
|
|
| |
Update test to take account of change 76fd5f9.
|
| |
|
|
|
|
|
|
|
| |
If a user cannot make new requests because they are
rate-limited, and they compose a request whilst logged
out, include the text of the request in the message
that explains about the rate limit so it is not lost.
|
| |
|
|
|
|
|
|
|
|
| |
When a user account has been suspended, we write (Banned) after their
user name. But sometimes we need to suspend accounts temporarily,
such as pending the result of a discussion, and it is misleading
to write (Banned) in such cases; so let’s change it to (Account
suspended) instead.
|
|
|
|
|
|
|
|
|
| |
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 a patch from louisecrow (https://github.com/mysociety/fixmytransport/blob/master/lib/patches/fixtures_constraint_disabling.rb)
that makes it possible to run the tests without being a database superuser.
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
config/general.yml-example
doc/CHANGES.md
|
| |
| |
| |
| |
| |
| | |
Add MAX_REQUESTS_PER_USER_PER_DAY to general.yml-example, because
the mySociety deployment system insists that the example file specify
precisely the same variables as the deployed one.
|
| |
| |
| |
| |
| | |
I am not sure why the tests anyway passed with this mistake, but
clearly those trailing .should's ought not to have been there.
|
| |
| |
| |
| | |
Document MAX_REQUESTS_PER_USER_PER_DAY in the 0.5 release notes
|
| |
| |
| |
| | |
4899ae188f728bfd77b6db950fd5a1e3180c7be8
|
| | |
|
| |
| |
| |
| | |
At the same time, cause the tests not to rely on WDTK data. Fixes #396
|
| |
| |
| |
| | |
categories have something to work with. Currently not used in any tests.
|
| | |
|
|/ |
|
|
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| | |
Test that duplicate requests are coalesced on the front page.
|
| |
| |
| |
| |
| |
| | |
Better error reporting when an incoming message has no raw_email.
This is useful if you make a mistake when creating new test data,
to pick an example application completely at random (not).
|
| |
| |
| |
| |
| |
| |
| | |
Put the most-recently-answered first, rather than the
most-recently-reclassified. This is inspired by issue #370,
though it does not fix all the issues raised in that ticket.
(The wording is still outright misleading in some cases.)
|
| |
| |
| |
| |
| | |
So, well, I found this change when I ran git diff; and the truth
is that I just prefer it aesthetically. Is that so sinful?
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
Accept test pairs on stdin even if they are not prefixed with the
string "* FAILED: ".
|
| |
| |
| |
| |
| | |
If $RAILS_ENV is unset, raise an exception rather than just blithely
creating a directory called cache/attachments_.
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | | |
- There is no such thing as “cursor: hand;”
- Opacity is not measured in pixels.
|
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/
|/|
| |
| |
| | |
This was added for temporary debugging purposes, and ought to have
been removed.
|
|\ \ |
|
| |\| |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| | |
|