Skip to content
This repository was archived by the owner on Mar 4, 2025. It is now read-only.

SUP-2582, Upcoming SRMs should be ordered by most recent date #542

Merged
merged 1 commit into from
Nov 6, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions app/my-srms/my-srms.spec.js
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ describe('My SRMs Controller', function() {
// by default it should load upcoming SRMs
expect(mySRMs.statusFilter).to.equal('past');
expect(mySRMs.srms).to.exist;
expect(mySRMs.orderBy).to.equal('endDate');
expect(mySRMs.orderBy).to.equal('codingEndAt');
expect(mySRMs.reverseOrder).to.be.true;
expect(mySRMs.srms.length).to.equal(srms.length - 1);
expect(spy.withArgs(0).calledOnce);
Expand Down Expand Up @@ -107,7 +107,7 @@ describe('My SRMs Controller', function() {
it('upcoming SRMs should be fetched', function() {
expect(mySRMs.srms).to.exist;
expect(mySRMs.statusFilter).to.equal('future');
expect(mySRMs.orderBy).to.equal('startDate');
expect(mySRMs.orderBy).to.equal('codingStartAt');
expect(mySRMs.reverseOrder).to.be.false;
expect(mySRMs.srms).to.exist;
// should have one extra srm for past filter as per mocked method
Expand Down