| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
In the largest Alaveteli instance, WDTK, only a fraction of tracks use
filters and these specs represent those that have actually been used
commonly.
|
|
|
|
|
| |
They're not finding by the existing object, they're finding an existing
object.
|
| |
|
|
|
|
| |
Used to say "comments or requests which are " when you did: View requests > All requests > Follow
|
|
|
|
| |
The purist would probably say separate these into 3 tests
|
|
|
|
| |
via the search UI
|
|
|
|
| |
test always passes
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Rename rss_at to described_at.
Email alerts based on date of description, not just creation date (so don't
miss things that were created before alert but described only recently)
Tidy up when described vs. newest is used for sort order.
Caching of text extracted from attachments, and display in search results.
Add some tests for things that aren't tested.
(alright, maybe we *should* use git/hg if I'm going to keep doing this many
separate commits on a train)
|