Produced by Araxis Merge on 2/5/2019 9:43:57 AM Central Standard 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 | EPIP_MC_GMTS_IP25_TV3.zip\EPIP_MC_GMTS_IP25_TV3 | EPIP_Test_Evaluation_(MC_2.3_48_GMTS_2.7_123).doc | Mon Feb 4 12:44:12 2019 UTC |
| 2 | EPIP_MC_GMTS_IP25_TV3.zip\EPIP_MC_GMTS_IP25_TV3 | EPIP_Test_Evaluation_(MC_2.3_48_GMTS_2.7_123).doc | Tue Feb 5 13:15:22 2019 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 8 | 550 |
| Changed | 6 | 12 |
| Inserted | 0 | 0 |
| Removed | 2 | 2 |
| 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 | Test Evalu ationExist ing Produc t Intake P rogram (EP IP) | ||
| 2 | MC*2.3*48 and GMTS*2 .7*123 | ||
| 3 | Test Evalu ation | ||
| 4 | |||
| 5 | Department of Vetera ns Affairs | ||
| 6 | January 20 19 | ||
| 7 | Version 1. 0 | ||
| 8 | Revision H istory | ||
| 9 | Note: The revision h istory cyc le begins once chang es or enha ncements a re request ed after t he Communi cations Pl an has bee n baseline d. | ||
| 10 | DateVersio nDescripti onAuthor01 /22/20191. 0Initial d ocumentEPI P Project TeamArtifa ct Rationa le | ||
| 11 | The test e valuation document i s the prim ary output of the te st and eva luation pr ocess, an integral p art of the systems e ngineering process, which iden tifies lev els of per formance a nd assists the devel oper in co rrecting d eficiencie s. | ||
| 12 | Table of C ontents | ||
| 13 | 11. | ||
| 14 | Test Evalu ation Intr oduction | ||
| 15 | |||
| 16 | |||
| 17 | 11.1. | ||
| 18 | Test Evalu ation Scop e | ||
| 19 | |||
| 20 | |||
| 21 | 11.2. | ||
| 22 | Test Archi tecture | ||
| 23 | |||
| 24 | |||
| 25 | 11.3. | ||
| 26 | Test Envir onment/Con figuration | ||
| 27 | |||
| 28 | |||
| 29 | 21.4. | ||
| 30 | Installati on Process | ||
| 31 | |||
| 32 | |||
| 33 | 22. | ||
| 34 | Test Data | ||
| 35 | |||
| 36 | |||
| 37 | 23. | ||
| 38 | Issues | ||
| 39 | |||
| 40 | |||
| 41 | 24. | ||
| 42 | Test Execu tion Log | ||
| 43 | |||
| 44 | |||
| 45 | 35. | ||
| 46 | Test Defec t Log | ||
| 47 | |||
| 48 | |||
| 49 | 36. | ||
| 50 | Test Resul ts Summary | ||
| 51 | |||
| 52 | |||
| 53 | 36.1. | ||
| 54 | Defect Sev erity and Priority L evels | ||
| 55 | |||
| 56 | |||
| 57 | 46.2. | ||
| 58 | Total Defe cts by Sev erity Leve l | ||
| 59 | |||
| 60 | |||
| 61 | 46.3. | ||
| 62 | Breakdown of Test Re sults | ||
| 63 | |||
| 64 | |||
| 65 | 46.4. | ||
| 66 | Performanc e Testing | ||
| 67 | |||
| 68 | |||
| 69 | 47. | ||
| 70 | Test Cover age | ||
| 71 | |||
| 72 | |||
| 73 | 47.1. | ||
| 74 | Requiremen ts Covered | ||
| 75 | |||
| 76 | |||
| 77 | 57.2. | ||
| 78 | Section 50 8 Complian ce Coverag e | ||
| 79 | |||
| 80 | |||
| 81 | 58. | ||
| 82 | Suggested Actions | ||
| 83 | |||
| 84 | |||
| 85 | 59. | ||
| 86 | Defect Sev erity and Priority D efinitions | ||
| 87 | |||
| 88 | |||
| 89 | 69.1. | ||
| 90 | Defect Sev erity Leve l | ||
| 91 | |||
| 92 | |||
| 93 | 69.1.1. | ||
| 94 | Severity L evel 1 – C ritical | ||
| 95 | |||
| 96 | |||
| 97 | 69.1.2. | ||
| 98 | Severity L evel 2 - H igh | ||
| 99 | |||
| 100 | |||
| 101 | 69.1.3. | ||
| 102 | Severity L evel 3 - M edium | ||
| 103 | |||
| 104 | |||
| 105 | 79.1.4. | ||
| 106 | Severity L evel 4 - L ow | ||
| 107 | |||
| 108 | |||
| 109 | 79.2. | ||
| 110 | Priority C lassificat ions | ||
| 111 | |||
| 112 | |||
| 113 | 79.2.1. | ||
| 114 | Priority 1 - Resolve Immediate ly | ||
| 115 | |||
| 116 | |||
| 117 | 79.2.2. | ||
| 118 | Priority 2 - Give Hi gh Attenti on | ||
| 119 | |||
| 120 | |||
| 121 | 79.2.3. | ||
| 122 | Priority 3 - Normal Queue | ||
| 123 | |||
| 124 | |||
| 125 | 79.2.4. | ||
| 126 | Priority 4 - Low Pri ority | ||
| 127 | |||
| 128 | |||
| 129 | 710. | ||
| 130 | Optional T ables, Cha rts, and G raphs | ||
| 131 | |||
| 132 | |||
| 133 | 811. | ||
| 134 | Document A pproval Si gnatures | ||
| 135 | |||
| 136 | |||
| 137 | 9Appendix A - Test E xecution L og | ||
| 138 | |||
| 139 | |||
| 140 | 10Appendix B – Defec t Log | ||
| 141 | |||
| 142 | |||
| 143 | |||
| 144 | |||
| 145 | Test Evalu ation Intr oduction | ||
| 146 | The purpos e of this Test Evalu ation is t o: | ||
| 147 | Identify t he testing approach used. | ||
| 148 | Present a summary an alysis of the key te st results from the remediatio n of this intake for review an d assessme nt by desi gnated sta keholders. | ||
| 149 | Provide a general st atement of the quali ty of the system und er test. | ||
| 150 | Make recom mendations for futur e testing efforts. | ||
| 151 | Test Evalu ation Scop e | ||
| 152 | The scope of this Te st Evaluat ion is to verify the functiona lity of th e code mod ification for patche s MC*2.3*4 8 and GMTS *2.7*123, as determi ned by Fun ctional, C omponent I ntegration /System, a nd Regress ion testin g. Testing activitie s followed the speci fications outlined i n the foll owing Mast er Test Pl an: MC*2.3 *48 and GM TS*2.7*123 Master Te st Plan (i ncluded in Appendix A). | ||
| 153 | Test Archi tecture | ||
| 154 | Following are the EP IP test ac counts use d by the L eidos Deve lopment an d SQA Test ing teams to test MC *2.3*48 an d GMTS*2.7 *123. | ||
| 155 | Developmen t Test Acc ounts | ||
| 156 | (For Unit Testing)SQ A Test Acc ounts | ||
| 157 | (For Funct ional, Reg ression, a nd Compone nt Integra tion and S ystem Test ing)VistAS 1 (alterna te name: D 1S1)VistAG 1 (alterna te name: D 1G1) VistA S2 (altern ate name: D1S2) – | ||
| 158 | for CPRS G UI testing onlyVistA G2 (altern ate name: D1G2) – | ||
| 159 | for CPRS G UI testing onlyTest Environmen t/Configur ation | ||
| 160 | The EPIP t est accoun ts are mai ntained by the EPIP System Adm inistrator , who inst alls all V A-released patches a s soon as they are n ationally released. All EPIP t est accoun ts are clo ned from e xisting VA Enterpris e Testing Services ( ETS) test accounts. The Comput erized Pat ient Recor d System ( CPRS) Grap hical User Interface (GUI) exe cutable is configure d for each VistA ins tance util izing a un ique Inter net Protoc ol (IP) ad dress to c onnect to the VistA applicatio ns. Any up dates to t he CPRS GU I executab le are han dled by th e EPIP Sys tem Admini strator. | ||
| 161 | All EPIP T est Engine ers and De velopers w ho have th e proper c redentials can acces s the test accounts. The VA Au stin Infor mation Tec hnology Ce nter (AITC ) support team reset s password s and sets up new ac cess crede ntials on an as-need ed basis. | ||
| 162 | Installati on Process | ||
| 163 | As soon as the remed iation pro cess is co mplete and the patch is availa ble for te sting, a K IDS build is created in the De velopment account an d then sen t to FORUM for final packaging . The patc h is then submitted to the VA SQA Lead’s Mailman a ccount for installat ion. | ||
| 164 | An EPIP De veloper or Test Engi neer utili zes the KI DS Install ation proc ess to ext ract the b uild from the patch and instal l the buil d into a t est accoun t. The ind ividual wh o installs the patch verifies the routin e checksum s and also checks fo r errors d uring the installati on process . If the p atch is su ccessfully installed without a ny errors, then the EPIP Test team proce eds with F unctional, Regressio n, and Com ponent Int egration a nd System testing. I f defects are found, then the Developmen t team wor ks to find a resolut ion and cr eates new versions o f the patc h until al l defects are resolv ed. | ||
| 165 | Test Data | ||
| 166 | The SQA Te sting team utilizes the test d ata in the designate d test acc ounts (D1G 1, D1G2). | ||
| 167 | The test d ata is enc rypted fol lowing the standards set forth by the VA Office of Informati on & Techn ology (OIT ). All Per sonally Id entifiable Informati on (PII) a nd Protect ed Health Informatio n (PHI) is scrubbed and is not available to the Te st Enginee rs. | ||
| 168 | All testin g is execu ted using encrypted test patie nts availa ble from a ny of the EPIP test accounts. Examples o f encrypte d test pat ients: | ||
| 169 | AAAHURMMX, XPHY | ||
| 170 | BADHB, HAA DXS | ||
| 171 | FDHUX, YHI J | ||
| 172 | All tests were execu ted manual ly by EPIP Test Engi neers. | ||
| 173 | Issues | ||
| 174 | No issues were encou ntered dur ing the te sting MC*2 .3*48 and GMTS*2.712 3. | ||
| 175 | TitleIssue Descripti onTypeSeve rityN/AN/A N/AN/ATest Execution Log | ||
| 176 | The Test E xecution L og records the execu tion of te st scripts and docum ents the t est result s for each test scri pt. | ||
| 177 | The SQA Te sting team utilizes the Ration al Quality Managemen t (QM) too l for all testing ac tivities. All test d ocuments a re stored in the EPI P reposito ry, includ ing the Ma ster Test Plan, Test Suites, T est Cases, and Test Scripts. T est execut ion is per formed, an d test res ults recor ded, in Ra tional QM. The Test Engineer a dds the te st results to the Te st Executi on records to indica te whether testing a chieved Pa ss or Fail status. | ||
| 178 | The Test E xecution r ecords for MC*2.3*48 and GMTS* 2.7*123 ar e included in the EP IP MC*2.3* 48 and GMT S*2.7*123 Master Tes t Plan. Th e Master T est Plan i s availabl e in Appen dix A. | ||
| 179 | Test Defec t Log | ||
| 180 | The Test D efect Log is a tool for record ing, analy zing, trac king, and documentin g the clos ure of def ects. It s pecifies t he screen, field, be havior or result tha t occurred , and the IEEE-defin ed Severit y Level. I t includes enough in formation for the de veloper to find and re-create the defect . The Defe ct Log is available in Appendi x B. | ||
| 181 | Test Resul ts Summary | ||
| 182 | SQA testin g for this intake st arted in t he Dev1 Go ld1 test e nvironment on Octobe r 31, 2018 and ended on Januar y 22, 2019 . | ||
| 183 | Test versi on 1 of pa tches MC*2 .3*48 and GMTS*2.7*1 23 were in stalled in the test environmen t after Un it testing in Dev1 S ilver1 was completed . Upon com pletion of Integrati on testing (Componen t Integrat ion and Sy stem Testi ng, Functi onal Testi ng, and Re gression T esting), o ne (1) def ect was fo und and re ported. | ||
| 184 | Test versi on 2 of pa tches MC*2 .3*48 and GMTS*2.7*1 23 were in stalled in the test environmen t on Decem ber 5, 201 8 after Un it testing in Dev1 S ilver1 was completed . This ver sion resol ved SQA De fect 87291 2 to remov e the seco ndary menu options u sed for te sting when the patch es are ins talled in a Producti on environ ment. Upon completio n of Integ ration tes ting (Comp onent Inte gration an d System T esting, Fu nctional T esting, an d Regressi on Testing ), one (1) defect wa s found an d reported . | ||
| 185 | Test versi on 3 of pa tches MC*2 .3*48 and GMTS*2.7*1 23 were in stalled in the test environmen t on Janua ry 14, 201 9 after Un it testing in Dev1 S ilver1 was completed . In test version 2, selecting a patient from the list durin g the crea tion of a Patient Ca re Encount er (PCE) v isit resul ted in an "Invalid c hoice" err or message displayin g. This ve rsion corr ected the issue. Aft er a produ ct demonst ration to VA stakeho lders, two additiona l items we re changed based on feedback. Code was c hanged to correctly display th e Narrativ e text fro m the PCE data trans fer and tw o option n ames were changed to remove "M CM4" from the screen display n ames. Upon completio n of Funct ional Test ing and Re gression T esting, ze ro (0) def ects were found and reported. | ||
| 186 | Defect Sev erity and Priority L evels | ||
| 187 | A defect i s defined as a flaw in a compo nent or sy stem that can cause the compon ent or sys tem to fai l to perfo rm its req uired func tion, e.g. , an incor rect state ment or da ta definit ion. A def ect, if en countered during exe cution, ma y cause a failure of the compo nent or sy stem. | ||
| 188 | Defects ar e categori zed accord ing to sev erity and priority l evels. The test anal yst assign s the seve rity, whil e the deve lopment ma nager assi gns the pr iority for repair. F or more in formation, see Defec t Severity and Prior ity Defini tion in th is Test Ev aluation. | ||
| 189 | Total Defe cts by Sev erity Leve l | ||
| 190 | The Defect Log in Ap pendix B d isplays th e defects encountere d while te sting this patch, an d the seve rity level of each. | ||
| 191 | Breakdown of Test Re sults | ||
| 192 | Testing wa s complete d on Janua ry 22, 201 9. All tes t results were recor ded in Rat ional QM. Detailed r esults are available in the EP IP MC*2.3* 48 and GMT S*2.7*123 Master Tes t Plan (se e Appendix A). | ||
| 193 | Performanc e Testing | ||
| 194 | Performanc e testing was not co nducted. | ||
| 195 | Test Cover age | ||
| 196 | The EPIP M C*2.3*48 a nd GMTS*2. 7*123 Mast er Test Pl an contain s details on test co verage (se e Appendix A). | ||
| 197 | Requiremen ts Covered | ||
| 198 | The requir ements for MC*2.3*48 and GMTS* 2.7*123 ar e stored i n the Rati onal Requi rements Ma nagement ( RM) applic ation. The test case s stored i n Rational Quality M anagement (QM) are u sed to val idate that the requi rements ha ve been ad dressed, p roviding f ull tracea bility. Th e user sto ries store d in Ratio nal Config uration Ma nagement ( CM) are li nked to th e requirem ents in RM and test cases in Q M. | ||
| 199 | The follow ing links provide ac cess to th e various Medicine r epositorie s related to the MC* 2.3*48 pat ch in the Rational t oolkit. If link tran slation is sues preve nt direct access, co py and pas te the URL s into you r browser. | ||
| 200 | Medicine ( RM) – Go t o Artifact s, then Br owse Artif acts. Loca te the EPI P folder o n the left side of t he page an d expand i t to displ ay patch f olders. Ea ch patch f older cont ains the r equirement s for the patch numb er shown i n the fold er name. | ||
| 201 | https://cl m.rational .oit. DNS /rm/web#ac tion=com.i bm.rdm.web .pages.sho wFoundatio nProjectDa shboard&co mponentURI =https://c lm.rationa l.oit. DNS /rm/rm-pro jects/_Ikf kEQXREeezM -6puAtpuw/ components /_JGUewAXR EeezM-6puA tpuw | ||
| 202 | Medicine ( QM) – Go t o Planning , then Bro wse Test P lans, and then searc h for the Master Tes t Plan you need. The Master Te st Plan an d test cas es are lin ked to req uirements. | ||
| 203 | https://cl m.rational .oit. DNS /qm/web/co nsole/Medi cine%20(QM )#action=c om.ibm.rqm .planning. home.actio nDispatche r&subActio n=viewUser Home | ||
| 204 | Medicine ( CM) – Go t o Plans, t hen All Pl ans, and t hen search for the S print Plan you need. The user stories in each Plan are linke d to requi rements an d test cas es. | ||
| 205 | https://cl m.rational .oit. DNS /ccm/web/p rojects/Me dicine%20( CM)#action =com.ibm.t eam.dashbo ard.viewDa shboard | ||
| 206 | The follow ing links provide ac cess to th e various Health Sum mary (HS) repositori es related to the GM TS*2.7*123 patch in the Ration al toolkit . If link translatio n issues p revent dir ect access , copy and paste the URLs into your brow ser. | ||
| 207 | HS (RM) – Go to Arti facts, the n Browse A rtifacts. Locate the EPIP fold er on the left side of the pag e and expa nd it to d isplay pat ch folders . Each pat ch folder contains t he require ments for the patch number sho wn in the folder nam e. | ||
| 208 | https://cl m.rational .oit. DNS /rm/web#ac tion=com.i bm.rdm.web .pages.sho wFoundatio nProjectDa shboard&co mponentURI =https://c lm.rationa l.oit. DNS /rm/rm-pro jects/_PB7 A0B6uEeafn 8RFT4tzpQ/ components /_PWMAoB6u Eeafn8RFT4 tzpQ | ||
| 209 | HS (QM) – Go to Plan ning, then Browse Te st Plans, and then s earch for the Master Test Plan you need. The Maste r Test Pla n and test cases are linked to requireme nts. | ||
| 210 | https://cl m.rational .oit. DNS /qm/web/co nsole/HS%2 0(QM)#acti on=com.ibm .rqm.plann ing.home.a ctionDispa tcher&subA ction=view UserHome | ||
| 211 | HS (CM) – Go to Plan s, then Al l Plans, a nd then se arch for t he Sprint Plan you n eed. The u ser storie s in each Plan are l inked to r equirement s and test cases. | ||
| 212 | https://cl m.rational .oit. DNS /ccm/web/p rojects/HS %20(CM)#ac tion=com.i bm.team.da shboard.vi ewDashboar d | ||
| 213 | Section 50 8 Complian ce Coverag e | ||
| 214 | Section 50 8 test res ults will be reporte d to VA in the follo wing docum ents: | ||
| 215 | EPIP_VASec tion508_Co mpliance_T est_Result s_(MC_2.3_ 48,_GMTS_2 .7_123) | ||
| 216 | EPIP_VASec tion508_In take_Docum ent_(MC_2. 3_48,_GMTS _2.7_123) | ||
| 217 | EPIP_VASec tion508_Ve rifiable_O bjective_E vidence_(M C_2.3_48,_ GMTS_2.7_1 23) | ||
| 218 | Suggested Actions | ||
| 219 | Leidos rec ommends mo ving this patch to I OC testing . | ||
| 220 | Defect Sev erity and Priority D efinitions | ||
| 221 | The classi fication o f defects within a s ystem exam ines both the severi ty and pri ority of t he defect. | ||
| 222 | Severity i s a measur e of how g reat the i mpact is o n the user ’s ability to comple te the doc umented ac tions with in the sys tem. | ||
| 223 | Priority d etermines the speed with which a given d efect must be repair ed. | ||
| 224 | Defect cla ssificatio n may be d etermined either bec ause testi ng is dela yed by a f ailure in the system or becaus e a cumber some worka round prev ents a use r from com pleting th e assigned tasks. Bo th severit y and prio rity measu res must b e recorded when sche duling def ect resolu tion tasks . | ||
| 225 | Defect Sev erity Leve l | ||
| 226 | The follow ing subsec tions iden tify the d efect seve rity level s. | ||
| 227 | Severity L evel 1 – C ritical | ||
| 228 | Institute of Electri cal and El ectronics Engineers (IEEE) def inition: T he defect results in the failu re of the complete s oftware sy stem, of a subsystem , or of a software u nit (progr am or modu le) within the syste m. | ||
| 229 | Any defect that comp romises pa tient safe ty or syst em securit y. Example s of syste m security defects i nclude bre ach of con fidentiali ty require ments of t he Privacy Act, the Health Ins urance Por tability a nd Account ability Ac t (HIPAA), or Federa l Tax Info rmation gu idelines. | ||
| 230 | Loss of sy stem funct ionality c ritical to user oper ations wit h no suita ble workar ound, i.e. , there is no way to achieve t he expecte d results using the applicatio n. | ||
| 231 | System cra sh or hang that prev ents furth er testing or operat ion of the complete applicatio n or a sec tion of th e applicat ion. | ||
| 232 | Any defect that caus es corrupt ion of dat a from a r esult of t he system (as oppose d to user error). | ||
| 233 | Any defect in which inappropri ate transm issions ar e consiste ntly gener ated or ap propriate transmissi ons of HL7 messages fail to be generated . | ||
| 234 | Loss of fu nctionalit y resultin g in erron eous eligi bility/enr ollment de terminatio ns or comm unications not being sent. | ||
| 235 | Severity L evel 2 - H igh | ||
| 236 | IEEE defin ition: The defect re sults in t he failure of the co mplete sof tware syst em, of a s ubsystem, or of a so ftware uni t (program or module ) within t he system. There is no way to make the f ailed comp onent(s) f unction. H owever, th ere are ac ceptable p rocessing alternativ es which w ill yield the desire d result. | ||
| 237 | A major de fect in th e function ality that does not result in corruption of data. | ||
| 238 | A major de fect in th e function ality resu lting in a failure o f all or p art of the applicati on, where: | ||
| 239 | The expect ed results can tempo rarily be achieved b y alternat e means. T he custome r indicate s the work around is acceptabl e for the short term . | ||
| 240 | Any defect that does not confo rm to Sect ion 508 st andards. | ||
| 241 | Any defect that resu lts in ina ccurate or missing r equirement s. | ||
| 242 | Any defect that resu lts in inv alid authe ntication or authent ication of an invali d end user . | ||
| 243 | Severity L evel 3 - M edium | ||
| 244 | IEEE defin ition: The defect do es not res ult in a f ailure, bu t causes t he system to produce incorrect , incomple te, or inc onsistent results, o r the defe ct impairs the syste ms usabili ty. | ||
| 245 | Minor func tionality is not wor king as in tended and a workaro und exists but is no t suitable for long term use | ||
| 246 | The inabil ity of a v alid user to access the system consisten t with gra nted privi leges | ||
| 247 | Typographi cal or gra mmatical e rrors in t he applica tion, incl uding inst allation g uides, use r guides, training m anuals, an d design d ocuments | ||
| 248 | Any defect producing cryptic, incorrect, or inappr opriate er ror messag es | ||
| 249 | Any defect that resu lts from t he use of non-standa rd data te rminology in the app lication o r document ation, as defined by the Depar tment of V eterans Af fairs | ||
| 250 | Cosmetic i ssues that are impor tant to th e integrit y of the p roduct, bu t do not r esult in d ata entry and or dat a quality problems. | ||
| 251 | Severity L evel 4 - L ow | ||
| 252 | IEEE defin ition: The defect do es not cau se a failu re, does n ot impair usability, and the d esired pro cessing re sults are easily obt ained by w orking aro und the de fect. | ||
| 253 | Minor loss of, or de fect in th e function ality wher e a long t erm use ex ists | ||
| 254 | Low-level cosmetic i ssues. | ||
| 255 | Priority C lassificat ions | ||
| 256 | The follow ing subsec tions iden tify the a ppropriate actions f or defects at each p riority le vel, per d efinitions of IEEE. | ||
| 257 | Priority 1 - Resolve Immediate ly | ||
| 258 | Further de velopment and/or tes ting canno t occur un til the de fect has b een repair ed. The sy stem canno t be used until the repair has been affe cted. | ||
| 259 | Priority 2 - Give Hi gh Attenti on | ||
| 260 | The defect must be r esolved as soon as p ossible be cause it i s impairin g developm ent and/or testing a ctivities. System us e will be severely a ffected un til the de fect is fi xed. | ||
| 261 | Priority 3 - Normal Queue | ||
| 262 | The defect should be resolved in the nor mal course of develo pment acti vities. It can wait until a ne w build or version i s created. | ||
| 263 | Priority 4 - Low Pri ority | ||
| 264 | The defect is an irr itant that should be repaired, but can b e repaired after mor e serious defects ha ve been fi xed. | ||
| 265 | Optional T ables, Cha rts, and G raphs | ||
| 266 | None. | ||
| 267 | Document A pproval Si gnatures | ||
| 268 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | ||
| 269 | Program/Pr oject Mana ger | ||
| 270 | Date | ||
| 271 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | ||
| 272 | Business S ponsor Rep resentativ e | ||
| 273 | Date | ||
| 274 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | ||
| 275 | Test Lead | ||
| 276 | Date | ||
| 277 | Appendix A - Test Ex ecution Lo g | ||
| 278 | The Test E xecution R ecords for MC*2.3*48 and GMTS* 2.7*123 ar e included in the EP IP MC*2.3* 48 and GMT S*2.7*123 Master Tes t Plan. | ||
| 279 | Appendix B – Defect Log | ||
| 280 | Two (2) de fects were found dur ing testin g of MC*2. 3*48 and G MTS*2.7*12 3. The def ect has be en resolve d. | ||
| 281 | Defect IDA ffected Sc reenAffect ed FieldOb served Beh aviorSever ityDescrip tionN/AN/A N/AN/AN/AN o defects were found during Un it Testing of versio n 1.0N/AN/ AN/AN/AN/A No defects were foun d during C omponent I ntegration /Systems T esting of version 1. 0N/AN/AN/A N/AN/ANo d efects wer e found du ring Regre ssion test ing of ver sion 1.0.8 72912Remov al of HL7 Transmissi on Menu in Productio n accountN /AN/AHighO ne (1) def ect was fo und during Functiona l Testing of version 1.0N/AN/A N/AN/AN/AN o defects were found during Un it Testing of versio n 2.0.N/AN /AN/AN/AN/ ANo defect s were fou nd during Component Integratio n/Systems Testing of version 2 .0.N/AN/AN /AN/AN/ANo defects w ere found during Reg ression te sting of v ersion 2.0 .904431Hea lth Summar y Visit Cr eationN/AN /AHighOne (1) defect was found during Fu nctional T esting of version 2. 0. N/AN/AN /AN/AN/ANo defects w ere found during Uni t Testing of version 3.0.N/AN/ AN/AN/AN/A No defects were foun d during R egression testing of version 3 .0.N/AN/AN /AN/AN/ANo defects w ere found during Fun ctional Te sting of v ersion 3.0 . | ||
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.