Produced by Araxis Merge on 6/26/2018 2:13:24 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 | 435_cif.zip | EPIP_Test_Evaluation_(OR_3.0_435).doc | Tue Jun 26 18:23:32 2018 UTC |
2 | 435_cif.zip | EPIP_Test_Evaluation_(OR_3.0_435).doc | Tue Jun 26 18:26:32 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 5 | 588 |
Changed | 4 | 8 |
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 | Existing P roduct Int ake Progra m (EPIP) | |
2 | Patch OR*3 .0*435 | |
3 | Test Evalu ation | |
4 | ||
5 | Department of Vetera ns Affairs | |
6 | March 2018 | |
7 | Version 4. 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 onAuthor03 /15/20184. 0Updated T est Result s Summary and Append ix B Defec t Log with new test resultsEPI P Project Team02/09/ 20183.0Upd ated Test Results Su mmary and Appendix B Defect Lo g with new test resu ltsEPIP Pr oject Team 07/21/2017 2.0Updated entire do cument wit h new test informati on, defect s, and tes ting detai lsEPIP Pro ject Team1 1/04/2016 | |
11 | 1.0Initial documentE PIP Projec t TeamArti fact Ratio nale | |
12 | 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. | |
13 | Table of C ontents | |
14 | 11. | |
15 | Test Evalu ation Intr oduction | |
16 | ||
17 | ||
18 | 11.1. | |
19 | Test Evalu ation Scop e | |
20 | ||
21 | ||
22 | 11.2. | |
23 | Test Archi tecture | |
24 | ||
25 | ||
26 | 11.3. | |
27 | Test Envir onment/Con figuration | |
28 | ||
29 | ||
30 | 21.4. | |
31 | Installati on Process | |
32 | ||
33 | ||
34 | 22. | |
35 | Test Data | |
36 | ||
37 | ||
38 | 23. | |
39 | Issues | |
40 | ||
41 | ||
42 | 24. | |
43 | Test Execu tion Log | |
44 | ||
45 | ||
46 | 35. | |
47 | Test Defec t Log | |
48 | ||
49 | ||
50 | 36. | |
51 | Test Resul ts Summary | |
52 | ||
53 | ||
54 | 46.1. | |
55 | Defect Sev erity and Priority L evels | |
56 | ||
57 | ||
58 | 46.2. | |
59 | Total Defe cts by Sev erity Leve l | |
60 | ||
61 | ||
62 | 46.3. | |
63 | Breakdown of Test Re sults | |
64 | ||
65 | ||
66 | 46.4. | |
67 | Performanc e Testing | |
68 | ||
69 | ||
70 | 47. | |
71 | Test Cover age | |
72 | ||
73 | ||
74 | 47.1. | |
75 | Requiremen ts Covered | |
76 | ||
77 | ||
78 | 57.2. | |
79 | Section 50 8 Complian ce Coverag e | |
80 | ||
81 | ||
82 | 58. | |
83 | Suggested Actions | |
84 | ||
85 | ||
86 | 59. | |
87 | Defect Sev erity and Priority D efinitions | |
88 | ||
89 | ||
90 | 69.1. | |
91 | Defect Sev erity Leve l | |
92 | ||
93 | ||
94 | 69.1.1. | |
95 | Severity L evel 1 – C ritical | |
96 | ||
97 | ||
98 | 69.1.2. | |
99 | Severity L evel 2 - H igh | |
100 | ||
101 | ||
102 | 79.1.3. | |
103 | Severity L evel 3 - M edium | |
104 | ||
105 | ||
106 | 79.1.4. | |
107 | Severity L evel 4 - L ow | |
108 | ||
109 | ||
110 | 79.2. | |
111 | Priority C lassificat ions | |
112 | ||
113 | ||
114 | 79.2.1. | |
115 | Priority 1 - Resolve Immediate ly | |
116 | ||
117 | ||
118 | 79.2.2. | |
119 | Priority 2 - Give Hi gh Attenti on | |
120 | ||
121 | ||
122 | 79.2.3. | |
123 | Priority 3 - Normal Queue | |
124 | ||
125 | ||
126 | 79.2.4. | |
127 | Priority 4 - Low Pri ority | |
128 | ||
129 | ||
130 | 810. | |
131 | Optional T ables, Cha rts, and G raphs | |
132 | ||
133 | ||
134 | 911. | |
135 | Document A pproval Si gnatures | |
136 | ||
137 | ||
138 | 10Appendix A - Test Execution Log | |
139 | ||
140 | ||
141 | 11Appendix B – Defec t Log | |
142 | ||
143 | ||
144 | ||
145 | ||
146 | Test Evalu ation Intr oduction | |
147 | The purpos e of this Test Evalu ation is t o: | |
148 | Identify t he testing approach used. | |
149 | 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. | |
150 | Provide a general st atement of the quali ty of the system und er test. | |
151 | Make recom mendations for futur e testing efforts. | |
152 | Test Evalu ation Scop e | |
153 | The scope of this Te st Evaluat ion is to verify the functiona lity of th e Patch OR *3.0*435 c ode modifi cation, as determine d by Funct ional, Com ponent Int egration/S ystem, and Regressio n testing. Testing a ctivities followed t he specifi cations ou tlined in the follow ing Master Test Plan : OR*3.0*4 35 Master Test Plan (included in Appendi x A). | |
154 | Test Archi tecture | |
155 | Following are the EP IP test ac counts use d by the L eidos Deve lopment an d SQA Test ing teams to test OR *3.0*435. | |
156 | Developmen t Test Acc ounts | |
157 | (For Unit Testing)SQ A Test Acc ounts | |
158 | (For Funct ional, Reg ression, a nd Compone nt Integra tion and S ystem Test ing)VistAS 1 ( altern ate name: D1S1)VistA G1 (altern ate name: D1G1) Vist AS2 (alter nate name: D1S2) | |
159 | for CPRS G UI testing onlyVistA G2 (altern ate name: D1G2) – | |
160 | for CPRS G UI testing onlyTest Environmen t/Configur ation | |
161 | 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. | |
162 | 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. | |
163 | Installati on Process | |
164 | 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. | |
165 | 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. | |
166 | Test Data | |
167 | The SQA Te sting team utilizes the test d ata in the designate d test acc ounts (D1G 1, D1G2). | |
168 | The test d ata is enc rypted fol lowing the standards set forth by the VA Office of Informati on & Techn ology (OI& T). All Pe rsonally I dentifiabl e Informat ion (PII) and Protec ted Health Informati on (PHI) i s scrubbed and is no t availabl e to the T est Engine ers. | |
169 | 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: | |
170 | AAAHURMMX, XPHY | |
171 | BADHB, HAA DXS | |
172 | FDHUX, YHI J | |
173 | All tests were execu ted manual ly by EPIP Test Engi neers. | |
174 | Issues | |
175 | The follow ing issues were enco untered du ring testi ng of OR*3 .0*435. | |
176 | TitleIssue Descripti onTypeSeve rityN/AN/A N/AN/ATest Execution Log | |
177 | 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. | |
178 | The SQA Te sting team utilizes the Ration al Quality Manager ( RQM) tool for all te sting acti vities. Al l test doc uments are stored in the EPIP repository , includin g the Mast er Test Pl an, Test S uites, Tes t Cases, a nd Test Sc ripts. Tes t executio n is perfo rmed, and test resul ts recorde d, in RQM. 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. | |
179 | The Test E xecution r ecords for OR*3.0*43 5 are incl uded in th e EPIP Pat ch OR*3.0* 435 Master Test Plan . The Mast er Test Pl an is avai lable in A ppendix A. | |
180 | Test Defec t Log | |
181 | 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. | |
182 | Test Resul ts Summary | |
183 | SQA testin g for this intake st arted on S eptember 2 6, 2016 an d ended on March 2, 2018. | |
184 | Test versi on 1 was i nstalled i n the Dev1 Gold2 tes t environm ent after Unit testi ng in Dev1 Silver2 w as complet ed. Upon c ompletion of Integra tion testi ng (Compon ent Integr ation and System tes ting, Func tional tes ting, and Regression testing), one (1) d efect was found and reported. | |
185 | Test versi on 2 was i nstalled i n the Dev1 Gold2 tes t environm ent on Mar ch 2, 2017 after Uni t testing in Dev1 Si lver2 was completed. Upon comp letion of Functional testing a nd Regress ion testin g, one (1) defect wa s found an d reported . | |
186 | Test versi on 3 was r eleased to SQA on Ma rch 15, 20 17 after U nit testin g in Dev1 Silver2 wa s complete d. This te st version was never installed in the De v1 Gold2 t est enviro nment. Cha nges reque sted by th e CPRS tea m during r eview, and a defect that cause d CPRS to display a server err or, were i dentified before pat ch install ation coul d be compl eted. | |
187 | Test versi on 4 was i nstalled i n the Dev1 Gold2 tes t environm ent on Mar ch 16, 201 7 after Un it testing in Dev1 S ilver2 was completed . During F unctional testing, o ne (1) def ect was fo und and re ported. | |
188 | Test versi on 5 was i nstalled i n the Dev1 Gold2 tes t environm ent on Mar ch 22, 201 7 after Un it testing in Dev1 S ilver2 was completed . During F unctional testing, o ne (1) def ect was fo und and re ported. | |
189 | Test versi on 6 was i nstalled i n the Dev1 Gold2 tes t environm ent on Mar ch 24, 201 7 after Un it testing in Dev1 S ilver2 was completed . Upon com pletion of Regressio n testing and Functi onal testi ng, one (1 ) defect w ere found and report ed. | |
190 | Test versi on 7 was i nstalled i n the Dev1 Gold2 tes t environm ent on May 2, 2017 a fter Unit testing in Dev1 Silv er2 was co mpleted. U pon comple tion of In tegration testing (C omponent I ntegration and Syste m testing, Functiona l testing, and Regre ssion test ing), zero (0) defec ts were fo und and re ported. Ho wever, a n ew busines s requirem ent was ad ded to all ow the aut omatically assigned ASAP prior ity to be changed to ROUTINE. This chang e resulted in a new test versi on. | |
191 | Test versi on 8 was i nstalled i n the Dev1 Gold2 tes t environm ent on May 5, 2017 a fter Unit testing in Dev1 Silv er2 was co mpleted. U pon comple tion of In tegration testing (C omponent I ntegration and Syste m testing, Functiona l testing, and Regre ssion test ing), thre e (3) defe cts were f ound and r eported. | |
192 | Test Versi on 9 was i nstalled i n the Dev1 Gold2 tes t environm ent on Jul y 17, 2017 after Uni t testing in Dev1 Si lver2 was completed. Upon comp letion of Integratio n testing (Component Integrati on and Sys tem testin g, Functio nal testin g, and Reg ression te sting), ze ro (0) def ects were found and reported. Although n o defects were found during th e testing of version 9.0, feed back from an IOC tes t site res ulted in a new test version th at modifie s the post -installat ion routin e ORFD435P to ensure that requ ired remot e procedur es are pro perly regi stered if the patch is install ed at a si te that is not runni ng CPRS v3 2. SQA Def ect 673176 was creat ed to addr ess this i ssue. | |
193 | Test Versi on 10 was installed in the Dev 1 Gold2 te st environ ment on Fe bruary 7, 2018 after Unit test ing in Dev 1 Silver2 was comple ted. Upon completion of Integr ation test ing (Funct ional test ing and Re gression t esting), z ero (0) de fects were found and reported. Although no defects were foun d during t he testing of versio n 10.0, fe edback fro m IOC test sites res ulted in a new versi on that re moves the dependency on OR*3.0 *377 and f ixes an is sue with m ultiple RP C registra tions. | |
194 | Test versi on 11 was installed in the Dev 1 Gold2 te st environ ment on Fe bruary 22, 2018 afte r Unit tes ting in De v1 Silver2 was compl eted. Upon completio n of Integ ration tes ting (Func tional tes ting and R egression testing), zero (0) d efects wer e found an d reported . | |
195 | Defect Sev erity and Priority L evels | |
196 | 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. | |
197 | 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. | |
198 | Total Defe cts by Sev erity Leve l | |
199 | 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. | |
200 | Breakdown of Test Re sults | |
201 | Testing wa s complete d on March 2, 2018. All test r esults wer e recorded in RQM. D etailed re sults are available in the EPI P Patch OR *3.0*435 M aster Test Plan (see Appendix A). | |
202 | Performanc e Testing | |
203 | Performanc e testing was not co nducted. | |
204 | Test Cover age | |
205 | The EPIP P atch OR*3. 0*435 Mast er Test Pl an contain s details on test co verage (se e Appendix A). | |
206 | Requiremen ts Covered | |
207 | The requir ements for OR*3.0*43 5 are stor ed in the Rational D ynamic Obj ect Orient ed Require ments Syst em (DOORS) . The test cases use d to valid ate that t he require ments have been addr essed are stored in RQM and ar e linked t o the requ irements, providing full trace ability. T he user st ories stor ed in the Rational C hange and Configurat ion Manage ment (CCM) applicati on (a.k.a. Rational Team Conce rt (RTC)) are linked to the re quirements and test cases. | |
208 | The follow ing links provide ac cess to th e various EPIP repos itories in the Ratio nal toolki t. | |
209 | EPIP (RM) – Go to Ar tifacts, t hen Browse Artifacts , and then search fo r the desi red patch number. Th e patch fo lder conta ins the re quirements for that patch. | |
210 | https://cl m.rational .oit. DNS /rm/web#ac tion=com.i bm.rdm.web .pages.sho wFoundatio nProjectDa shboard&pr ojectURI=h ttps%3A%2F %2Fclm.rat ional.oit. DNS %2Frm%2Fpr ocess%2Fpr oject-area s%2F_ZZeMg l7AEeSE8-z V-rLMog&vv c.configur ation=http s%3A%2F%2F clm.ration al.oit. DNS %2Frm%2Fcm %2Fstream% 2F_1ynVoNK DEeWADNdRz gPDKQ | |
211 | EPIP (QM) – Go to Pl anning, th en Browse Test Plans , and then search fo r the desi red Master Test Plan . The Mast er Test Pl an and tes t cases ar e linked t o requirem ents. | |
212 | https://cl m.rational .oit. DNS /qm/web/co nsole/EPIP %20(QM)#ac tion=com.i bm.rqm.pla nning.home .actionDis patcher&su bAction=vi ewUserHome | |
213 | EPIP (CM) – Go to Pl ans, then All Plans, and then search for the desir ed sprint Plan. The user stori es in each Plan are linked to requiremen ts and tes t cases. | |
214 | https://cl m.rational .oit. DNS /ccm/web/p rojects/EP IP%20(CM)# action=com .ibm.team. dashboard. viewDashbo ard | |
215 | Section 50 8 Complian ce Coverag e | |
216 | Section 50 8 test res ults will be reporte d to VA in the follo wing docum ents: | |
217 | EPIP_VASec tion508_11 94_21_Soft ware_Check list_(OR_3 .0_435) | |
218 | EPIP_VASec tion508_11 94_31_Func tional_Che cklist_(OR _3.0_435) | |
219 | EPIP_VASec tion508_11 94_41_Docu mentation_ Checklist _(OR_3.0_4 35) | |
220 | EPIP_VASec tion508_Co mpliance_T est_Result s _(OR_3.0 _435) | |
221 | EPIP_VASec tion508_Co nformance_ Validation _Statement _(OR_3.0_ 435) | |
222 | EPIP_VASec tion508_Se lf-Certifi cation_Doc ument_(OR_ 3.0_435) | |
223 | EPIP_VASec tion508_Ve rifiable_O bjective_E vidence_(O R_3.0_435) | |
224 | Suggested Actions | |
225 | Leidos rec ommends mo ving this patch to I OC testing . | |
226 | Defect Sev erity and Priority D efinitions | |
227 | The classi fication o f defects within a s ystem exam ines both the severi ty and pri ority of t he defect. | |
228 | 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. | |
229 | Priority d etermines the speed with which a given d efect must be repair ed. | |
230 | 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 . | |
231 | Defect Sev erity Leve l | |
232 | The follow ing subsec tions iden tify the d efect seve rity level s. | |
233 | Severity L evel 1 – C ritical | |
234 | 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. | |
235 | 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. | |
236 | 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. | |
237 | 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. | |
238 | Any defect that caus es corrupt ion of dat a from a r esult of t he system (as oppose d to user error). | |
239 | 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 . | |
240 | Loss of fu nctionalit y resultin g in erron eous eligi bility/enr ollment de terminatio ns or comm unications not being sent. | |
241 | Severity L evel 2 - H igh | |
242 | 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. | |
243 | A major de fect in th e function ality that does not result in corruption of data. | |
244 | 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: | |
245 | 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 . | |
246 | Any defect that does not confo rm to Sect ion 508 st andards. | |
247 | Any defect that resu lts in ina ccurate or missing r equirement s. | |
248 | Any defect that resu lts in inv alid authe ntication or authent ication of an invali d end user . | |
249 | Severity L evel 3 - M edium | |
250 | 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. | |
251 | Minor func tionality is not wor king as in tended and a workaro und exists but is no t suitable for long term use | |
252 | The inabil ity of a v alid user to access the system consisten t with gra nted privi leges | |
253 | 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 | |
254 | Any defect producing cryptic, incorrect, or inappr opriate er ror messag es | |
255 | 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 | |
256 | 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. | |
257 | Severity L evel 4 - L ow | |
258 | 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. | |
259 | Minor loss of, or de fect in th e function ality wher e a long t erm use ex ists | |
260 | Low-level cosmetic i ssues. | |
261 | Priority C lassificat ions | |
262 | 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. | |
263 | Priority 1 - Resolve Immediate ly | |
264 | 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. | |
265 | Priority 2 - Give Hi gh Attenti on | |
266 | 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. | |
267 | Priority 3 - Normal Queue | |
268 | 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. | |
269 | Priority 4 - Low Pri ority | |
270 | 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. | |
271 | Optional T ables, Cha rts, and G raphs | |
272 | None. | |
273 | Document A pproval Si gnatures | |
274 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
275 | Program/Pr oject Mana ger | |
276 | Date | |
277 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
278 | Business S ponsor Rep resentativ e | |
279 | Date | |
280 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
281 | Test Lead | |
282 | Date | |
283 | Appendix A - Test Ex ecution Lo g | |
284 | The Test E xecution R ecords for OR*3.0*43 5 are incl uded in th e EPIP Pat ch OR*3.0* 435 Master Test Plan . | |
285 | ||
286 | Appendix B – Defect Log | |
287 | Thirteen ( 13) defect s were fou nd during testing of OR*3.0*43 5. All def ects have been resol ved. | |
288 | SQA Defect IDAffecte d ScreenAf fected Fie ldObserved BehaviorS everityDes criptionN/ AN/AN/AN/A N/ANo defe cts were f ound durin g Unit Tes ting of ve rsion 1.0. N/AN/AN/AN /AN/ANo de fects were found dur ing Compon ent Integr ation/Syst ems Testin g of versi on 1.0.N/A N/AN/AN/AN /ANo defec ts were fo und during Regressio n testing of version 1.0.56573 1CPRS Orde rs TabN/AI f ASAP doe s not exis t in the O rder Urgen cy File, a server er ror occurs .HighOne ( 1) defect was found during Fun ctional Te sting of v ersion 1.0 .N/AN/AN/A N/AN/ANo d efects wer e found du ring Unit 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 .565799CPR S Orders T abN/AIf AS AP has bee n deleted and the IE N called c annot be l ocated, a server err or is disp layed in C PRS.HighOn e (1) defe ct was fou nd during Functional Testing o f version 2.0.N/AN/A N/AN/AN/AN o defects were found during Un it Testing of versio n 3.0.5658 26Inpatien t Medicati on Sign Or ders dialo g boxN/AIf ASAP has been delet ed from th e Order Ur gency file and the I EN called cannot be located, a server er ror is dis played in CPRS.HighO ne (1) def ect was fo und before installat ion could be complet ed. Test v ersion 3.0 was not i nstalled. 565826Inpa tient Medi cation Sig n Orders d ialog boxN /AIf ASAP has been d eleted fro m the Orde r Urgency file and t he IEN cal led cannot be locate d, a serve r error is displayed in CPRS.H ighOne (1) defect wa s found be fore insta llation co uld be com pleted. Te st version 3.0 was n ot install ed. N/AN/A N/AN/AN/AN o defects were found during Un it Testing of versio n 4.0.5658 36Orders T ab, Inpati ent Medica tionN/APat ch Install ation, CPR S & Server Error if IRM does n ot enter a n ASAP Alt ernative.H ighOne (1) defect wa s found an d reported during Fu nctional T esting of version 4. 0.N/AN/AN/ AN/AN/ANo defects we re found d uring Unit Testing o f version 5.0.565847 Orders Tab Inpatient Medicatio n dialog b ox Priorit yOverride the Defaul t Value of ASAP with Routine f or Give Ad ditional D ose Now.N/ AOne (1) d efect was found duri ng Functio nal Testin g of versi on 5.0.N/A N/AN/AN/AN /ANo defec ts were fo und during Unit Test ing of ver sion 6.0.N /AN/AN/AN/ AN/ANo def ects were found duri ng Regress ion testin g of versi on 6.0.50 PORT CPRS Order s Tab Inpa tient Medi cation Com plex Order sComplex O rder Warni ng notific ation is n o longer d isplayingH ighOne (1) new defec t was foun d during F unctional Testing of version 6 .0.N/AN/AN /AN/AN/ANo defects w ere found during Uni t Testing of version 7.0.N/AN/ AN/AN/AN/A No defects were foun d during C omponent I ntegration /Systems T esting of version 7. 0.N/AN/AN/ AN/AN/ANo defects we re found d uring Regr ession tes ting of ve rsion 7.0. N/AN/AN/AN /AN/ANo de fects were found dur ing Functi onal testi ng of vers ion 7.0.Al though no defects we re found d uring the testing of version 7 .0, a new business r equirement was added that allo ws the aut omatic ASA P priority to be cha nged back to ROUTINE . This ena bles Give additional dose now orders to have two o rders with the prior ity ROUTIN E.N/AN/AN/ AN/AN/ANo defects we re found d uring Unit Testing o f version 8.0.N/AN/A N/AN/AN/AN o defects were found during Co mponent In tegration/ Systems Te sting of v ersion 8.0 .527066Ord ers tab, I npatient m edication dialog box PriorityWh en Priorit y field is blank and Give Addi tional Dos e Now is c hecked, tw o errors o ccur.HighT hree (3) d efects wer e found du ring Regre ssion test ing of ver sion 8.0.5 65887CPRS Orders Tab Inpatient Medicatio n (Complex )PriorityW hen Priori ty field i s blank fo r a Comple x Order an d Give Add itional Do se is chec ked, an er ror occurs .High56589 6Orders Ta b, Inpatie nt Medicat ion Quick Order (Com plex) | |
289 | GAD fieldG ive Additi onal Dose NowGive Ad ditional D ose Now fl ag not ret ained for some Compl ex Quick O rders.High N/AN/AN/AN /AN/ANo de fects were found dur ing Unit T esting of version 9. 0.N/AN/AN/ AN/AN/ANo defects we re found d uring Comp onent Inte gration/Sy stems Test ing of ver sion 9.0.N /AN/AN/AN/ AN/ANo def ects were found duri ng Regress ion testin g of versi on 9.0.673 176Remote Procedure ORWDPS1 GE TPRIOROrde rs Tab Err or Message displays when order ing an inp atient med ication if the RPC i s not pres ent.Medium No defects were foun d during F unctional testing of version 9 .0. | |
290 | However, o ne (1) def ect was re ported dur ing IOC te sting. SQA Defect 67 3176 was c reated to address th is issue, resulting in test ve rsion 10.0 .N/AN/AN/A N/AN/ANo d efects wer e found du ring Unit Testing of version 1 0.0.N/AN/A N/AN/AN/AN o defects were found during Re gression T esting of version 10 .0.688759 | |
291 | 688763 | |
292 | Patch Inst allation | |
293 | Patch Inst allationN/ A | |
294 | N/AORWDPS1 GETPRIOR and GETPRI EN are reg istered mu ltiple tim es to OR C PRS GUI Ch art. | |
295 | Patch has a dependen cy on OR* 3.0*377, w hich is de layed.Medi um | |
296 | HighNo def ects were found duri ng Functio nal testin g of versi on 10.0. | |
297 | However, t wo (2) def ects were reported d uring IOC testing. S QA defects 688759 an d 688763 w ere create d to addre ss these i ssues, res ulting in test versi on 11.0.N/ AN/AN/AN/A N/ANo defe cts were f ound durin g Unit Tes ting of ve rsion 11.0 .N/AN/AN/A N/AN/ANo d efects wer e found du ring Regre ssion Test ing of ver sion 11.0. N/AN/AN/AN /AN/ANo de fects were found dur ing Functi onal testi ng of vers ion 11.0. | |
298 | _159152455 3.pdf |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.