Produced by Araxis Merge on 7/31/2018 9:10:40 AM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
# | Location | File | Last Modified |
---|---|---|---|
1 | EPIP_CiF.zip\215-452\docs | EPIP_Test_Evaluation_(PSO_7.0_452,_PSS_1.0_215).doc | Thu Jul 26 12:10:26 2018 UTC |
2 | EPIP_CiF.zip\215-452\docs | EPIP_Test_Evaluation_(PSO_7.0_452,_PSS_1.0_215).doc | Thu Jul 26 12:20:21 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 7 | 580 |
Changed | 6 | 12 |
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 | Leidos Pro prietary | |
2 | Existing P roduct Int ake Progra m (EPIP) | |
3 | Patches PS O*7.0*452 and PSS*1. 0*215 | |
4 | Test Evalu ation | |
5 | ||
6 | Department of Vetera ns Affairs | |
7 | July 2018 | |
8 | Version 1. 0 | |
9 | Revision H istory | |
10 | 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. | |
11 | DateVersio nDescripti onAuthor07 /18/20181. 0Initial d ocument.EP IP Project TeamArtif act Ration ale | |
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 | 36.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 | 69.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 | 710. | |
131 | Optional T ables, Cha rts, and G raphs | |
132 | ||
133 | ||
134 | 811. | |
135 | Document A pproval Si gnatures | |
136 | ||
137 | ||
138 | 9Appendix A - Test E xecution L og | |
139 | ||
140 | ||
141 | 10Appendix 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 code mod ifications delivered in Patche s PSO*7.0* 452 and PS S*1.0*215, as determ ined by Fu nctional, Component Integratio n/System, and Regres sion testi ng. Testin g activiti es followe d the spec ifications outlined in the fol lowing Mas ter Test P lan: PSO*7 .0*452 and PSS*1.0*2 15 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 PS O*7.0*452 and PSS*1. 0*215. | |
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 (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. | |
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 | No issues were encou ntered dur ing testin g of patch es PSO*7.0 *452 and P SS*1.0*215 . | |
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 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. | |
179 | The Test E xecution r ecords for PSO*7.0*4 52 and PSS *1.0*215 a re include d in the E PIP Patche s PSO*7.0* 452 and PS S*1.0*215 Master Tes t Plan. Th e Master T est Plan i s availabl e in Appen dix 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 O ctober 16, 2017 and ended on J uly 16, 20 18. | |
184 | Test versi on 1 was i nstalled i n the Dev1 Gold2 tes t environm ent after Unit testi ng in Dev1 Silver1 w as complet ed. During Functiona l testing one (1) de fect was f ound and r eported. | |
185 | Test versi on 2 was i nstalled i n the Dev1 Gold2 tes t environm ent on Dec ember 1, 2 017 after Unit testi ng in Dev1 Silver1 w as complet ed. Upon c ompletion of Functio nal testin g, two (2) defects w ere found and report ed. | |
186 | Test versi on 3 was i nstalled i n the Dev1 Gold2 tes t environm ent on Dec ember 20, 2017 after Unit test ing in Dev 1 Silver1 was comple ted. Durin g Function al testing , a MOCHA 2.1 patch was releas ed that sh ared a rou tine (PSOD EM) with P SO*7.0*452 and that code was a bsorbed. O ne (1) def ect was fo und and re ported. | |
187 | Test versi on 4 was i nstalled i n the Dev1 Gold2 tes t environm ent on Mar ch 14, 201 8 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), t wo (2) def ects were found and reported. | |
188 | Test versi on 5 was i nstalled i n the Dev1 Gold2 tes t environm ent on May 17, 2018 after Unit testing i n Dev1 Sil ver1 was c ompleted. Upon compl etion of F unctional testing, t wo (2) def ects were found and reported. | |
189 | Test versi on 6 was i nstalled i n the Dev1 Gold2 tes t environm ent on Jun e 5, 2018 after Unit testing i n Dev1 Sil ver1 was c ompleted. Upon compl etion of F unctional testing an d Regressi on testing , two (2) defects we re found a nd reporte d. During the stakeh older demo , addition al changes to the Pr int from S uspense he lp text an d prompt d efault val ue were re quested, r esulting i n Test ver sion 7. | |
190 | Test versi on 7 was i nstalled i n the Dev1 Gold2 tes t environm ent on Jun e 22, 2018 after Uni t testing in Dev1 Si lver1 was completed. Upon comp letion of Functional testing a nd Regress ion testin g, zero (0 ) defects were found and repor ted. | |
191 | Defect Sev erity and Priority L evels | |
192 | 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. | |
193 | 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. | |
194 | Total Defe cts by Sev erity Leve l | |
195 | 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. | |
196 | Breakdown of Test Re sults | |
197 | Testing wa s complete d on July 16, 2018. All test r esults wer e recorded in RQM. D etailed re sults are available in the EPI P Patches PSO*7.0*45 2 and PSS* 1.0*215 Ma ster Test Plan (see Appendix A ). | |
198 | Performanc e Testing | |
199 | Performanc e testing was not co nducted. | |
200 | Test Cover age | |
201 | The EPIP P atch PSO*7 .0*452 Mas ter Test P lan contai ns details on test c overage (s ee Appendi x A). | |
202 | Requiremen ts Covered | |
203 | The requir ements for this patc h 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. | |
204 | The follow ing links provide ac cess to th e various Outpatient Pharmacy (PSO) and Pharmacy D ata Manage ment (PDM) repositor ies in the Rational toolkit. I f link tra nslation i ssues prev ent direct access, c opy and pa ste the UR Ls into yo ur browser . | |
205 | Outpatient Pharmacy (RM) - Go to Artifac ts. Locate the EPIP folder on the left s ide of the page and expand it to display patch fol ders. Each patch fol der contai ns the req uirements for the pa tch number shown in the folder name. | |
206 | 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/_4s8 KwXkhEea6E -3s3yro6A/ components /_5XaEEHkh Eea6E-3s3y ro6A | |
207 | Pharmacy D ata Manage ment (RM) - Go to Ar tifacts. L ocate the EPIP folde r on the l eft side o f the page and expan d it to di splay patc h folders. Each patc h folder c ontains th e requirem ents for t he patch n umber show n in the f older name . | |
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/_Y7C 2AchrEeanU dQ87CKe9A/ components /_Zo8d0Mhr EeanUdQ87C Ke9A | |
209 | PSO (QM) – Go to Pla nning, the n Browse T est Plans, and then search for the desir ed Master Test Plan. 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/Outp atient_Pha rmacy%20(Q M)#action= com.ibm.rq m.planning .home.acti onDispatch er&subActi on=viewUse rHome | |
211 | PDM (QM) – Go to Pla nning, the n Browse T est Plans, and then search for the desir ed Master Test Plan. The Maste r Test Pla n and test cases are linked to requireme nts. | |
212 | https://cl m.rational .oit. DNS /qm/web/co nsole/PDM% 20(QM)#act ion=com.ib m.rqm.plan ning.home. actionDisp atcher&sub Action=vie wUserHome | |
213 | PSO (CM) – Go to Pla ns, then A ll Plans, and then s earch for the desire d Sprint P lan. The u ser storie s in each Plan are l inked to r equirement s and test cases. | |
214 | https://cl m.rational .oit. DNS /ccm/web/p rojects/Ou tpatient_P harmacy%20 (CM)#actio n=com.ibm. team.dashb oard.viewD ashboard | |
215 | PDM (CM) – Go to Pla ns, then A ll Plans, and then s earch for the desire d Sprint P lan. The u ser storie s in each Plan are l inked to r equirement s and test cases. | |
216 | https://cl m.rational .oit. DNS /ccm/web/p rojects/PD M%20(CM)#a ction=com. ibm.team.d ashboard.v iewDashboa rd | |
217 | Section 50 8 Complian ce Coverag e | |
218 | Section 50 8 testing for this p atch will be complet ed at a la ter time. Test resul ts will be reported to VA in t he followi ng documen ts: | |
219 | EPIP_VASec tion508_Co mpliance_T est_Result s_(PSO_7.0 _452,_PSS_ 1.0_215) | |
220 | EPIP_VASec tion508_In take_Docum ent_(PSO_7 .0_452,_PS S_1.0_215) | |
221 | EPIP_VASec tion508_Ve rifiable_O bjective_E vidence_(P SO_7.0_452 ,_PSS_1.0_ 215) | |
222 | Suggested Actions | |
223 | Leidos rec ommends mo ving this patch to I OC testing . | |
224 | Defect Sev erity and Priority D efinitions | |
225 | The classi fication o f defects within a s ystem exam ines both the severi ty and pri ority of t he defect. | |
226 | 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. | |
227 | Priority d etermines the speed with which a given d efect must be repair ed. | |
228 | 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 . | |
229 | Defect Sev erity Leve l | |
230 | The follow ing subsec tions iden tify the d efect seve rity level s. | |
231 | Severity L evel 1 – C ritical | |
232 | 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. | |
233 | 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. | |
234 | 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. | |
235 | 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. | |
236 | Any defect that caus es corrupt ion of dat a from a r esult of t he system (as oppose d to user error). | |
237 | 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 . | |
238 | Loss of fu nctionalit y resultin g in erron eous eligi bility/enr ollment de terminatio ns or comm unications not being sent. | |
239 | Severity L evel 2 - H igh | |
240 | 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. | |
241 | A major de fect in th e function ality that does not result in corruption of data. | |
242 | 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: | |
243 | 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 . | |
244 | Any defect that does not confo rm to Sect ion 508 st andards. | |
245 | Any defect that resu lts in ina ccurate or missing r equirement s. | |
246 | Any defect that resu lts in inv alid authe ntication or authent ication of an invali d end user . | |
247 | Severity L evel 3 - M edium | |
248 | 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. | |
249 | Minor func tionality is not wor king as in tended and a workaro und exists but is no t suitable for long term use | |
250 | The inabil ity of a v alid user to access the system consisten t with gra nted privi leges | |
251 | 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 | |
252 | Any defect producing cryptic, incorrect, or inappr opriate er ror messag es | |
253 | 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 | |
254 | 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. | |
255 | Severity L evel 4 - L ow | |
256 | 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. | |
257 | Minor loss of, or de fect in th e function ality wher e a long t erm use ex ists | |
258 | Low-level cosmetic i ssues. | |
259 | Priority C lassificat ions | |
260 | 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. | |
261 | Priority 1 - Resolve Immediate ly | |
262 | 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. | |
263 | Priority 2 - Give Hi gh Attenti on | |
264 | 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. | |
265 | Priority 3 - Normal Queue | |
266 | 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. | |
267 | Priority 4 - Low Pri ority | |
268 | 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. | |
269 | Optional T ables, Cha rts, and G raphs | |
270 | None. | |
271 | Document A pproval Si gnatures | |
272 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
273 | Program/Pr oject Mana ger | |
274 | Date | |
275 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
276 | Business S ponsor Rep resentativ e | |
277 | Date | |
278 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
279 | Test Lead | |
280 | Date | |
281 | Appendix A - Test Ex ecution Lo g | |
282 | The Test E xecution R ecords for PSO*7.0*4 52 and PSS *1.0*215 a re include d in the E PIP Patch PSO*7.0*45 2 and PSS* 1.0*215 Ma ster Test Plan. | |
283 | ||
284 | Appendix B – Defect Log | |
285 | Ten (10) d efects wer e found du ring testi ng of PSO* 7.0*452 an d PSS*1.0* 215. All d efects hav e been res olved. | |
286 | 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.0.6059 43N/AN/AHo st File Bu ild Error during Pat ch Install ationCriti calOne (1) defect wa s found du ring Funct ional Test ing of ver sion 1.0.N /AN/AN/AN/ AN/ANo def ects were found duri ng Unit Te sting of v ersion 2.0 .629031Hig h Cost Rx ReportDivi sionReport does not print if u ser enters a list/ra nge at the Division prompt.Hig h | |
287 | Two (2) de fects were found dur ing Functi onal Testi ng of vers ion 2.0.62 9034MailMa n Message | |
288 | N/AMailMan message i s not sent when Uppe r Bound Na rcotic or RX warning limit is reached.Hi ghN/AN/AN/ AN/AN/ANo defects we re found d uring Unit Testing o f version 3.0.739743 Mocha 2.1 Update for Shared Ro utine PSOE MO N/AN/AH ighOne (1) defect wa s found du ring Funct ional Test ing of ver sion 3.0.N /AN/AN/AN/ AN/ANo def ects were found duri ng Unit Te sting of v ersion 4.0 .N/AN/AN/A N/AN/ANo d efects wer e found du ring Compo nent Integ ration and System Te sting of v ersion 4.0 .N/AN/AN/A N/AN/ANo d efects wer e found du ring Regre ssion test ing of ver sion 4.0.7 39825Pharm acy Superv isors Mail Man GroupO rganizerEn d of Presc ribing Num bering War ning Messa ges not se nt | |
289 | Medium | |
290 | Two (2) de fects were found dur ing Functi onal Testi ng of vers ion 4.0.73 9832Print from Suspe nse FileEx clude Help Text for Non-Contro lled Refri gerated It ems and Su pplies and Controlle d Substanc es Refrige rated Item sAdded add itional He lp text fo r Exclude, Removed d ebug codeH ighN/AN/AN /AN/AN/ANo defects w ere found during Uni t Testing of version 5.0.75050 5MailMan M essageLimi tLimit fie ld is inco rrect in M ailMan mes sageHigh | |
291 | Two (2) de fects were found dur ing Functi onal Testi ng of vers ion 5.0.75 0515Print from Suspe nse | |
292 | N/ALabels are not pr inted afte r selectio n of categ ory and fi ltersCriti calN/AN/AN /AN/AN/ANo defects w ere found during Uni t Testing of version 6.0.N/AN/ AN/AN/AN/A No defects were foun d during R egression testing of version 6 .0.770156 | |
293 | End of RX Range -Mai lMan Messa geN/AInact ive Sites are includ ed in Mail Man messag e.MediumTw o (2) defe cts were f ound durin g Function al Testing of versio n 6. 0.770 162Print f rom Suspen se FileHel p Text | |
294 | Default va lueHelp te xt | |
295 | Default va lueMediumD uring the VA stakeho lder demo, changes w ere reques ted, resul ting in ve rsion 7.0. | |
296 | These chan ges relate d to help text verbi age update s and a de fault valu e for the Print from Suspense by Categor y prompt.N /AN/AN/AN/ AN/ANo def ects were found duri ng Unit Te sting of v ersion 7.0 .N/AN/AN/A N/AN/ANo d efects wer e found du ring Regre ssion test ing of ver sion 7.0.N /AN/AN/AN/ AN/ANo def ects were found duri ng Functio nal testin g of versi on 7.0._1 594094168. pdf |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.