Custom Coverages are not returned in descending order

Description

To address UIEH-666, we need the backend to return custom coverage date in descending order. Please see the below statement

Per : The reason of the issue is that backend sends the custom coverages sorted in a wrong order. It's actually strange. Back-end requires front-end to send custom coverages in descending order, but sends it to front-end in ascending order.
I investigated ways to resolve the issue on the front-end side. All of them are kind of clumsy and strange. I think this should be fixed on the back-end side so that we have consistent requirements on sending and receiving custom coverages data

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:
Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 13, 2019 at 11:08 AM
Updated March 21, 2019 at 2:12 PM
Resolved March 21, 2019 at 2:12 PM
TestRail: Cases
TestRail: Runs