Produced by Araxis Merge on 10/4/2017 8:04:42 AM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
| # | Location | File | Last Modified |
|---|---|---|---|
| 1 | rdk.zip\rdk\product\tests\acceptance-tests\features.arch | F202_ManualTest_IntergrateCDS.feature | Mon Aug 21 12:51:01 2017 UTC |
| 2 | rdk.zip\rdk\product\tests\acceptance-tests\features.arch | F202_ManualTest_IntergrateCDS.feature | Tue Oct 3 17:28:00 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 2 | 338 |
| Changed | 1 | 2 |
| Inserted | 0 | 0 |
| Removed | 0 | 0 |
| Whitespace | |
|---|---|
| Character case | Differences in character case are significant |
| Line endings | Differences in line endings (CR and LF characters) are ignored |
| CR/LF characters | Not shown in the comparison detail |
No regular expressions were active.
| 1 | # Team Eur opa | |
| 2 | ||
| 3 | @manual | |
| 4 | ||
| 5 | Feature: F 202 - Inte grate Clin ical Decis ion Suppor t | |
| 6 | ||
| 7 | @US5471_cd sadvice_li st @F202-3 @manual | |
| 8 | Scenario: List of ad vice is re turned wit h successf ul respons e | |
| 9 | Given a patient "EIGHT,PAT IENT" | |
| 10 | When a GET reque st is made using pos tman | |
| 11 | Then t he list of advice an d reminder is displa yed | |
| 12 | And th e successf ul respons e is retur ned | |
| 13 | ||
| 14 | @US5471_cd sadvice_de tail_200 @ F202-3 @ma nual | |
| 15 | Scenario: Detail of advice is returned w ith succes sful respo nse | |
| 16 | Given a patient "EIGHT,PAT IENT" | |
| 17 | When a GET reque st is made using pos tman | |
| 18 | Then t he detail of advice or reminde r is displ ayed | |
| 19 | And th e successf ul respons e is retur ned | |
| 20 | ||
| 21 | @US5471_cd sadvice_de tail_404 @ F202-3 @ma nual | |
| 22 | Scenario: A message is returne d with 404 response code | |
| 23 | Given a patient "EIGHT,PAT IENT" | |
| 24 | When a GET reque st is made using pos tman with random adv ice id | |
| 25 | Then t he message is return ed | |
| 26 | And th e 404 resp onse code is returne d | |
| 27 | ||
| 28 | @US5471_cd sadvice_de tail_404 @ F202-3 @ma nual | |
| 29 | Scenario: A message is returne d with 400 response code for i nvalid GET request | |
| 30 | Given a patient "EIGHT,PAT IENT" | |
| 31 | When a GET reque st is made using pos tman with random adv ice id | |
| 32 | Then t he message is return ed | |
| 33 | And th e 400 resp onse code is returne d | |
| 34 | ||
| 35 | @US5471_cd sschedule_ Get_200 @F 202-3 @man ual | |
| 36 | Scenario: A job is r eturned wi th success ful respon se | |
| 37 | Given a patient "EIGHT,PAT IENT" | |
| 38 | When a GET reque st is made using pos tman | |
| 39 | Then c ds job is returned | |
| 40 | And th e successf ul respons e is retur ned | |
| 41 | ||
| 42 | @US5471_cd sschedule_ Get_404 @F 202-3 @man ual | |
| 43 | Scenario: The 404 re sponse cod e is retur ned with i nvalid req uest | |
| 44 | Given a patient "EIGHT,PAT IENT" | |
| 45 | When i nvalid GET request i s made usi ng postman | |
| 46 | Then t he 404 res ponse code is return ed | |
| 47 | ||
| 48 | @US5471_cd sschedule_ Post_201 @ F202-3 @ma nual | |
| 49 | Scenario: A message is returne d with cre ated respo nse code 2 01 for POS T | |
| 50 | Given a patient "EIGHT,PAT IENT" | |
| 51 | When a POST requ est is mad e using po stman | |
| 52 | Then t he message is return ed | |
| 53 | And th e created response c ode 201 is returned | |
| 54 | ||
| 55 | @US5471_cd sschedule_ Post_400 @ F202-3 @ma nual | |
| 56 | Scenario: An error m essage is returned w ith 400 re sponse cod e for POST | |
| 57 | Given a patient "EIGHT,PAT IENT" | |
| 58 | When a n invalid POST reque st is made using pos tman | |
| 59 | Then t he error m essage is returned | |
| 60 | And th e 400 resp onse code is returne d | |
| 61 | ||
| 62 | @US5471_cd sschedule_ Put_200 @F 202-3 @man ual | |
| 63 | Scenario: A message is returne d with 200 response code for P UT | |
| 64 | Given a patient "EIGHT,PAT IENT" | |
| 65 | When a PUT reque st is made using pos tman | |
| 66 | Then t he message is return ed | |
| 67 | And th e successf ul respons e is retur ned | |
| 68 | ||
| 69 | @US5471_cd sschedule_ Put_400 @F 202-3 @man ual | |
| 70 | Scenario: An error m essage is returned w ith 400 re sponse cod e for PUT | |
| 71 | Given a patient "EIGHT,PAT IENT" | |
| 72 | When a n invalid PUT reques t is made using post man | |
| 73 | Then t he error m essage is returned | |
| 74 | And th e 400 resp onse code is returne d | |
| 75 | ||
| 76 | @US5471_cd sschedule_ Delete_200 @F202-3 @ manual | |
| 77 | Scenario: A message is returne d with 200 response code for D ELETE | |
| 78 | Given a patient "EIGHT,PAT IENT" | |
| 79 | When a DELETE re quest is m ade using postman | |
| 80 | Then t he message is return ed | |
| 81 | And th e successf ul respons e is retur ned | |
| 82 | ||
| 83 | @US5471_cd sschedule_ Delete_404 @F202-3 @ manual | |
| 84 | Scenario: The 404 re sponse cod e is retur ned with i nvalid req uest for D ELETE | |
| 85 | Given a patient "EIGHT,PAT IENT" | |
| 86 | When i nvalid DEL ETE reques t is made using post man for ne w job | |
| 87 | Then t he 404 res ponse code is return ed | |
| 88 | ||
| 89 | @US5471_cd sworkprodu ct_Post_20 1 @F202-3 @manual | |
| 90 | Scenario: A message is returne d with cre ated respo nse code 2 01 for wor k product | |
| 91 | Given a patient "EIGHT,PAT IENT" | |
| 92 | When a POST requ est is mad e using po stman to c reate a wo rk product | |
| 93 | Then t he message is return ed | |
| 94 | And th e created response c ode 201 is returned | |
| 95 | ||
| 96 | @US5471_cd sworkprodu ct_Get_200 @F202-3 @ manual | |
| 97 | Scenario: A work pro duct is re turned wit h successf ul respons e | |
| 98 | Given a patient "EIGHT,PAT IENT" | |
| 99 | When a GET reque st is made using pos tman for w ork produc t | |
| 100 | Then w ork produc t is retur ned | |
| 101 | And th e successf ul respons e is retur ned | |
| 102 | ||
| 103 | @US5471_cd sworkprodu ctslist_Ge t_200 @F20 2-3 @manua l | |
| 104 | Scenario: A work pro ducts list is return ed with su ccessful r esponse | |
| 105 | Given a patient "EIGHT,PAT IENT" | |
| 106 | When a GET reque st is made using pos tman for w ork produc ts list | |
| 107 | Then w ork produc ts list is returned | |
| 108 | And th e successf ul respons e is retur ned | |
| 109 | ||
| 110 | @US5471_cd sworkprodu ct_Get_404 @F202-3 @ manual | |
| 111 | Scenario: A message is returne d with 404 response code when requesting work prod uct with i nvalid id | |
| 112 | Given a patient "EIGHT,PAT IENT" | |
| 113 | When a GET reque st is made using pos tman with invalid wo rk product id | |
| 114 | Then t he message is return ed | |
| 115 | And th e 404 resp onse code is returne d | |
| 116 | ||
| 117 | @US5471_cd sworkprodu ct_Put_200 @F202-3 @ manual | |
| 118 | Scenario: A message is returne d with 200 response code for P UT work pr oduct | |
| 119 | Given a patient "EIGHT,PAT IENT" | |
| 120 | When a PUT reque st is made using pos tman to up date a wor k product | |
| 121 | Then t he message is return ed | |
| 122 | And 20 0 response code is r eturned | |
| 123 | ||
| 124 | @US5471_cd sworkprodu ct_Put_404 @F202-3 @ manual | |
| 125 | Scenario: A message is returne d with 404 response code when requesting to update work prod uct with i nvalid id | |
| 126 | Given a patient "EIGHT,PAT IENT" | |
| 127 | When a PUT reque st is made using pos tman with invalid wo rk product id | |
| 128 | Then t he message is return ed | |
| 129 | And th e 404 resp onse code is returne d | |
| 130 | ||
| 131 | @US5471_cd sworkprodu ct_Delete_ 200 @F202- 3 @manual | |
| 132 | Scenario: A message is returne d with 200 response code for D elete work product | |
| 133 | Given a patient "EIGHT,PAT IENT" | |
| 134 | When a DELETE re quest is m ade using postman to delete a work produ ct | |
| 135 | Then t he message is return ed | |
| 136 | And 20 0 response code is r eturned | |
| 137 | ||
| 138 | @US5471_cd sworkprodu ct_Put_404 @F202-3 @ manual | |
| 139 | Scenario: A message is returne d with 404 response code when requesting to delete work prod uct with i nvalid id | |
| 140 | Given a patient "EIGHT,PAT IENT" | |
| 141 | When a DELETE re quest is m ade using postman wi th invalid work prod uct id | |
| 142 | Then t he message is return ed | |
| 143 | And th e 404 resp onse code is returne d | |
| 144 | ||
| 145 | @US5471_cd ssubscript ion_Get_20 0 @F202-3 @manual | |
| 146 | Scenario: Subscripti ons are re turned wit h successf ul respons e | |
| 147 | Given a patient "EIGHT,PAT IENT" | |
| 148 | When a GET reque st is made using pos tman for s ubscriptio ns | |
| 149 | Then a ll subscri ptions are returned | |
| 150 | And th e successf ul respons e is retur ned | |
| 151 | ||
| 152 | @US5471_cd ssubscript ions_Put_2 00 @F202-3 @manual | |
| 153 | Scenario: A message is returne d with 200 response code for P UT subscri ptions | |
| 154 | Given a patient "EIGHT,PAT IENT" | |
| 155 | When a PUT reque st is made using pos tman to up date subsc riptions | |
| 156 | Then t he message is return ed | |
| 157 | And 20 0 response code is r eturned | |
| 158 | ||
| 159 | @US5471_cd sworkprodu ct_Delete_ 200 @F202- 3 @manual | |
| 160 | Scenario: A message is returne d with 200 response code for D elete subs criptions | |
| 161 | Given a patient "EIGHT,PAT IENT" | |
| 162 | When a DELETE re quest is m ade using postman to delete su bscription s | |
| 163 | Then t he message is return ed | |
| 164 | And 20 0 response code is r eturned | |
| 165 | ||
| 166 | @US8534_vi tals_useca se @manual | |
| 167 | Scenario: Pass histo ric height , weight a nd date in vitals us e case | |
| 168 | Given a patient "E IGHT,PATIE NT" | |
| 169 | When a POS T request "http:// IP /cds-resul ts-service /cds/invok eRules" is made for vitals via postman w ith contex t "{"conte xt":{"loca tion":{"en tityType": "Location" ,"id":"Loc ation1","n ame":"Test Location" },"subject ":{"entity Type":"Sub ject","id" :"9E7A;253 ","name":" TestSubjec t"},"user" :{"entityT ype":"User ","id":"Id 1","name": "Tester"}} ,"paramete rs":{"Weig ht":{"reso urceType": "Observati on","code" :{"coding" :[{"system ":"http:// loinc.org" ,"code":"2 9463-7"}]} ,"valueQua ntity":{"v alue":295, "units":"l b"},"issue d":"2015-0 6-11T13:24 :21.080-07 :00","comm ents":"Com ment","sta tus":"prel iminary"}, "Height":{ "resourceT ype":"Obse rvation"," code":{"co ding":[{"s ystem":"ht tp://loinc .org","cod e":"8302-2 "}]},"valu eQuantity" :{"value": 95,"units" :"inches"} ,"issued": "2004-03-3 0T21:54:42 -00:00","c omments":" Comment"," status":"p reliminary "}},"targe t":{"inten tsSet":["V italsValid ation"],"m ode":"Norm al","type" :"Direct"} }" | |
| 170 | Then adv ices are r eturned in the respo nse for he ight and w eight |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.