Investigate parameter error responses handling for GET eholdings/providers request

Priority

Labels

Environment

None

Template

None

Description

During the demo session, we have found that responses from the Java module do not reflect responses from the Ruby module for the following cases:

  • in case of empty value for parameter

    for

    we receive different responces. For the Ruby module


    and for Java module

  • parameter

    for

    is also produce diffrerent responces
    for Ruby:


    and for Java:


    Also, there is a concern for the following issue:

  • parameter sort vs. orderby for the search query are treated equally and it is not clear what parameter is an appropriate
    example

Development Team

None

Release

None

Story Points

Sprint

Attachments

6

Checklist

hide

TestRail: Results

Activity

Show:

Andrii Paias November 12, 2018 at 10:58 AM
Edited

Fixed in this PR.
1)First query:


2)Second query:


3) — parameter sort vs. orderby for the search query are treated equally and it is not clear what parameter is an appropriate example

mod-kb-ebsco-java module only has parameter sort, if sort is missing it defaults to relevance,
orderby parameter is ignored, same as any other unknown parameter

Done

Details

Assignee

Reporter

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 8, 2018 at 4:47 PM
Updated November 15, 2018 at 10:05 AM
Resolved November 14, 2018 at 1:44 PM
TestRail: Cases
TestRail: Runs