Produced by Araxis Merge on 6/22/2018 1:31:14 PM 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 | Fri Jun 22 18:31:12 2018 UTC | ||
| 2 | v1603_release_60.zip\Docs | 178061 - Build 1.6 - PACT Regression Testing.docx | Thu Jun 21 19:25:09 2018 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 0 | 0 |
| Changed | 0 | 0 |
| Inserted | 1 | 536 |
| 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 | 178061: Bu ild 1.6 - PACT Regre ssion Test ing | |||||
| 2 | ||||||
| 3 | Creation D ate: May 9, 2018 8: 50:57 AM ( UTC-05:00) Last Modif ied: May 9 , 2018 8:5 0:59 AM (U TC-05:00) | |||||
| 4 | ||||||
| 5 | State: Dra ft | |||||
| 6 | Originator : Pribyl, Brent (BA H)Owner: | |||||
| 7 | Type: Manu al | |||||
| 8 | Test Data: Unassigne d | |||||
| 9 | ||||||
| 10 | Descriptio n: Build 1.6 - PACT Regressio n Testing | |||||
| 11 | ||||||
| 12 | Summary | |||||
| 13 | ||||||
| 14 | Categories | |||||
| 15 | Function: Unassigned Test Phas e: Unassig ned | |||||
| 16 | ||||||
| 17 | Formal Rev iew | |||||
| 18 | ||||||
| 19 | ||||||
| 20 | General Co mments | |||||
| 21 | ||||||
| 22 | Manual Ste ps | |||||
| 23 | ||||||
| 24 | ||||||
| 25 | Step 1 | |||||
| 26 | Execution Step | |||||
| 27 | ||||||
| 28 | Descriptio n* | |||||
| 29 | In the VCC M CRM appl ication, l og-in to t he system as an FTP PACT (Team let 12) te st user (o pen USD) | |||||
| 30 | ||||||
| 31 | Expected R esults | |||||
| 32 | The user i s able to log-in as a FTP PACT test user Comments | |||||
| 33 | Validates | |||||
| 34 | ||||||
| 35 | Attachment s | |||||
| 36 | ||||||
| 37 | ||||||
| 38 | Step 2 | |||||
| 39 | Execution Step | |||||
| 40 | ||||||
| 41 | Descriptio n* | |||||
| 42 | Upon the V istA crede ntialing p rompt, ent er in your test cred entials (i n QA for 9 91 - SLC). | |||||
| 43 | ||||||
| 44 | Expected R esults | |||||
| 45 | The user i s propmted to enter their acce ss, verify and eSig code and t he user is able to s ucessfully log in to VistA. Co mments | |||||
| 46 | Validates | |||||
| 47 | ||||||
| 48 | Attachment s | |||||
| 49 | ||||||
| 50 | ||||||
| 51 | Step 3 | |||||
| 52 | Execution Step | |||||
| 53 | ||||||
| 54 | ||||||
| 55 | ||||||
| 56 | Descriptio n* | |||||
| 57 | Click on M y Work fro m the USD ribbon | |||||
| 58 | ||||||
| 59 | Expected R esults | |||||
| 60 | The user i s directed to the wo rk queue a nd able to view requ ests to be worked on Comments | |||||
| 61 | Validates | |||||
| 62 | ||||||
| 63 | Attachment s | |||||
| 64 | ||||||
| 65 | ||||||
| 66 | Step 4 | |||||
| 67 | Execution Step | |||||
| 68 | ||||||
| 69 | Descriptio n* | |||||
| 70 | Locate the request r outed from R1.4 CCA regression test for the FTP PA CT Test Us er (reques t for Geor ge VCCMAlb ert) | |||||
| 71 | ||||||
| 72 | Expected R esults | |||||
| 73 | The user i s able to validate t hat the re quest from the Regre ssion CCA test is ro uted corre ctly to th e PACT tea m. Comment s | |||||
| 74 | Validates | |||||
| 75 | ||||||
| 76 | Attachment s | |||||
| 77 | ||||||
| 78 | ||||||
| 79 | Step 5 | |||||
| 80 | Execution Step | |||||
| 81 | ||||||
| 82 | Descriptio n* | |||||
| 83 | Double cli ck to open the reque st | |||||
| 84 | ||||||
| 85 | Expected R esults | |||||
| 86 | The reques t is opene d along wi th Veteran Info and Medical Ch arts tabs Comments | |||||
| 87 | Validates | |||||
| 88 | ||||||
| 89 | Attachment s | |||||
| 90 | ||||||
| 91 | ||||||
| 92 | Step 6 | |||||
| 93 | Execution Step | |||||
| 94 | ||||||
| 95 | Descriptio n* | |||||
| 96 | Click on ' Assign to Self' on t he request | |||||
| 97 | ||||||
| 98 | Expected R esults | |||||
| 99 | The user i s able to assign the request t o themselv es - the o wner field is set as the curre nt user Co mments | |||||
| 100 | Validates | |||||
| 101 | ||||||
| 102 | Attachment s | |||||
| 103 | ||||||
| 104 | ||||||
| 105 | ||||||
| 106 | Step 7 | |||||
| 107 | Execution Step | |||||
| 108 | ||||||
| 109 | Descriptio n* | |||||
| 110 | Click on C reate Prog ress Note on the req uest | |||||
| 111 | ||||||
| 112 | Expected R esults | |||||
| 113 | A new tab is opended to enter in progres s note Com ments | |||||
| 114 | Validates | |||||
| 115 | ||||||
| 116 | Attachment s | |||||
| 117 | ||||||
| 118 | ||||||
| 119 | Step 8 | |||||
| 120 | Execution Step | |||||
| 121 | ||||||
| 122 | Descriptio n* | |||||
| 123 | Select Can cel on the note pop- up to crea te a histo rical note | |||||
| 124 | ||||||
| 125 | Expected R esults | |||||
| 126 | A new hist orical not e is creat ed. In the note text , the call back phone number is populated Comments | |||||
| 127 | Validates | |||||
| 128 | ||||||
| 129 | Attachment s | |||||
| 130 | ||||||
| 131 | ||||||
| 132 | Step 9 | |||||
| 133 | Execution Step | |||||
| 134 | ||||||
| 135 | Descriptio n* | |||||
| 136 | On the his torical no te validat e the foll owing | |||||
| 137 | ||||||
| 138 | The Select ed Notes g rid, Refre sh Notes b utton and the Apply Selected N otes butto n is now p laced unde r the Note Detail* f ield | |||||
| 139 | ||||||
| 140 | Users will be presen ted with t he General and Histo rical Note sections for comple tion | |||||
| 141 | ||||||
| 142 | All sectio ns/tabs ar e expanded | |||||
| 143 | The notes from the i nteraction and the r equest are available in the In teraction and Reques t Notes se ction Expe cted Resul ts | |||||
| 144 | The user i s able to validate t he histori cal note f orm Commen ts | |||||
| 145 | Validates | |||||
| 146 | ||||||
| 147 | Attachment s | |||||
| 148 | ||||||
| 149 | ||||||
| 150 | Step 10 | |||||
| 151 | Execution Step | |||||
| 152 | ||||||
| 153 | ||||||
| 154 | ||||||
| 155 | Descriptio n* | |||||
| 156 | Select a n ote from t he section and click on 'Apply Selected Note' | |||||
| 157 | ||||||
| 158 | Expected R esults | |||||
| 159 | The note t ext is pop ulated and editable in the pro gress note text fiel d Comments | |||||
| 160 | Validates | |||||
| 161 | ||||||
| 162 | Attachment s | |||||
| 163 | ||||||
| 164 | ||||||
| 165 | Step 11 | |||||
| 166 | Execution Step | |||||
| 167 | ||||||
| 168 | Descriptio n* Click o n Save | |||||
| 169 | note: 'Sav e to Vista /CPRS will have to b e tested i n R1.4 Int egration t est case f or the ind ividual us er logged in with VI STA access ' Expected Results | |||||
| 170 | The progre ss note in fo is save d in CRM C omments | |||||
| 171 | Validates | |||||
| 172 | ||||||
| 173 | Attachment s | |||||
| 174 | ||||||
| 175 | ||||||
| 176 | Step 12 | |||||
| 177 | Execution Step | |||||
| 178 | ||||||
| 179 | Descriptio n* | |||||
| 180 | Close out the progre ss note | |||||
| 181 | ||||||
| 182 | Expected R esults | |||||
| 183 | The progre ss note is closed Co mments | |||||
| 184 | Validates | |||||
| 185 | ||||||
| 186 | Attachment s | |||||
| 187 | ||||||
| 188 | ||||||
| 189 | Step 13 | |||||
| 190 | Execution Step | |||||
| 191 | ||||||
| 192 | Descriptio n* | |||||
| 193 | Click on C reate Prog ress Note on the req uest | |||||
| 194 | ||||||
| 195 | Expected R esults | |||||
| 196 | A new tab is opended to enter in progres s note Com ments | |||||
| 197 | Validates | |||||
| 198 | ||||||
| 199 | ||||||
| 200 | ||||||
| 201 | Attachment s | |||||
| 202 | ||||||
| 203 | ||||||
| 204 | Step 14 | |||||
| 205 | Execution Step | |||||
| 206 | ||||||
| 207 | Descriptio n* | |||||
| 208 | Select OK on the not e pop-up t o create a n encounte r note | |||||
| 209 | ||||||
| 210 | Expected R esults | |||||
| 211 | A new enco unter note is create d. In the note text, the callb ack phone number is populated Comments | |||||
| 212 | Validates | |||||
| 213 | ||||||
| 214 | Attachment s | |||||
| 215 | ||||||
| 216 | ||||||
| 217 | Step 15 | |||||
| 218 | Execution Step | |||||
| 219 | ||||||
| 220 | Descriptio n* | |||||
| 221 | On the enc ounter not e, validat e the foll owing: Wor kload Enco unter Form s: | |||||
| 222 | -Place the notes gri d, Refresh Notes Gri d Button a nd the App ly Selecte d Notes bu tton under the Note Detail* fi eld | |||||
| 223 | -Users wil l be prese nted with the Genera l and Work load Encou nter secti ons for co mpletion E xpected Re sults | |||||
| 224 | The user i s able to validate t he encount er note fo rm Comment s | |||||
| 225 | Validates | |||||
| 226 | ||||||
| 227 | Attachment s | |||||
| 228 | ||||||
| 229 | ||||||
| 230 | Step 16 | |||||
| 231 | Execution Step | |||||
| 232 | ||||||
| 233 | Descriptio n* | |||||
| 234 | Provide th e followin g test val ues: | |||||
| 235 | ||||||
| 236 | Location | |||||
| 237 | ||||||
| 238 | Note Title | |||||
| 239 | ||||||
| 240 | Primary Di agnosis Co de | |||||
| 241 | CPT Code E xpected Re sults | |||||
| 242 | The user i s able to provide te st values Comments | |||||
| 243 | Validates | |||||
| 244 | ||||||
| 245 | ||||||
| 246 | ||||||
| 247 | Attachment s | |||||
| 248 | ||||||
| 249 | ||||||
| 250 | Step 17 | |||||
| 251 | Execution Step | |||||
| 252 | ||||||
| 253 | Descriptio n* Click o n Save | |||||
| 254 | note: 'Sav e to Vista /CPRS will have to b e tested i n R1.4 Int egration t est case f or the ind ividual us er logged in with VI STA access ' Expected Results | |||||
| 255 | The progre ss note in fo is save d in CRM C omments | |||||
| 256 | Validates | |||||
| 257 | ||||||
| 258 | Attachment s | |||||
| 259 | ||||||
| 260 | ||||||
| 261 | Step 18 | |||||
| 262 | Execution Step | |||||
| 263 | ||||||
| 264 | Descriptio n* | |||||
| 265 | Close out the progre ss note | |||||
| 266 | ||||||
| 267 | Expected R esults | |||||
| 268 | The progre ss note is closed Co mments | |||||
| 269 | Validates | |||||
| 270 | ||||||
| 271 | Attachment s | |||||
| 272 | ||||||
| 273 | ||||||
| 274 | Step 19 | |||||
| 275 | Execution Step | |||||
| 276 | ||||||
| 277 | Descriptio n* | |||||
| 278 | Open the c all script prompt (c hevron on the left o f the scre en) and cl ick on 'Cr eate Actio n Taken' | |||||
| 279 | ||||||
| 280 | Expected R esults | |||||
| 281 | The user i s prompted to enter actions ta ken on a n ew tab Com ments | |||||
| 282 | Validates | |||||
| 283 | ||||||
| 284 | Attachment s | |||||
| 285 | ||||||
| 286 | ||||||
| 287 | Step 20 | |||||
| 288 | Execution Step | |||||
| 289 | ||||||
| 290 | Descriptio n* | |||||
| 291 | On the new tab, prov ide an act ion (notes field) an d a descri pation and click on save. Clos e out the tab | |||||
| 292 | ||||||
| 293 | ||||||
| 294 | ||||||
| 295 | Expected R esults | |||||
| 296 | The user i s able to provide an action ta ken Commen ts | |||||
| 297 | Validates | |||||
| 298 | ||||||
| 299 | Attachment s | |||||
| 300 | ||||||
| 301 | ||||||
| 302 | Step 21 | |||||
| 303 | Execution Step | |||||
| 304 | ||||||
| 305 | Descriptio n* | |||||
| 306 | On the req uest form, refresh t he form an d validate that the action and descripti on are now present i n the 'Act ion Taken' tab | |||||
| 307 | ||||||
| 308 | Expected R esults | |||||
| 309 | The action and descr iptions ar e now pres ent Commen ts | |||||
| 310 | Validates | |||||
| 311 | ||||||
| 312 | Attachment s | |||||
| 313 | ||||||
| 314 | ||||||
| 315 | Step 22 | |||||
| 316 | Execution Step | |||||
| 317 | ||||||
| 318 | Descriptio n* | |||||
| 319 | For the st eps below - click on each butt on listed in the act ion step a nd validat e that dat a is being displayed from ESR and any ad ditional e xpected de tails (not e: may nee d differen t Veteran records fo r differen t ESR pull s, as need ed) | |||||
| 320 | ||||||
| 321 | Expected R esults | |||||
| 322 | The user i s able to validate e ach of the medical c hart tab C omments | |||||
| 323 | Validates | |||||
| 324 | ||||||
| 325 | Attachment s | |||||
| 326 | ||||||
| 327 | ||||||
| 328 | Step 23 | |||||
| 329 | Execution Step | |||||
| 330 | ||||||
| 331 | Descriptio n* SC Disa bilities | |||||
| 332 | Expected R esults | |||||
| 333 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 334 | Validates | |||||
| 335 | ||||||
| 336 | Attachment s | |||||
| 337 | ||||||
| 338 | ||||||
| 339 | Step 24 | |||||
| 340 | ||||||
| 341 | ||||||
| 342 | ||||||
| 343 | Execution Step | |||||
| 344 | ||||||
| 345 | Descriptio n* Problem s | |||||
| 346 | Expected R esults | |||||
| 347 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 348 | Validates | |||||
| 349 | ||||||
| 350 | Attachment s | |||||
| 351 | ||||||
| 352 | ||||||
| 353 | Step 25 | |||||
| 354 | Execution Step | |||||
| 355 | ||||||
| 356 | Descriptio n* Notes | |||||
| 357 | Expected R esults | |||||
| 358 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 359 | Validates | |||||
| 360 | ||||||
| 361 | Attachment s | |||||
| 362 | ||||||
| 363 | ||||||
| 364 | Step 26 | |||||
| 365 | Execution Step | |||||
| 366 | ||||||
| 367 | Descriptio n* Orders | |||||
| 368 | Expected R esults | |||||
| 369 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 370 | Validates | |||||
| 371 | ||||||
| 372 | Attachment s | |||||
| 373 | ||||||
| 374 | ||||||
| 375 | Step 27 | |||||
| 376 | Execution Step | |||||
| 377 | ||||||
| 378 | Descriptio n* Appoint ments | |||||
| 379 | Expected R esults | |||||
| 380 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 381 | Validates | |||||
| 382 | ||||||
| 383 | ||||||
| 384 | ||||||
| 385 | Attachment s | |||||
| 386 | ||||||
| 387 | ||||||
| 388 | Step 28 | |||||
| 389 | Execution Step | |||||
| 390 | ||||||
| 391 | Descriptio n* Medicat ions | |||||
| 392 | Expected R esults | |||||
| 393 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 394 | Validates | |||||
| 395 | ||||||
| 396 | Attachment s | |||||
| 397 | ||||||
| 398 | ||||||
| 399 | Step 29 | |||||
| 400 | Execution Step | |||||
| 401 | ||||||
| 402 | Descriptio n* Posting s | |||||
| 403 | Expected R esults | |||||
| 404 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 405 | Validates | |||||
| 406 | ||||||
| 407 | Attachment s | |||||
| 408 | ||||||
| 409 | ||||||
| 410 | Step 30 | |||||
| 411 | Execution Step | |||||
| 412 | ||||||
| 413 | Descriptio n* Allergi es | |||||
| 414 | Expected R esults | |||||
| 415 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 416 | Validates | |||||
| 417 | ||||||
| 418 | Attachment s | |||||
| 419 | ||||||
| 420 | ||||||
| 421 | Step 31 | |||||
| 422 | Execution Step | |||||
| 423 | ||||||
| 424 | Descriptio n* Labs | |||||
| 425 | Expected R esults | |||||
| 426 | If availab le for the test user , data is populated in the tab . | |||||
| 427 | ||||||
| 428 | ||||||
| 429 | ||||||
| 430 | Comments | |||||
| 431 | Validates Attachment s | |||||
| 432 | ||||||
| 433 | ||||||
| 434 | Step 32 | |||||
| 435 | Execution Step | |||||
| 436 | ||||||
| 437 | Descriptio n* Consult s | |||||
| 438 | Expected R esults | |||||
| 439 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 440 | Validates | |||||
| 441 | ||||||
| 442 | Attachment s | |||||
| 443 | ||||||
| 444 | ||||||
| 445 | Step 33 | |||||
| 446 | Execution Step | |||||
| 447 | ||||||
| 448 | Descriptio n* Non-VA Meds | |||||
| 449 | Expected R esults | |||||
| 450 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 451 | Validates | |||||
| 452 | ||||||
| 453 | Attachment s | |||||
| 454 | ||||||
| 455 | ||||||
| 456 | Step 34 | |||||
| 457 | Execution Step | |||||
| 458 | ||||||
| 459 | Descriptio n* Vitals | |||||
| 460 | Expected R esults | |||||
| 461 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 462 | Validates | |||||
| 463 | ||||||
| 464 | Attachment s | |||||
| 465 | ||||||
| 466 | ||||||
| 467 | Step 35 | |||||
| 468 | Execution Step | |||||
| 469 | ||||||
| 470 | Descriptio n* | |||||
| 471 | Imaging (p reviously named Radi ology) | |||||
| 472 | ||||||
| 473 | ||||||
| 474 | ||||||
| 475 | Expected R esults | |||||
| 476 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 477 | Validates | |||||
| 478 | ||||||
| 479 | Attachment s | |||||
| 480 | ||||||
| 481 | ||||||
| 482 | Step 36 | |||||
| 483 | Execution Step | |||||
| 484 | ||||||
| 485 | Descriptio n* Dischar ges | |||||
| 486 | Expected R esults | |||||
| 487 | If availab le for the test user , data is populated in the tab . Comments | |||||
| 488 | Validates | |||||
| 489 | ||||||
| 490 | Attachment s | |||||
| 491 | ||||||
| 492 | ||||||
| 493 | Step 37 | |||||
| 494 | Execution Step | |||||
| 495 | ||||||
| 496 | Descriptio n* | |||||
| 497 | Navigate b ack to the request t ab | |||||
| 498 | ||||||
| 499 | Expected R esults | |||||
| 500 | The user i s directed to the re quest tab Comments | |||||
| 501 | Validates | |||||
| 502 | ||||||
| 503 | Attachment s | |||||
| 504 | ||||||
| 505 | ||||||
| 506 | Step 38 | |||||
| 507 | Execution Step | |||||
| 508 | ||||||
| 509 | Descriptio n* | |||||
| 510 | Click on ' Resolve Re quest' and 'Ok' on t he prompt | |||||
| 511 | ||||||
| 512 | Expected R esults | |||||
| 513 | The user i s able to select the resolve r equest Com ments | |||||
| 514 | Validates | |||||
| 515 | ||||||
| 516 | Attachment s | |||||
| 517 | ||||||
| 518 | ||||||
| 519 | Step 39 | |||||
| 520 | Execution Step | |||||
| 521 | ||||||
| 522 | ||||||
| 523 | ||||||
| 524 | Descriptio n* | |||||
| 525 | Click on S ave to clo se out the request | |||||
| 526 | ||||||
| 527 | Expected R esults | |||||
| 528 | The reques t is now c losed and resolved a nd unedita ble Commen ts | |||||
| 529 | Validates | |||||
| 530 | ||||||
| 531 | Attachment s | |||||
| 532 | ||||||
| 533 | Associated E-Signatu res | |||||
| 534 | ||||||
| 535 | ||||||
| 536 | SignedActi onSignerCo mmentAddit ional Info rmation |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.