Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Change custom coverage tests in accordance with the new back-end response

Description

1. Go to a selected resource
2. Add custom coverage dates (see below screenshot)


3. Save record
4. Edit record
5. Problem. Notice that the custom coverage dates order change from descending to ascending


6. If you update custom coverage dates w/o changing order then use gets this

Expected order: Custom Coverage date order should not change. RM API only accepts custom coverage dates in descending order

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

maksym_dryha March 14, 2019 at 9:39 AM

thank you! Some minor changes to UI tests will be required after back-end guys start returning custom coverages ordered correctly

Khalilah Gambrell March 13, 2019 at 11:08 AM

maksym_dryha March 13, 2019 at 10:14 AM

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

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 2, 2019 at 5:50 PM
Updated March 18, 2019 at 2:31 PM
Resolved March 18, 2019 at 2:31 PM
TestRail: Cases
TestRail: Runs