Produced by Araxis Merge on 6/26/2018 12:46:11 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 | CIF.zip | EPIP_Test_Evaluation_(OR_3_0_444).doc | Mon Jun 25 13:26:28 2018 UTC |
2 | CIF.zip | EPIP_Test_Evaluation_(OR_3_0_444).doc | Mon Jun 25 15:53:16 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 4 | 588 |
Changed | 3 | 6 |
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 | Test Evalu ation Temp lateExisti ng Product Intake Pr ogram (EPI P) | |
2 | Patch OR*3 .0*444 | |
3 | Test Evalu ation | |
4 | ||
5 | Department of Vetera ns Affairs | |
6 | November 2 017 | |
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 onAuthor11 /17/20171. 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 | 46.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 | 57. | |
70 | Test Cover age | |
71 | ||
72 | ||
73 | 57.1. | |
74 | Requiremen ts Covered | |
75 | ||
76 | ||
77 | 57.2. | |
78 | Section 50 8 Complian ce Coverag e | |
79 | ||
80 | ||
81 | 68. | |
82 | Suggested Actions | |
83 | ||
84 | ||
85 | 69. | |
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 | 79.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 | 89.2.2. | |
118 | Priority 2 - Give Hi gh Attenti on | |
119 | ||
120 | ||
121 | 89.2.3. | |
122 | Priority 3 - Normal Queue | |
123 | ||
124 | ||
125 | 89.2.4. | |
126 | Priority 4 - Low Pri ority | |
127 | ||
128 | ||
129 | 810. | |
130 | Optional T ables, Cha rts, and G raphs | |
131 | ||
132 | ||
133 | 911. | |
134 | Document A pproval Si gnatures | |
135 | ||
136 | ||
137 | 10Appendix A - Test Execution Log | |
138 | ||
139 | ||
140 | 11Appendix 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 Patch OR *3.0*444 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 44 Master Test Plan (included in Appendi x 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 OR *3.0*444. | |
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 ( altern ate name: D1S1)VistA G1 (altern ate name: D1G1) Vist AS2 (alter nate 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 (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. | |
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 testin g of OR*3. 0*444. | |
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 Manager ( QM) tool f or all tes ting activ ities. All test docu ments are stored in the EPIP r epository, including the Maste r Test Pla n, Test Su ites, Test Cases, an d Test Scr ipts. Test execution is perfor med, and t est result s recorded , in Ratio nal QM. Th e Test Eng ineer adds the test results to the Test Execution records to indicate whether te sting achi eved Pass or Fail st atus. | |
178 | The Test E xecution r ecords for OR*3.0*44 4 are incl uded in th e EPIP Pat ch OR*3.0* 444 Master Test Plan . The Mast er Test Pl an is avai lable in A ppendix 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 ld2 test e nvironment on Novemb er 20, 201 6 and ende d on Novem ber 14, 20 17. | |
183 | Test versi on 1 was i nstalled i n the Dev1 Gold2 tes t environm ent on Nov ember 20, 2016 after Unit test ing in Dev 1 Silver2 was comple ted. Upon completion of Integr ation test ing (Compo nent Integ ration and System Te sting, Fun ctional Te sting, and Regressio n Testing) , one (1) defect was found and reported. | |
184 | Test versi on 2 was i nstalled i n the Dev1 Gold2 tes t environm ent on Nov ember 21, 2016 after Unit test ing in Dev 1 Silver2 was comple ted. Upon completion of Integr ation test ing (Compo nent Integ ration and System Te sting, Fun ctional Te sting, and Regressio n Testing) , one (1) defect was found and reported. During te sting of T est versio n 2, it wa s determin ed by the VA stakeho lders that an On/Off switch is needed fo r the UAP functional ity. The E PIP Develo pment team created T est versio n 3 to res olve the r eported de fect and a dd the On/ Off switch functiona lity. | |
185 | Test versi on 3 was i nstalled i n the Dev1 Gold2 tes t environm ent on Nov ember 29, 2016 after Unit test ing in Dev 1 Silver2 was comple ted. Upon completion of Integr ation test ing (Compo nent Integ ration and System Te sting, Fun ctional Te sting, and Regressio n Testing) , zero (0) defects w ere found and report ed. Howeve r, two (2) defects w ere identi fied durin g review b y the VA C PRS team a nd the CPR S Workgrou p. Test ve rsion 4 wa s created to address the defec ts resulti ng from th e CPRS tea m reviews; specifica lly, this test versi on modifie d the sort ing of Ser vices on t he CPRS Or ders tab a nd removed the “Revi ewed” colu mn from th e Orders v iew and th e Discharg e Meds vie w. | |
186 | Test versi on 4 was i nstalled i n the Dev1 Gold2 tes t environm ent on Dec ember 08, 2016 after Unit test ing in Dev 1 Silver2 was comple ted. Upon completion of Functi onal Testi ng, one (1 ) defect w as found a nd reporte d. | |
187 | Test versi on 5 was i nstalled i n the Dev1 Gold2 tes t environm ent on Feb ruary 02, 2017 after Unit test ing in Dev 1 Silver2 was comple ted. Upon completion of Functi onal Testi ng, zero ( 0) defects were foun d and repo rted; howe ver, a har d coded er ror was di scovered r esulting f rom a miss ing requir ed build o f the nati onally rel eased patc h HMP*2.0* 2 for CPRS GUI testi ng. Test v ersion 6 w as created to includ e the requ ired build . | |
188 | Test versi on 6 was i nstalled i n the Dev1 Gold2 tes t environm ent on Mar ch 21, 201 7 after Un it testing in Dev1 S ilver2 was completed . Upon com pletion of Functiona l Testing, zero (0) defects we re found a nd reporte d; however , two test sites for CPRS v32 reported i ssues with test vers ion 6. Tes t version 7 was crea ted to sen d the late st version of this p atch to CP RS and Lei dos SQA in advance o f the next increment al CPRS bu ild. | |
189 | Test versi on 7 was i nstalled i n the Dev1 Gold2 tes t environm ent on May 1, 2017 a fter Unit testing in Dev1 Silv er2 was co mpleted. U pon comple tion of Fu nctional T esting, ze ro (0) def ects were found and reported. During the product d emo, stake holders re quested th at medicat ion orders be listed in alphab etical ord er on the UAP Screen . Test ver sion 8 was created t o address this reque st. | |
190 | Test versi on 8 was i nstalled i n the Dev1 Gold2 tes t environm ent on May 25, 2017 after Unit testing i n Dev1 Sil ver2 was c ompleted. Upon compl etion of F unctional Testing, o ne (1) def ect was fo und and re ported. | |
191 | Test versi on 9 was i nstalled i n the Dev1 Gold2 tes t environm ent on May 31, 2017 after Unit testing i n Dev1 Sil ver2 was c ompleted. It includ ed a reque st from th e Stakehol ders to up date the D ischarge M eds Review page head er to disp lay Discha rge Meds R eview - Ac tive, Pend ing, Expir ed, & D/C’ d <90 days . Upon co mpletion o f Function al Testing , two (2) defects we re found a nd reporte d. | |
192 | Test versi on 10 was installed in the Dev 1 Gold2 te st environ ment on Se ptember 11 , 2017 aft er Unit te sting in D ev1 Silver 2 was comp leted. Vis tA code fr om Patch O R*3.0*456 was added to OR*3.0* 444 becaus e OR*3.0*4 56 is sche duled to b e released before OR *3.0*444. Upon compl etion of F unctional Testing, f our (4) de fects were found and reported. | |
193 | Test versi on 11 was installed in the Dev 1 Gold 2 t est enviro nment on S eptember 2 7, 2017 af ter Unit t esting in Dev1 Silve r2 was com pleted. U pon comple tion of Fu nctional T esting, ze ro (0) def ects were found. | |
194 | Note: CPRS 32 test ve rsion (tv) 38 was in stalled in Dev1 Gold 2 on Novem ber 10, 20 17. Upon c ompletion of Functio nal Testin g, zero (0 ) defects were found . | |
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 Novem ber 14, 20 17. All te st results were reco rded in Ra tional QM. Detailed results ar e availabl e in the E PIP Patch OR*3.0*444 Master Te st Plan (s ee Appendi x 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*444 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*44 4 are stor ed in the Rational R equirement s Manageme nt (RM) ap plication. The test cases stor ed in Rati onal Quali ty Managem ent (QM) a re used to validate that the r equirement s have bee n addresse d, providi ng full tr aceability . The user stories s tored in R ational Co nfiguratio n Manageme nt (CM) ar e linked t o the requ irements i n RM and t est cases in QM. | |
208 | The follow ing links provide ac cess to th e various EPIP repos itories in the Ratio nal toolki t. If link translati on issues prevent di rect acces s, copy an d paste th e URLs int o your bro wser. | |
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_Co mpliance_T est_Result s_(OR_3.0_ 444) | |
218 | EPIP_VASec tion508_11 94_21_Soft ware_Check list_(OR_3 .0_444) | |
219 | EPIP_VASec tion508_11 94_31_Func tional_Che cklist_(OR _3.0_444) | |
220 | EPIP_VASec tion508_11 94_41_Docu mentation_ Checklist_ (OR_3.0_44 4) | |
221 | EPIP_VASec tion508_Se lfCertific ationDocum ent_(OR_3. 0_444) | |
222 | EPIP_VASec tion508_Co nformanceV alidationS tatement_( OR_3.0_444 ) | |
223 | EPIP_VASec tion_508_V erifiable_ Objective_ Evidence_( OR_3.0_444 ) | |
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*44 4 are incl uded in th e EPIP Pat ch OR*3.0* 444 Master Test Plan . | |
285 | ||
286 | Appendix B – Defect Log | |
287 | Thirteen ( 13) defect s were fou nd during testing of OR*3.0*44 4 and CPRS 32. All de fects have been reso lved. | |
288 | 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.042 2461CPRS G UI Main sc reenCPRS G UI Log in promptN/AH ighOne (1) defect wa s found du ring Funct ional Test ing of ver sion 1.0N/ AN/AN/AN/A N/ANo defe cts were f ound durin g Unit Tes ting of ve rsion 2.0N /AN/AN/AN/ AN/ANo def ects were found duri ng Compone nt Integra tion/Syste ms Testing of versio n 2.0N/AN/ AN/AN/AN/A No defects were foun d during R egression testing of version 2 .0426440CP RS GUI UAP pageDisco ntinue Med ication Or derN/AHigh One (1) de fect was f ound durin g Function al Testing of versio n 2.0N/AN/ AN/AN/AN/A No defects were foun d during U nit testin g of versi on 3.0N/AN /AN/AN/AN/ ANo defect s were fou nd during Component Integratio n and Syst em testing of versio n 3.0N/AN/ AN/AN/AN/A No defects were foun d during R egression testing of version 3 .0Defect I DAffected ScreenAffe cted Field Observed B ehaviorSev erityDescr iption4402 93CPRS GUI Remove CPR S Reviewed column fr om Orders PageN/AHig hNo defect s were fou nd during Functional testing o f version 3.0; howev er, two (2 ) defects were found during VA CPRS team review of version 3 .0.440315C PRS GUI Se rvices sor ting in Or ders PageN /AHighN/AN /AN/AN/AN/ ANo defect s were fou nd during Unit Testi ng of vers ion 4.0N/A N/AN/AN/AN /ANo defec ts were fo und during Component Integrati on and Sys tem testin g of versi on 4.0N/AN /AN/AN/AN/ ANo defect s were fou nd during Regression testing o f version 4.0461230C PRS GUIMis sing Revie w column i n UAP page N/AHighOne (1) defec t was foun d during F unctional Testing of version 4 .0N/AN/AN/ AN/AN/ANo defects we re found d uring Unit testing o f version 5.0N/AN/AN /AN/AN/ANo defects w ere found during Com ponent Int egration a nd System testing of version 5 .0N/AN/AN/ AN/AN/ANo defects we re found d uring Regr ession tes ting of ve rsion 5.0N /AN/AN/AN/ AN/ANo def ects were found duri ng Functio nal Testin g of versi on 5.0Alth ough no de fects were found dur ing testin g of versi on 5.0, a hard coded error was discovere d. This er ror result ed from a missing re quired bui ld of the nationally released patch HMP* 2.0*2 for CPRS GUI t esting. Te st version 6.0 was c reated to include th e required build.N/A N/AN/AN/AN /ANo defec ts were fo und during Unit test ing of ver sion 6.0N/ AN/AN/AN/A N/ANo defe cts were f ound durin g Function al testing of versio n 6.0Altho ugh no def ects were found duri ng testing of versio n 6.0, two test site s for CPRS v32 repor ted issues with test version 6 . Test ver sion 7 was created t o send the latest ve rsion of t his patch to CPRS an d Leidos S QA in adva nce of the next incr emental CP RS build.N /AN/AN/AN/ AN/ANo def ects were found duri ng Unit te sting of v ersion 7.0 N/AN/AN/AN /AN/ANo de fects were found dur ing Functi onal testi ng of vers ion 7.0Alt hough no d efects wer e found du ring testi ng of vers ion 7.0, s takeholder s requeste d that med ication or ders be li sted in al phabetical order on the UAP Sc reen. Test version 8 was creat ed to addr ess this r equest.N/A N/AN/AN/AN /ANo defec ts were fo und during Unit test ing of ver sion 8.053 1763CPRS G UIOrders t ab, CPRS E rror Messa geMissing RPC, Provi der with l imited cre dentialsHi ghOne (1) defect was found dur ing Functi onal testi ng of vers ion 8.0Tes t version 9 was crea ted to add ress defec t 531763 a nd a stake holder req uest that the Discha rge Meds h eader be u pdated. N /AN/AN/AN/ AN/ANo def ects were found duri ng Unit te sting of v ersion 9.0 580151 | |
289 | CPRS GUIOr ders tab, UAP page, Review req uest and C ancelRevie wed column displays decisionHi gh | |
290 | Two (2) de fects were found dur ing Functi onal testi ng of vers ion 9.0581 246CPRS GU I | |
291 | Orders tab , UAP page , Error Me ssageRPC n ot registe red, Provi der with l imited cre dentialsHi ghTest ver sion 10 wa s created to address the two d efects in version 9 and to add code from Patch OR* 3.0*456, w hich is be ing releas ed prior t o OR*3.0*4 44. During the testi ng of vers ion 10, CP RS32 was u pdated, wh ich resolv ed defects 585440 an d 590187.N /ACPRS | |
292 | GUIOrders tab, Disch arge Meds Review Pag eAll Order s are disp layingN/AO ne (1) def ect was fo und during Unit test ing of ver sion 10.0 as a resul t of CPRS code chang es from an other grou p.585440CP RS GUIOrde rs tab, UA P ViewCont inue flag not displa yed in Rev iewed colu mnHigh | |
293 | Four (4) d efects wer e found du ring Funct ional test ing of ver sion 10.05 90187CPR | |
294 | GUIOrders tab, UAP V iewNon-VA Meds not d isplaying in Service s columnHi gh586943CP RS | |
295 | GUIOrders tab UAP Vi ewNon-VA M edication, Reviewed flag displ ays and sh ould not a fter a Can celHigh590 719CPRS | |
296 | GUIOrders tab, UAP V iewOutpati ent, Renew does not display in Reviewed columnHigh Test versi on 11 was created to address t wo defects in test v ersion 10 that were not correc ted by the new CPRS version. T he defects corrected in test v ersion 11 were 58694 3 and 5907 19.N/AN/AN /AN/AN/ANo defects w ere found during Uni t testing of version 11.0N/AN/ AN/AN/AN/A No defects were foun d during Functional testing o f version 11.0CPRS32 tv38 addr essed a mo dification to the UA P cancel c ode that w as reques ted by the CPRS Code Reviewer. The defec t correcte d in CPRS3 2 tv38 was 622821. N/AN/AN/AN /AN/ANo de fects were found dur ing Unit t esting of CPRS32 tv3 8 and OR*3 .0*444 tv 11.N/AN/AN /AN/AN/ANo defects w ere found during Fun ctional te sting of C PRS32 tv38 and OR*3. 0*444 tv 1 1. | |
297 | _159142032 3.pdf |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.