Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong order of array for revision history of versioned composition #870

Open
6 tasks
gregorberger opened this issue May 20, 2022 · 1 comment
Open
6 tasks
Labels
bug Something isn't working

Comments

@gregorberger
Copy link

Steps to reproduce

robot -t "3. Get Correct Ordered Revision History of Versioned Composition Of Existing EHR With Two Composition Versions (JSON)" robot/COMPOSITION_TESTS/GET_VERSIONED_COMPOSITION/"C.6__B)_Get_Versioned_COMPOSITION_Revision_History".robot

Actual result

a1602e08-8b57-418f-a327-1d50ecd3e743::default::1 != a1602e08-8b57-418f-a327-1d50ecd3e743::default::2

Expected result (Acceptance Criteria)

The first version_id in array should be the most recent one. As you can see in specifications:
https://specifications.openehr.org/releases/RM/latest/common.html#_revision_history_class

items: List<REVISION_HISTORY_ITEM>
The items in this history in most-recent-last order.

Definition of Done

  • The defect is checked by an unit or an integration test (Robot)
  • Merge Request approved
  • Unit tests passed
  • Build without errors
  • Release notes prepared
  • No additional runtime warnings
@gregorberger gregorberger added the bug Something isn't working label May 20, 2022
@vladislavploaia
Copy link
Contributor

vladislavploaia commented May 23, 2022

Indeed @gregorberger,
Version ID value is ordered ASC, not as per requirements:
image
Robot script created.
Jira ticket: https://jira.vitagroup.ag/browse/CDR-413
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants