diff options
author | Robin Houston <robin.houston@gmail.com> | 2012-01-29 19:07:42 +0000 |
---|---|---|
committer | Robin Houston <robin.houston@gmail.com> | 2012-01-29 19:07:42 +0000 |
commit | 2f82314374a644952019ac34b59dff10f6470004 (patch) | |
tree | 1a1e3f1ed0914d0917f5fb299703ae36d19c32c9 /spec/controllers/general_controller_spec.rb | |
parent | 11f45e188c59c8ad272a9fa611b387c54fcec80a (diff) |
Change order of requests on front page
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.)
Diffstat (limited to 'spec/controllers/general_controller_spec.rb')
-rw-r--r-- | spec/controllers/general_controller_spec.rb | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/spec/controllers/general_controller_spec.rb b/spec/controllers/general_controller_spec.rb index 00239c14e..6c9f8b88d 100644 --- a/spec/controllers/general_controller_spec.rb +++ b/spec/controllers/general_controller_spec.rb @@ -116,8 +116,13 @@ describe GeneralController, "when searching" do end it 'should list the newest successful request first' do - # Make sure the newest is listed first even if an older one has an even newer comment: + # Make sure the newest is listed first even if an older one + # has a newer comment or was reclassified more recently: # https://github.com/sebbacon/alaveteli/issues/370 + # + # This is a deliberate behaviour change, in that the + # previous behaviour (showing more-recently-reclassified + # requests first) was intentional. get :frontpage assigns[:request_events].first.info_request.should == info_requests(:another_boring_request) end |