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 | FX_Activities_Patient.feature | Mon Aug 21 12:51:01 2017 UTC |
| 2 | rdk.zip\rdk\product\tests\acceptance-tests\features | FX_Activities_Patient.feature | Tue Oct 3 20:20:40 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 63 | 394 |
| Changed | 62 | 130 |
| 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 | @F_activit ies @F_act ivities_pa tient @JBP M @future | |
| 2 | Feature: A ctivities | |
| 3 | ||
| 4 | @F_activit ies_patien t @F_activ ities_pati ent_1 | |
| 5 | Scenario: Patient vi ew, activi ty applet requests " Activities related t o me" and display on ly "open" | |
| 6 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 7 | When the clicent r equests op en activit ies for th e patient context | |
| 8 | | para meter | va lue | | |
| 9 | | crea tedByMe|tr ue| | |
| 10 | | inte ndedForMeA ndMyTeams| true| | |
| 11 | | pid| R E D A CTED ;3| | |
| 12 | Then a s uccessful response i s returned | |
| 13 | ||
| 14 | ||
| 15 | @F_activit ies_patien t @F_activ ities_pati ent_2 | |
| 16 | Scenario: Patient vi ew, activi ty applet requests " Intended f or me or m y team(s)" and displ ay only "o pen" | |
| 17 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 18 | When the clicent r equests op en activit ies for th e patient context | |
| 19 | | para meter | va lue | | |
| 20 | | inte ndedForMeA ndMyTeams| true| | |
| 21 | | pid| R E D A CTED ;3| | |
| 22 | Then a s uccessful response i s returned | |
| 23 | ||
| 24 | @F_activit ies_patien t @F_activ ities_pati ent_3 | |
| 25 | Scenario: Patient vi ew, activi ty applet requests " Created by me" and d isplay onl y "open" | |
| 26 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 27 | When the clicent r equests op en activit ies for th e patient context | |
| 28 | | para meter | va lue | | |
| 29 | | crea tedByMe|tr ue| | |
| 30 | | pid| R E D A CTED ;3| | |
| 31 | Then a s uccessful response i s returned | |
| 32 | ||
| 33 | @F_activit ies_patien t @F_activ ities_pati ent_4 | |
| 34 | Scenario: Patient vi ew, activi ty applet requests " All Activi ties" and display on ly "open" | |
| 35 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 36 | When the clicent r equests op en activit ies for th e patient context | |
| 37 | | para meter | va lue | | |
| 38 | | pid| R E D A CTED ;3| | |
| 39 | Then a s uccessful response i s returned | |
| 40 | ||
| 41 | @F_activit ies_patien t @F_activ ities_pati ent_5 @DE6 524 | |
| 42 | Scenario: Patient vi ew, activi ty applet requests " All Activi ties" and display on ly "closed " | |
| 43 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 44 | When the clicent r equests cl osed activ ities for the patien t context | |
| 45 | | para meter | va lue | | |
| 46 | | pid| R E D A CTED ;3| | |
| 47 | Then a s uccessful response i s returned | |
| 48 | ||
| 49 | @F_activit ies_patien t @F_activ ities_pati ent_6 @DE6 524 | |
| 50 | Scenario: Patient vi ew, activi ty applet requests " Created by me" and d isplay onl y "closed" | |
| 51 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 52 | When the clicent r equests cl osed activ ities for the patien t context | |
| 53 | | para meter | va lue | | |
| 54 | | crea tedByMe|tr ue| | |
| 55 | | pid| R E D A CTED ;3| | |
| 56 | Then a s uccessful response i s returned | |
| 57 | ||
| 58 | @F_activit ies_patien t @F_activ ities_pati ent_7 @DE 6524 | |
| 59 | Scenario: Patient vi ew, activi ty applet requests " Intended f or me or m y team(s)" and displ ay only "c losed" | |
| 60 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 61 | When the clicent r equests cl osed activ ities for the patien t context | |
| 62 | | para meter | va lue | | |
| 63 | | inte ndedForMeA ndMyTeams| true| | |
| 64 | | pid| R E D A CTED ;3| | |
| 65 | Then a s uccessful response i s returned | |
| 66 | ||
| 67 | @F_activit ies_patien t @F_activ ities_pati ent_8 @DE 6524 | |
| 68 | Scenario: Patient vi ew, activi ty applet requests " Activities related t o me" and display on ly "closed " | |
| 69 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 70 | When the clicent r equests cl osed activ ities for the patien t context | |
| 71 | | para meter | va lue | | |
| 72 | | crea tedByMe|tr ue| | |
| 73 | | inte ndedForMeA ndMyTeams| true| | |
| 74 | | pid| R E D A CTED ;3| | |
| 75 | Then a s uccessful response i s returned | |
| 76 | ||
| 77 | @F_activit ies_patien t @F_activ ities_pati ent_9 @DE 6524 | |
| 78 | Scenario: Patient vi ew, activi ty applet requests " All Activi ties" and display on ly "open a nd closed" | |
| 79 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 80 | When the clicent r equests op en and clo sed activi ties for t he patient context | |
| 81 | | para meter | va lue | | |
| 82 | | pid| R E D A CTED ;3| | |
| 83 | Then a s uccessful response i s returned | |
| 84 | ||
| 85 | @F_activit ies_patien t @F_activ ities_pati ent_10 @D E6524 | |
| 86 | Scenario: Patient vi ew, activi ty applet requests " Created by me" and d isplay onl y "open an d closed" | |
| 87 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 88 | When the clicent r equests op en and clo sed activi ties for t he patient context | |
| 89 | | para meter | va lue | | |
| 90 | | crea tedByMe|tr ue| | |
| 91 | | pid| R E D A CTED ;3| | |
| 92 | Then a s uccessful response i s returned | |
| 93 | ||
| 94 | @F_activit ies_patien t @F_activ ities_pati ent_11 @D E6524 | |
| 95 | Scenario: Patient vi ew, activi ty applet requests " Intended f or me or m y team(s)" and displ ay only "o pen and cl osed" | |
| 96 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 97 | When the clicent r equests op en and clo sed activi ties for t he patient context | |
| 98 | | para meter | va lue | | |
| 99 | | inte ndedForMeA ndMyTeams| true| | |
| 100 | | pid| R E D A CTED ;3| | |
| 101 | Then a s uccessful response i s returned | |
| 102 | ||
| 103 | @F_activit ies_patien t @F_activ ities_pati ent_12 @D E6524 | |
| 104 | Scenario: Patient vi ew, activi ty applet requests " Activities related t o me" and display on ly "open a nd closed" | |
| 105 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 106 | When the clicent r equests op en and clo sed activi ties for t he patient context | |
| 107 | | para meter | va lue | | |
| 108 | | crea tedByMe|tr ue| | |
| 109 | | inte ndedForMeA ndMyTeams| true| | |
| 110 | | pid| R E D A CTED ;3| | |
| 111 | Then a s uccessful response i s returned | |
| 112 | ||
| 113 | @add_activ ity_myteam | |
| 114 | Scenario: Client can add an ac tivity for my teams | |
| 115 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 116 | And the client has the curre nt deploym entid | |
| 117 | And the user tdnur se has sta rted an ac tivity for my teams with param eters | |
| 118 | | param eter | value | | |
| 119 | | patient_ facility | R E D A CTED | | |
| 120 | | patie nt_id | 3 | | |
| 121 | | urgen cy | 9 | | |
| 122 | | facil ity | 500 | | |
| 123 | | authorFa c | R E D A CTED | | |
| 124 | | autho rId | 100000 00016 | | |
| 125 | | autho rName | TDNURS E,ONE | | |
| 126 | | assigned ToFac | R E D A CTED | | |
| 127 | | full_ assignedTo | [TM:Ph ysical The rapy - 3rd floor - K DK(1130)/T R:NURSE PR ACTITIONER (24)] | | |
| 128 | | team code | 1130 | | |
| 129 | | team name | Physic al Therapy - 3rd flo or - KDK | | |
| 130 | | assig ned roles code | 24 | | |
| 131 | | assig ned roles name | NUR SE PRACTIT IONER | | |
| 132 | And a su ccessful r esponse is returned | |
| 133 | When the u ser " PW " requests open acti vities for the patie nt context | |
| 134 | | para meter | va lue | | |
| 135 | | pid| R E D A CTED ;3| | |
| 136 | Then a s uccessful response i s returned | |
| 137 | Then the activity response d oes contai n the titl e | |
| 138 | When the u ser " PW " requests open acti vities for the patie nt context | |
| 139 | | para meter | va lue | | |
| 140 | | crea tedByMe|tr ue| | |
| 141 | | pid| R E D A CTED ;3| | |
| 142 | Then a s uccessful response i s returned | |
| 143 | Then the activity response d oes not co ntain the title | |
| 144 | When the u ser " PW " requests open acti vities for the patie nt context | |
| 145 | | para meter | va lue | | |
| 146 | | inte ndedForMeA ndMyTeams| true| | |
| 147 | | pid| R E D A CTED ;3| | |
| 148 | Then a s uccessful response i s returned | |
| 149 | Then the activity response d oes not co ntain the title | |
| 150 | ||
| 151 | @add_activ ity_anytea m | |
| 152 | Scenario: Client can add an ac tivity for any teams | |
| 153 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 154 | And the client has the curre nt deploym entid | |
| 155 | And the user tdnur se has sta rted an ac tivity for any team with param eters | |
| 156 | | param eter | value | | |
| 157 | | patient_ facility | R E D A CTED | | |
| 158 | | patie nt_id | 3 | | |
| 159 | | urgen cy | 9 | | |
| 160 | | facil ity | 500 | | |
| 161 | | authorFa c | R E D A CTED | | |
| 162 | | autho rId | 100000 00016 | | |
| 163 | | autho rName | TDNURS E,ONE | | |
| 164 | | assigned ToFac | R E D A CTED | | |
| 165 | | full_ assignedTo | [TM:Ot her Primar y Care - P AN(1132)/T R:RESIDENT (PHYSICIA N)(48)] | | |
| 166 | | team code | 1132 | | |
| 167 | | team name | Other Primary Ca re - PAN | | |
| 168 | | assig ned roles code | 48 | | |
| 169 | | assig ned roles name | RES IDENT (PHY SICIAN) | | |
| 170 | And a su ccessful r esponse is returned | |
| 171 | When the u ser " PW " requests open acti vities for the patie nt context | |
| 172 | | para meter | va lue | | |
| 173 | | pid| R E D A CTED ;3| | |
| 174 | Then a s uccessful response i s returned | |
| 175 | Then the activity response d oes contai n the titl e | |
| 176 | ||
| 177 | @add_activ ity_me | |
| 178 | Scenario: Client ca n add an a ctivity as signed to me | |
| 179 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 180 | And the client has the curre nt deploym entid | |
| 181 | And the user tdnur se has sta rted an ac tivity ass igned to m e with par ameters | |
| 182 | | param eter | value | | |
| 183 | | patient_ facility | R E D A CTED | | |
| 184 | | patie nt_id | 3 | | |
| 185 | | assigned ToFac | R E D A CTED | | |
| 186 | | assig nedToUser | 100000 00270 | | |
| 187 | | full_ass ignedTo | R E D A CTED ;100000002 70 | | |
| 188 | | authorFa c | R E D A CTED | | |
| 189 | | autho rId | 100000 00016 | | |
| 190 | | autho rName | TDNURS E,ONE | | |
| 191 | And a su ccessful r esponse is returned | |
| 192 | ||
| 193 | @add_activ ity_person | |
| 194 | Scenario: When the client req uests acti vities "Cr eated by m e", then c lient only receives activities they have created | |
| 195 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 196 | And the client has the curre nt deploym entid | |
| 197 | And the user tdnur se has sta rted an ac tivity ass igned to a person wi th paramet ers | |
| 198 | | param eter | value | | |
| 199 | | patient_ facility | R E D A CTED | | |
| 200 | | patie nt_id | 3 | | |
| 201 | # | urge ncy | 9 | | |
| 202 | # | faci lity | 500 | | |
| 203 | # | faci lity name | PANOR AMA (PAN) COLVILLE, WA | | |
| 204 | | assigned ToFac | R E D A CTED | | |
| 205 | | assig nedToUser | 100000 00270 | | |
| 206 | | full_ass ignedTo | R E D A CTED ;100000002 70 | | |
| 207 | | authorFa c | R E D A CTED | | |
| 208 | | autho rId | 100000 00016 | | |
| 209 | | autho rName | TDNURS E,ONE | | |
| 210 | And a su ccessful r esponse is returned | |
| 211 | When the u ser " PW " requests open acti vities for the patie nt context | |
| 212 | | para meter | va lue | | |
| 213 | | crea tedByMe|tr ue| | |
| 214 | | pid| R E D A CTED ;3| | |
| 215 | Then a s uccessful response i s returned | |
| 216 | Then the activity response d oes not co ntain the title | |
| 217 | And the ac tivity res ponse only contains activities started b y REDACT | |
| 218 | When the u ser " R E D A CTED ;1tdnurse" requests open activ ities for the patien t context | |
| 219 | | para meter | va lue | | |
| 220 | | crea tedByMe|tr ue| | |
| 221 | | pid| R E D A CTED ;3| | |
| 222 | Then a s uccessful response i s returned | |
| 223 | Then the activity response d oes contai n the titl e | |
| 224 | And the activity r esponse on ly contain s activiti es started by tdnurs e | |
| 225 | ||
| 226 | @add_activ ity_patien tteam | |
| 227 | Scenario: Client can add an ac tivity for Patients teams | |
| 228 | Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API | |
| 229 | And the client has the curre nt deploym entid | |
| 230 | And the user tdnur se has sta rted an ac tivity for Patient's Teams wit h paramete rs | |
| 231 | | param eter | value | | |
| 232 | | patient_ facility | R E D A CTED | | |
| 233 | | patie nt_id | 3 | | |
| 234 | | urgen cy | 9 | | |
| 235 | | facil ity | 500 | | |
| 236 | | authorFa c | R E D A CTED | | |
| 237 | | autho rId | 100000 00016 | | |
| 238 | | autho rName | TDNURS E,ONE | | |
| 239 | | assigned ToFac | R E D A CTED | | |
| 240 | | full_ assignedTo | [TM:KO DAK Primar y Care - K DK(1134)/T R:RESIDENT (PHYSICIA N)(48)] | | |
| 241 | | team code | 1134 | | |
| 242 | | team name | KODAK Primary Ca re - KDK | | |
| 243 | | assig ned roles code | 48 | | |
| 244 | | assig ned roles name | RES IDENT (PHY SICIAN) | | |
| 245 | And a su ccessful r esponse is returned | |
| 246 | When the user " PW " requests open acti vities for the patie nt context | |
| 247 | | para meter | va lue | | |
| 248 | | pid| R E D A CTED ;3| | |
| 249 | Then a s uccessful response i s returned | |
| 250 | Then the activity response d oes contai n the titl e | |
| 251 | When the u ser " PW " requests open acti vities for the patie nt context | |
| 252 | | para meter | va lue | | |
| 253 | | crea tedByMe|tr ue| | |
| 254 | | pid| R E D A CTED ;3| | |
| 255 | Then a s uccessful response i s returned | |
| 256 | Then the activity response d oes not co ntain the title | |
| 257 | When the u ser " PW " requests open acti vities for the patie nt context | |
| 258 | | para meter | va lue | | |
| 259 | | inte ndedForMeA ndMyTeams| true| | |
| 260 | | pid| R E D A CTED ;3| | |
| 261 | Then a s uccessful response i s returned | |
| 262 | Then the activity response d oes not co ntain the title |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.