69. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 11/8/2016 5:25:18 PM Eastern 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.

69.1 Files compared

#	Location	File	Last Modified
1	rxrefill-v2.0.0 P2.zip	Rx+Refill_MTP.docx	Fri Nov 4 21:49:01 2016 UTC
2	rxrefill-v2.0.0 P2.zip	Rx+Refill_MTP.docx	Sun Nov 6 22:53:43 2016 UTC

69.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	7	2404
Changed	6	12
Inserted	0	0
Removed	0	0

69.3 Comparison options

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

69.4 Active regular expressions

No regular expressions were active.

69.5 Comparison detail

	1	Rx Refill_ MTP
	2	Department of Vetera ns Affairs Mobile Ap plications (Apps) Ph ase Two (M AP2)Rx Ref ill - Pres cription R efill – Ma ster Test Plan April 2016Versi on 0.6
	3
	4	Introducti on
	5	Veterans H ealth Admi nistration (VHA), Pa tient Care Services (PCS), Pha rmacy Bene fits Manag ement (PBM ) is reque sting modi fication t o the exit ing Rx Ref ill – Pres cription R efill (Rx Refill) mo bile appli cation.The current H ypertext M ark-up Lan guage five (5) (HTML 5) version of the Rx Refill ap p., which is not in production due to co mpliance a nd 508 iss ues. The A pplication must firs t be updat ed to meet complianc e requirem ents and t hen have t he agreed upon enhan cements up dated to i nclude sel f-service Rx medicat ion tracki ng. The VA now sends the major ity of out patient Rx 's to Vete ran patien ts via mai l. In orde r to track the deliv ery of mai led Rx med ications, VA patient s must cal l their lo cal VAMC d irectly an d wait for a represe ntative to look up t heir order and conne ct them to the carri er respons ible for d elivering the shipme nt. The cu rrent Rx R efill mobi le applica tion shall be enhanc ed to allo w Veterans to track Rx medicat ion shipme nts to inc lude the s tatus of t heir maile d Rx medic ation and expected d elivery da te and tim e. The Rx Refill mob ile app sh all be mod ified to d isplay rel evant mail tracking informatio n, with li nks to sen d the user or displa y status i nformation from comm on deliver y services such as t he United States Pos tal Servic e (USPS), FedEx and United Par cel Servic e. The con tent displ ayed on th e enhanced Rx Refill app shall mirror th e informat ion in My HealtheVet (MHV), ma king use o f existing MHV servi ces, where appropria te.Additio nally, the existing Rx Refill applicatio n shall be enhanced to include a picture of the me dication i ncluding t he name of the medic ation. VA will provi de a web s ervice lin k to the M edication Image Libr ary (MIL) system in the VA Cor porate Dat a Warehous e (CDW).
	6	Test Plan Purpose
	7	The purpos e of this Master Tes t Plan (MT P) for the RX Refill applicati on is to d efine all testing th at must be performed on this m obile appl ications b efore the applicatio n can be d eemed read y for subm ission to the VA Com pliance Re view and V erificatio n and Vali dation (V& V) testing processes . An Agile testing a pproach wi ll be foll owed by th e MAP2 Hew lett Packa rd Enterpr ise (HPE) Test teams (i.e., De velopers a nd System Quality As surance (S QA) Tester s for the testing of the funct ionalities as define d in the v arious pro gram docum ents inclu ding the P erformance Work Stat ement (PWS ) for the Mobile App lications (Apps) Pha se Two (MA P2), requi rements do cumentatio n, and sys tem design specifica tions. Thi s MTP is d esigned to ensure th at the obj ectives of testing a re success fully met. It serves as a guid eline for MAP2 test developmen t and test execution . Where ap plicable, this test plan will reference other exis ting progr am documen tation. Th e purpose of referen cing exist ing docume ntation is to minimi ze informa tion redun dancy and also to mi nimize the associate d maintena nce effort s required to keep m ultiple do cuments sy nchronized . Supporti ng documen tation for the Rx Re fill appli cation can be found on the Rx Refill App wiki page (https:// DNS /display/R XR/P2+Docu mentation) . Table 1 provides a list of p rogram doc umentation reference d within t his test p lan.
	8	Table 1: R eference D ocuments
	9	Document
	10	Author
	11	Status
	12	Version
	13	MAP2 – Per formance W ork Statem ent – TAC- 14-16925
	14	VHA
	15	Client App roved
	16	1.0
	17	MAP2 – Pro gram Maste r Test Pla n
	18	Ephraim Bl evins
	19	Baseline
	20	1.0
	21	MAP2 – Con tract Proj ect Manage ment Plan
	22	Eddie Urso
	23	Baseline
	24	1.0
	25	Rx Refill MAP2 Maste r Schedule
	26	Sandi Wint ers, Debra Wolf
	27	Baseline
	28	TBD
	29	MAP2 Issue s and Risk Logs/DAIR
	30	Eddie Urso , Dave Get man
	31	Work in Pr ogress
	32	TBD
	33	Rx Refill_ BRD
	34	David Getm an
	35	Work in Pr ogress
	36	1.0 2/17/2 015
	37	Rx Refill_ RTM
	38	Megan Luca s
	39	Work in Pr ogress
	40	V6
	41	Rx Refill_ User Stori es – Sprin t Planning
	42	Laurie Kir by, Megan Lucas
	43	Work in Pr ogress
	44	TBD
	45	RxRefill_W ireframes_ Mobile
	46	Laurie Kir by, Christ ine Durose
	47	Work in Pr ogress
	48	V6
	49	RxRefill_W ireframes_ Tablet
	50	Laurie Kir by, Christ ine Durose
	51	Work in Pr ogress
	52	V6
	53	Rx Refill (RXR) SDD Addendum
	54	Aaron Luca s
	55	Work in Pr ogress
	56	2.0
	57	Rx Refill_ RSD Addend um
	58	Megan Luca s
	59	Work in Pr ogress
	60	V6
	61	Rx Refill (RXR) Serv ice Interf ace Contro l Document (ICD)
	62	Aaron Luca s
	63	Work in Pr ogress
	64	2.16
	65	This Test Plan also supports t he followi ng specifi c objectiv es:
	66	Identifies the items that shou ld be targ eted by th e tests
	67	Identifies the motiv ation for, and ideas behind, t he test ar eas to be covered
	68	Outlines t he testing approache s that wil l be used
	69	Identifies the requi red resour ces and pr ovides an estimate o f the test efforts
	70	Describes the testin g environm ent
	71	Lists the deliverabl e elements of the te st project
	72	Test Objec tives
	73	This Maste r Test Pla n supports the follo wing objec tives:
	74	To provide test cove rage for 1 00% of the documente d requirem ents – fun ctional an d non-func tional con tained in applicable applicati on require ment docum entation f unctional contained in applica ble requir ement docu mentation (i.e., the Business Requiremen ts Documen ts (BRD), the Requir ement Spec ifications Document (RSD), and User Stor ies)
	75	To validat e the Acce ptance Cri teria of e ach User S tory for t he Rx Refi ll applica tion has b een met
	76	Provide co verage for System De sign Docum ent (SDD) addendum e lements
	77	To execute 100% of t he test ca ses during all testi ng levels
	78	To perform handoffs with V&V, business s ponsors, a nd Complia nce bodies for indep endent tes ting, comp liance rev iews, and User Funct ionality t esting
	79	To create, maintain, and contr ol the tes t environm ent
	80	Acronyms
	81	This secti on contain s a list o f acronyms used in t his docume nt.
	82	Acronym
	83	Descriptio n
	84	ADM
	85	Agile Deve lopment Me thodology
	86	ADR
	87	Administra tive Data Repository
	88	BRD
	89	Business R equirement s Document
	90	CCB
	91	Change Con trol Board
	92	CDW
	93	Corporate Data Wareh ouse
	94	COR
	95	Contractin g Officer' s Represen tative
	96	EAS
	97	Enterprise Applicati on Securit y
	98	EHR
	99	Electronic Health Re cord
	100	ESE
	101	Enterprise Systems E ngineering
	102	HPE
	103	Hewlett Pa ckard Ente rprise
	104	IAM
	105	Identity a nd Access Management
	106	ID
	107	Identifica tion
	108	IOC
	109	Initial Op erating Ca pability
	110	MA
	111	Mobile App lication
	112	MADW
	113	Mobile App lication D evelopment Workflows
	114	MAE
	115	Mobile App lication E nvironment
	116	MDWS
	117	Medical Do main Web S ervices
	118	MHV
	119	My Healthe Vet
	120	MIL
	121	Medication Image Lib rary
	122	MTP
	123	Master Tes t Plan
	124	MVI
	125	Master Vet eran Index
	126	NFR
	127	Non-Functi onal Requi rement
	128	NIST
	129	National I nstitute o f Standard s and Tech nology
	130	NSOC
	131	Network Se curity Ope rations Ce nter
	132	OIA
	133	Office of Informatio n Assuranc e or Offic e of Infor matics and Analytics
	134	OI&T
	135	Office of Informatio n and Tech nology
	136	O&M
	137	Operations and Maint enance
	138	Rx Refill
	139	Rx Refill Delivery T racking an d Image En hancements
	140	PHI
	141	Private He alth Infor mation
	142	PII
	143	Personally Identifia ble Inform ation
	144	PMAS
	145	Project Ma nagement a nd Account ability Sy stem
	146	RSD
	147	Requiremen ts Specifi cation Doc ument
	148	RTM
	149	Requiremen ts Traceab ility Matr ix
	150	SDD
	151	System Des ign Docume nt
	152	SQA
	153	Software Q uality Ass urance
	154	SSP
	155	System Sec urity Plan
	156	UFT
	157	User Funct ionality T est
	158	URL
	159	Uniform Re source Loc ator
	160	VA
	161	Department of Vetera ns Affairs
	162	VAHA
	163	VA Health Adapter
	164	VAMC
	165	VA Medical Center
	166	VAMF
	167	VA Mobile Framework
	168	VDD
	169	Version De scription Document
	170	VHA
	171	Veterans H ealth Admi nistration
	172	VistA
	173	Veterans H ealth Info rmation Sy stems and Technology Architect ure
	174	VP
	175	Verificati on Point
	176	V&V
	177	Verificati on and Val idation
	178	WMS
	179	Web and Mo bile Solut ions
	180	WASAs
	181	Web Applic ation Secu rity Asses sments
	182	Roles and Responsibi lities
	183	Table 2 li sts the ke y roles an d their re sponsibili ties for t his Master Test Plan . The role s defined below are members of the MAP2 HPE Progra m team.
	184	Table 2: R oles and D escription s
	185	Role
	186	Descriptio n
	187	Developers
	188	Persons th at build o r construc t the prod uct/produc t componen t and comp lete the r equired te sting.
	189	Developmen t Manager
	190	Person res ponsible f or ensurin g mobile a pplication component s have gon e through adequate u nit and co mponent-in tegration testing by developme nt team be fore turni ng over to the Syste m Quality Assurance (SQA) Test Team for system tes ting. Resp onsible fo r approvin g the MTP.
	191	Project Ma nager
	192	Person res ponsible f or oversee ing the de velopment and testin g of mobil e applicat ions under the MAP2 program. R esponsible for appro ving the M TP.
	193	Program Ma nager
	194	Person tha t has over all respon sibility f or the suc cessful pl anning and execution of the MA P2 program . The Prog ram Manage r will be responsibl e for appr oving the MTP.
	195	Stakeholde rs
	196	Persons th at hold a stake in a situation in which they may a ffect or b e affected by the ou tcome.
	197	SQA Test P lanner/Eng ineer
	198	An experie nced test analyst or member of the Test Team that leads and coordinate s activiti es (i.e., ensure tes t environm ent setup, support I nitial Ope rating Cap ability (I OC) and V& V testing activities , etc.) re lated to a ll aspects of testin g for an i ndividual mobile app lication. Responsibl e for deve loping a M TP for eac h applicat ion.
	199	SQA Test M anager
	200	Person tha t has over all respon sibility f or creatio n and impl ementation of the pr ogram-leve l MTP. Per son respon sible for leading an d coordina ting activ ities rela ted to all aspects o f testing based on a n approved applicati on-level M TPs and sc hedules.
	201	SQA Test T eam
	202	Persons th at execute tests and ensure th e test env ironment w ill adequa tely suppo rt planned test acti vities.
	203	Test Envir onment Tea m
	204	Persons th at establi sh, mainta in, and co ntrol test environme nts.
	205	Processes and Refere nces
	206	The proces ses that g uide the i mplementat ion of thi s Master T est Plan a re:
	207	VA's Mobil e Applicat ion Develo pment Life Cycle
	208	VA's Mobil e Applicat ion Projec t Manageme nt Account ability Sy stem
	209	MADW-3 App lication D evelopment document
	210	MADW-4 Ver ification and Valida tion
	211	MADW-5 Com pliance Re view
	212	MADW-6 Use r Acceptan ce Test
	213	MADW-7 Fie ld Test (I OC)
	214	The refere nces that support th e implemen tation of this Maste r Test Pla n are:
	215	Mobile Dev elopment A pplication Life Cycl e (http:// DNS /content/d eveloping- va-apps)
	216	ProPath
	217	(http:// DNS /process/p ropath)
	218	Section 50 8 Office W eb Page
	219	(http:// DNS /508workgr oup)
	220	Privacy Im pact Asses sment - Pr ivacy Serv ice
	221	(http:// DNS /Privacy_I mpact_Asse ssment.asp ) Note: Fo r 508 Comp liance, co py and pas te the abo ve URLs in to your br owser to r each each site. Also , the abov e hyperlin ks/URLs pr efaced wit h DNS are only accessible with acce ss to VA n etwork.
	222	Items to B e Tested
	223	During des ign of the Rx Refill mobile ap plication, the MAP2 HPE Develo pment and SQA Test t eams will define the changes r equired to deploy an d test the Rx Refill applicati on into th e Mobile A pplication Environme nt (MAE). After rece ipt of the SDD Adden dum and/or the Inter face Contr ol Documen t (ICD) fo r the Rx R efill appl ication, t he MAP2 HP E SQA Test team will determine the kind of integra tion testi ng that ne eds to occ ur for the Rx Refill applicati on in addi tion to th e other sy stem testi ng to occu r on this applicatio n.
	224	Overview o f Test Exc lusions
	225	Note: Addi tional inf ormation f or the Ove rview of T est Exclus ions secti on will be added/upd ated in fu ture itera tions, as needed.The following component s and feat ures and c ombination s of compo nents and features w ill not be tested:
	226	Non-functi onal requi rements th at are not applicabl e to the R x Refill a pplication developed by the MA P2 HPE Dev elopment t eam
	227	Testing on Android m obile devi ces (i.e. phone, tab let, etc.)
	228
	229	Epic/Story #
	230	JIRA Story #
	231	Epic/Story Requireme nt
	232	RXR-528
	233	RXR-538
	234	As a Rx Re fill team member, I want to cr eate the s ingle page applicati on templat e so that the RXR ap plication has a defi ned struct ure.
	235	RXR-534
	236	RXR-556
	237	As a Rx Re fill devel oper, I wa nt to crea te the pro ject struc ture and s hell along with buil d scripts for the VA MF Rx Refi ll Service so that a web servi ce project can be in itiated to provide R x Refill a nd Trackin g informat ion for th e Rx Refil l applicat ion.
	238	RXR-534
	239	RXR-557
	240	As a Rx Re fill devel oper, I wa nt to crea te an acti ve prescri ptions end point with in the VAM F Rx Refil l Service so that ac tive presc riptions f rom the En terprise T racking an d Refill s ervice can be provid ed to the Rx Refill Applicatio n.
	241	RXR-534
	242	RXR-558
	243	As a Rx Re fill devel oper, I wa nt to crea te a histo rical pres criptions endpoint w ithin the VAMF Rx Re fill Servi ce so that historica l prescrip tions from the Enter prise Trac king and R efill serv ice can be provided to the Rx Refill App lication.
	244	RXR-534
	245	RXR-559
	246	As a Rx Re fill devel oper, I wa nt to crea te a presc ription re fill endpo int within the VAMF Rx Refill Service so that a pr escription refill re quest can be submitt ed to the Enterprise Tracking and Refill service v ia the Rx Refill App lication.
	247	RXR-534
	248	RXR-560
	249	As a Rx Re fill devel oper, I wa nt to crea te a track able presc riptions e ndpoint wi thin the V AMF Rx Ref ill Servic e so that trackable prescripti ons from t he Enterpr ise Tracki ng and Ref ill servic e can be p rovided to the Rx Re fill Appli cation.
	250	RXR-534
	251	RXR-561
	252	As a Rx Re fill devel oper, I wa nt to crea te a track able presc ription de tail endpo int within the VAMF Rx Refill Service so that deta iled track ing inform ation on a prescript ion from t he Enterpr ise Tracki ng and Ref ill servic e can be p rovided to the Rx Re fill App.
	253	RXR-534
	254	RXR-562
	255	As a Rx Re fill devel oper, I wa nt to crea te a medic ation refi ll request endpoint within the VAMF Rx R efill Serv ice so tha t details on prescri ptions tha t have bee n successf ully refil led by the VAMF Rx R efill app.
	256	RXR-535
	257	RXR-564
	258	As a Rx Re fill devel oper, I wa nt to crea te a medic ation imag e metadata endpoint within the VAMF MIL Service so that medi cation ima ge metadat a from the CDW MIL d atabase ca n be provi de to VAMF applicati ons.
	259	RXR-535
	260	RXR-565
	261	As a Rx Re fill devel oper, I wa nt to crea te a MIL i mage endpo int within the VAMF MIL Servic e so that medication image fro m the CDW MIL databa se can be provide to VAMF appl ications.
	262	RXR-535
	263	RXR-566
	264	As a Rx Re fill devel oper, I wa nt to crea te a MIL i mages endp oint withi n the VAMF MIL Servi ce so that a list of medicatio n images f rom the CD W MIL data base can b e provide to VAMF ap plications .
	265	RXR-535
	266	RXR-567
	267	As a Rx Re fill devel oper, I wa nt to crea te a MIL i mages endp oint withi n the VAMF MIL Servi ce so that a list of medicatio n images f rom the CD W MIL data base can b e provide to VAMF ap plications .
	268	RXR-535
	269	RXR-563
	270	As a Rx Re fill devel oper, I wa nt to crea te the pro ject struc ture and s hell along with buil d scripts for the VA MF MIL Ser vice so th at a web s ervice pro ject can b e initiate d to provi de medicat ion images from the MIL for VA MF applica tions.
	271	RXR-534
	272	RXR-973
	273	As a Rx Re fill devel oper, I wa nt to deve lop a mech anism to l ookup a Ve teran's mh vCorrelati onId, so t hat I can implement business l ogic withi n the RXR Session en dpoint.
	274	RXR-534
	275	RXR-974
	276	As a Rx Re fill devel oper, I wa nt to impl ement oAut h security for all n on-public webservice endpoints , so that endpoints are protec ted.
	277	RXR-1010
	278	RXR-1012
	279	As an RxR Developer, I need to incorpora te the use r friendly error des cription t hat were p rovided by the Busin ess Owner into the e xception h andling of each webs ervice end point, so that user friendly e rror messa ges can be provided to a calli ng applica tion.
	280	RXR-529
	281	RXR-1017
	282	As a Rx Re fill devel oper, I wa nt to crea te a refil lable pres cription e ndpoint wi thin the V AMF RxRefi ll Service , so that only refil lable pres criptions can be pro vided to t he RxRefil l applicat ion.
	283	RXR-1010
	284	RXR-1009
	285	As an Rx R efill Busi ness Owner , I need t o provide user frien dly error descriptio ns, so tha t Veterans have mean ingful err or descrip tions to a llow them to resolve any poten tial error s.
	286	RXR-1010
	287	RXR-1013
	288	As an Rx R efill deve loper, I n eed to inc orporate t he user fr iendly err or descrip tion that were provi ded by the Business Owner into the excep tion handl ing of eac h webservi ce endpoin t, so that user frie ndly error messages can be pro vided to a calling a pplication .
	289	RXR-1133
	290	RXR-1130
	291	As a RXR d eveloper, I would li ke to upda te/verify that the l ogin funct ionality i s consiste nt with ot her MAP2 a pps and to integrate it with R OA, so tha t a common workflow for login is achieve d.
	292	RXR-1206
	293	RXR-1188
	294	As an RxR developer, I would l ike to upg rade Handl ebars from version 1 .0.12 to v ersion 2.0 .0, so tha t the envi ronment is running o n the most up to dat e TRM appr oved versi on.
	295	RXR-1206
	296	RXR-1189
	297	As an RxR developer, I would l ike to upg rade Jasmi ne from ve rsion 2.1 to version 2.3, so t hat the en vironment is running on the mo st up to d ate TRM ap proved ver sion.
	298	RXR-1206
	299	RXR-1190
	300	As an RxR developer, I would l ike to upg rade SASS, so that t he environ ment is ru nning on t he most up to date T RM approve d version.
	301	RXR-1206
	302	RXR-1191
	303	As an RxR developer, I would l ike to upg rade the R XR Resourc e service to align J ersey libr aries with those run ning in th e Health A dapter, so that the libraries running be have as ex pected wit hout libra ry collisi ons.
	304	RXR-1206
	305	RXR-1193
	306	As an RxR developer I would li ke to upgr ade the MI L Resource service t o align Je rsey libra ries with those runn ing in the Health Ad apter, so that the l ibraries r unning beh ave as exp ected with out librar y collisio ns.
	307	RXR-1235
	308	RXR-1236
	309	As an RXR (MT) Devel oper, I ne ed to inco rporate th e oAuth Li b Spring M VC Control ler into m y applicat ion so tha t the Fron t End can query MT f or oAuth c lient deta ils and ca n request MT to brok er calls f or obtaini ng oauth t okens give n the oAut h code.
	310	RXR-1235
	311	RXR-1237
	312	As a UI De veloper, I want to u tilize the Auth Func tions wrap per to ini tialize th e applicat ion, so th at user ca n see if t hey are au thenticate d properly .
	313
	314	Overview o f Test Inc lusions
	315	Note: Addi tional inf ormation f or the Ove rview of T est Inclus ions secti on will be added/upd ated in fu ture itera tions, as needed.The following component s, feature s, and com binations of compone nts and fe atures wil l be teste d:
	316	Mobile Web site (HTM L5)
	317	Testing on IOS mobil e devices, e.g., GFE iPad usin g Safari w eb browser .
	318	Testing on Windows l aptop usin g IE-11, C hrome, Fir efox, web browsers.
	319	For phone view only, emulators are used as no GFE device is available.
	320
	321	Epic/Story #
	322	JIRA Story #
	323	Epic/Story Requireme nt
	324	RXR-528
	325
	326	Web Applic ation Temp late
	327	RXR-528
	328	RXR-539
	329	As a Rx Re fill team member, I want to cr eate the f ooter area of the si ngle page applicatio n so that the RXR ap plication displays g eneral inf ormation a bout the a pplication and the u ser.
	330	RXR-528
	331	RXR-690
	332	As a Rx Re fill team member, I want to cr eate the h ome/landin g page for the RXR a pplication so that t he user ha s quick ac cess to th e major el ements pro vided by t he applica tion.
	333	RXR-528
	334	RXR-691
	335	As a Rx Re fill team member, I want to cr eate a qui ck access navigation element i n the bann er of the RXR applic ation so t hat the us er has qui ck access to the maj or element s provided by the ap plication.
	336	RXR-528
	337	RXR-692
	338	As a Rx Re fill team member, I want to cr eate a hel p page so that the u ser is pro vided with help info rmation re lating to the applic ation by t he applica tion.
	339	RXR-528
	340	RXR-693
	341	As a Rx Re fill team member, I want to cr eate an ab out page s o that the user is p rovided wi th help in formation relating t o the appl ication by the appli cation.
	342	RXR-528
	343	RXR-694
	344	As a Rx Re fill team member, I want to in tegrate wi th the VAM F authoriz ation mech anism for login so t hat the us er can be authentica ted prior to enterin g the appl ication.
	345	RXR-528
	346	RXR-696
	347	As a Rx Re fill proje ct team, w e must ens ure that f ollowing 1 5 minutes of inactiv ity by the current u ser our ap plication time-outs so that ou r applicat ion effici ently used the limit ed resourc es that ma ybe availa ble to the user.
	348	RXR-529
	349
	350	Refillable VA Medica tions
	351	RXR-529
	352	RXR-697
	353	As a Veter an, I want to see my active/re fillable V A prescrip tions, so that I can view deta iled infor mation on a prescrip tion and r efill it w hen approp riate.
	354	RXR-529
	355	RXR-698
	356	As a Veter an, I want to sort m y active/r efillable VA prescri ptions, so that I ca n view det ailed info rmation on a prescri ption and refill it when appro priate.
	357	RXR-529
	358	RXR-699
	359	As a Veter an, I want to see me dication d etail on m y active/r efillable VA prescri ptions, so that I ca n easily v iew detail ed informa tion on a prescripti on.
	360	RXR-529
	361	RXR-700
	362	As a Veter an, I want to reques t a refill on my act ive/refill able VA pr escription s, so that I can ref ill my VA medication s.
	363	RXR-530
	364
	365	Track Deli very
	366	RXR-530
	367	RXR-545
	368	As a Veter an I want the abilit y to see a list of m y VA presc riptions t hat have b een shippe d so I can determine when I wi ll receive my VA med ication by mail.
	369	RXR-530
	370	RXR-546
	371	As a Veter an, I want to sort m y trackabl e prescrip tions, so that I can ultimatel y view det ailed info rmation on tracking and shipme nt.
	372	RXR-530
	373	RXR-547
	374	As a Veter an, I want the optio n to see a n importan t informat ion screen when I se lect track ing delive ry details so that I can be in formed on tracking d etail info rmation.
	375	RXR-530
	376	RXR-548
	377	As a Veter an, I want to see de tail track ing inform ation for my trackab le prescri ptions, so that I tr ack and de termine wh ere my med ication is .
	378	RXR-530
	379	RXR-549
	380	As a Veter an, I want to see an image of my medicat ion for tr ackable pr escription s, so that I can com pare what was shippe d to what I received
	381	RXR-530
	382	RXR-550
	383	As a Veter an, I want to track my prescri ption, so that I can determine where it is.
	384	RXR-531
	385
	386	Prescripti on History
	387	RXR-531
	388	RXR-551
	389	As a Veter an, I want to see my VA prescr iptions, s o that I c an view de tailed inf ormation o n a prescr iption
	390	RXR-531
	391	RXR-552
	392	As a Veter an, I want to sort m y VA presc riptions o n the pres cription h istory scr een, so th at I can v iew detail ed informa tion on a prescripti on
	393	RXR-531
	394	RXR-553
	395	As a Veter an, I want to see me dication d etail on a prescript ion select ed from th e prescrip tion histo ry screen, so that I can easil y view det ailed info rmation on a prescri ption.
	396	RXR-532
	397
	398	Medication Image
	399	RXR-532
	400	RXR-554
	401	As a Rx Re fill team member, I want to cr eate a mec hanism for resizing MIL images , so that the images can be us ed on a mo bile platf orm.
	402	RXR-533
	403
	404	Disclaimer
	405	RXR-533
	406	RXR-555
	407	As a Rx Re fill team member, I want to pr ovide a di sclaimer f or the Vet eran, so t hat the ap plication informs th e user to take medic ation as p rescribed.
	408	RXR-536
	409
	410	Medication List on M yHealtheVe t
	411	RXR-536
	412	RXR-568
	413	As a Veter an using t he RxRefil l applicat ion, I nee d access t o the My C omplete Me dication L ist via a link to MH V, so that I can vie w all my m edications .
	414	RXR-536
	415	RXR-569
	416	As a Veter an using t he RxRefil l applicat ion, I nee d access t o my Blue Button Dow nload via a link to MHV, so th at I acces s my Blue Button dat a.
	417	RXR-536
	418	RXR-570
	419	As a Veter an using t he RxRefil l applicat ion, I nee d access t o my Healt h Summary (VA CCD) v ia a link to MHV, so that I ca n view all my CCD da ta.
	420	RXR-537
	421
	422	Icebox
	423	RXR-537
	424	RXR-571
	425	As a Veter an, I want a way to track deli very of a refill for my prescr iption dir ectly from the refil l details.
	426	RXR-537
	427	RXR-572
	428	As a Veter an, I want the abili ty to call my pharma cy/provide r so that I can talk to them d irectly if I have qu estions re garding my prescript ion.
	429	RXR-537
	430	RXR-573
	431	As a Veter an, I want the abili ty to send a secure message to my pharma cist or pr ovider so I can talk to them d irectly if I have qu estions re garding my prescript ion.
	432	RXR-537
	433	RXR-574
	434	As a Veter an, I need access to an authen ticated us er's COMPL ETE medica tion list as defined by the Es sential Me d Directiv e (EMD).
	435	RXR-537
	436	RXR-575
	437	As a Veter an, I want to be abl e to under stand the meaning of a term or status an d how it r elates to similar Rx Refill in terfaces s uch as MHV Rx Refill and Audio care.
	438	RXR-537
	439	RXR-576
	440	As a Veter an, I want to be abl e to repla ce the MIL image wit h a pictur e of my VA Pharmacy/ CMOP dispe nsed medic ation.
	441	RXR-537
	442	RXR-577
	443	As a Veter an, I want to be pro mpted to n otify my V A Pharmacy /provider of any dis crepancies I have fo und regard ing the me dication i mages.
	444	RXR-537
	445	RXR-578
	446	As a Veter an, I want a warning of a chro nic medica tion presc ription th at is abou t to expir e so that that the V eteran can take acti on before the medica tion runs out.
	447	RXR-537
	448	RXR-579
	449	As a Veter an, I want to be abl e to submi t a refill request b y using my mobile de vice to sc an a presc ription la bel bar co de.
	450	RXR-537
	451	RXR-580
	452	As a Veter an, I want the abili ty to get an automat ed Renewal request f or non-ref illable pr escription s similar to Audio C are.
	453	RXR-537
	454	RXR-581
	455	As a Veter an, I want a refill reminder s ent to my mobile dev ice or ema il account .
	456	RXR-537
	457	RXR-582
	458	As a Veter an, I want to be ale rted on my mobile de vice when a medicati ons is abo ut to be s ent so tha t (if need ed) I have plenty of time to s top a refi ll from be ing sent ( i.e. alert me 10 day s prior to the next fill date.
	459	RXR-537
	460	RXR-583
	461	As a Veter an, I want a pill re minder to remind me when I nee d to take my pill ba sed on the frequency I enter O R the freq uency cont ained in m y VA presc ription.
	462	RXR-537
	463	RXR-584
	464	As a Veter an, I want the abili ty to util ize a "Fac ility Loca tor" to fi nd my pref erred VA H ealthcare facility o r faciliti es closest to my mob ile device .
	465	RXR-537
	466	RXR-585
	467	As a Veter an, I want links to future/exi sting educ ation on m edication informatio n.
	468	RXR-537
	469	RXR-586
	470	As a Veter an, I want Drug Info rmation lo okup speci fic to the prescribe d medicati on using t he VA Heal th Library and the V A National Formulary .
	471	RXR-537
	472	RXR-587
	473	Additional requireme nts as req uested by HFE contai ned within "Dec2014_ Interviews _Rx Refill _ABIntervi ews_Report " and agre ed upon by the BO, P BM:
	474	RXR-1010
	475	RXR-1014
	476	As a Veter an, I want to see us er friendl y error me ssages whe n an error occurs, s o that I u nderstand how to cor rect the e rror or be provided with a mec hanism for assistanc e.
	477	RXR-529
	478	RXR-1018
	479	As a Veter an, I want to see on ly refilla ble prescr iptions in the Refil lable VA M edications screen, s o that I c an quickly review an d refill m y refillab le medicat ions.
	480	RXR-1134
	481	RXR-1107
	482	As a Veter an, I want to approv e the rele ase of my health inf ormation, so that I may be gra nted acces s to my in formation via the RX R mobile a pplication .
	483	RXR-530
	484	RXR-1015
	485	As a Veter an, I want to see "I mage not a vailable" when an im age for me dication i s selected and is no t availabl e for trac kable medi cation, so that I se e an image is not av ailable in clear, re adable lan guage.
	486	RXR-530
	487	RXR-1016
	488	As a Veter an, I want to see an image dis claimer be fore viewi ng the sel ected medi cation for trackable medicatio n, so that I am awar e the imag e is for i dentificat ion purpos es only.
	489	RXR-1133
	490	RXR-1131
	491	As a Veter an, I want the appli cation to integrate with the V AMF author ization me chanism fo r logout s o that the user can see they a re logged out of the applicati on.
	492	RXR-1235
	493	RXR-1238
	494	As a SQA T ester, I n eed to reg ression te st the use of Token validation services with Autho rization S ervices 4. 4 to ensur e that the service p rotection continues to work
	495	RXR-1235
	496	RXR-1239
	497	As a SQA T ester, I n eed to ens ure that t he Inactiv ity timeou t function ality cont inues to f unction as before wi th Authori zation Ser vices 4.4, so that I can verif y the upgr ade did no t impact t imeout.
	498	RXR-1235
	499	RXR-1240
	500	As a SQA T ester, I n eed to ens ure that t he Logout functions continue t o perform as before with Autho rization S ervices 4. 4, so that I can ver ify that I can logou t of the s ystem.
	501	For a list of non-fu nctional r equirement s to be te sted, refe r to the R x Refill R SD addendu m document located o n the VA R x Refill A pp wiki pa ge: (_Toc4 02796789" class="ext ernal-link " rel="nof ollow"> DNS /display/R XR/PWS+Del iverables) .
	502	Testing Ap proach
	503	Note: Addi tional inf ormation f or the Tes t Approach section w ill be add ed/updated in future iteration s, as need ed.The MAP 2 Program team will be utilizi ng an Agil e Developm ent Method ology (ADM ) as well as using b est practi ces in agi le testing technique s for all applicatio ns develop ed as part of the MA P2 program . Develope rs assigne d to a Scr um team wi ll perform product c omponent o r unit tes ting on th eir local developmen t workstat ion and co mponent-in tegration testing fo r each Spr int iterat ion using the MAE De velopment environmen t, next th e MAP2 HPE SQA teste r assigned to the Sc rum team w ill perfor m feature (aka funct ional) ver ification testing us ing the MA E Developm ent enviro nment, whi ch involve s testing against th e user sto ry's accep tance crit eria. In a ddition, a parallel process of regressio n testing will occur throughou t the Spri nt iterati on. This i nvolves re -running t he automat ed and/or manual pro duct-compo nent tests and featu re verific ation test s from the current S print iter ation and previous i terations via a cont inuous int egration f ramework. This level of testin g will be completed in the MAE Developme nt environ ment. Duri ng the app lication d evelopment stage, th e MAP2 HPE Developme nt team wi ll perform a static code analy sis on the Rx Refill applicati on using t he HPE For tify tool. Any issue s found wi ll be reme diated. MA P2 HPE SQA Test team members w ill be eng aged in th is process to review static an alysis out put result s as well as verifyi ng the cod e has been remediate d. Members of the MA P2 HPE SQA Test team will perf orm the Sy stem Test level, whi ch starts once the f irst user story is r eady for t his test l evel. Syst em testing will cons ist of exe cuting fun ctional, e nd-to-end, system-in tegration, full regr ession, pe rformance, etc. usin g the MAE Developmen t-Test env ironment. System tes ting will begin at t he start o f Sprint 2 , but no l ater than Sprint 4. The timing of the Sy stem Test level, inc luding wha t test typ es will be performed , will be addressed in Section 2.2 of th is documen t in conju nction wit h the appl icable Spr int planni ng meeting where the System Te st level i s expected to begin. After com pletion of system te sting, the final bui ld will be submitted for VA Co mpliance R eviews and V&V Test processes.
	504	Testing Pr ocesses
	505	The follow ing testin g processe s will be employed b y the MAP2 HPE SQA T est team:
	506	Develop th e Master T est Plan ( this docum ent)
	507	Establish the Test E nvironment s
	508	MAE Develo pment
	509	MAE Develo pment-Test
	510	Prepare Te st Scenari os, Cases, Scripts a nd Data
	511	Conduct th e Tests
	512	Verify Tes t Results
	513	Document T est Result s
	514	Update the Test Stat us
	515	Identify a nd Resolve Discrepan cies
	516	Retest rem ediated de fects
	517	Representa tives of t he user ba se perform user acce ptance tes ting and i ndependent teams per form verif ication an d validati on testing and compl iance body reviews. While the strategy i s standard to best p ractices i n testing, there are some uniq ue aspects to the mo bile and M AP2 test a pproach.
	518	The MAP2 p rogram wil l be follo wing an Ag ile Develo pment Meth odology (A DM), which integrate s testing into the e ntire deve lopment pr ocess vers us a separ ate test p hase at th e end of t he develop ment cycle as well a s promotes constant communicat ion with t he busines s owner's team. This yields ap plication software t hat implem ents the i ntended re quirements and will not yield many requi rements su rprises in the downs tream test ing levels .
	519	The ADM fo llowed by the MAP2 p rogram tea m promotes the follo wing Agile test-rela ted strate gies:
	520	MAP2 HPE S QA tester involvemen t in user story refi nement and specifica tion of ac ceptance c riteria as part of s tory defin ition
	521	Automate p roduct com ponent, co mponent-in tegration, system an d acceptan ce testing as much a s possible
	522	Incorporat ion of aut omated tes ts into th e continuo us build e nvironment
	523	Small (min imal) hand -offs betw een Scrum team (deve lopers, bu siness ana lyst, test ers) membe rs (they w ork togeth er)
	524	Lightweigh t (fast-tu rnaround) defect tra cking and management (defects are identi fied and f ixed withi n the Spri nt)
	525	Explorator y testing
	526	Test in th e same Spr int in whi ch the fea ture is de veloped
	527	Track test coverage
	528	Incorporat ion of tes ting into the "Defin ition of D one"
	529	Considerat ion of how various f acets of t esting wil l be perfo rmed durin g the Rele ase Cycle (e.g., str onger emph asis on pe rformance testing du ring 'hard ening Spri nt iterati ons')
	530	Separate B lack-box ( behavioral ) unit tes ting from white-box (code-stru cture base d) unit te sting.
	531	Product co mponent or unit test ing is typ ically the responsib ility of d evelopers. However, for agile projects, it is reco mmended th at the res ponsibilit y for whit e-box test ing be ass igned to d evelopers, while the testers c an focus o n black-bo x (feature -driven) u nit testin g concurre ntly. This provides complement ary but co mprehensiv e focus to unit test ing while also enabl ing early detection of defects that woul d typicall y be found in later test level s (e.g., s ystem test ing) and r educes cyc le time fo r defect f ixes and r ework.
	532	Integrate Automated Tests with the Conti nuous Inte gration Bu ild Enviro nment
	533	Automated tests will run again st the con tinuous bu ild enviro nment
	534	The compli ance revie ws that mu st be perf ormed on a mobile ap plication are define d based on the level of risk t o VA. The Rx Refill applicatio n has been assessed as a categ ory 4 appl ication. T he risk le vel is def ined as on e of the f our levels shown in Table 3. T he complia nce bodies that must review th ose applic ations are also show n.
	535	Table 3: R isk Level Definition
	536	Mobile App lication C lassificat ion
	537	1a - Very Low: Non- OI&T**
	538	1 - Very L ow
	539	2 - Low
	540	3 - Medium
	541	4 - High
	542	Compliance Review Bo dy
	543	Does not u tilize VA resource o r OI&T Fun ding
	544	Does not u tilize VA resources
	545	Read only access to VA resourc es
	546	Write acce ss to VA o r external resources
	547	Read and/o r write ac cess to VA or extern al sensiti ve resourc es
	548	V&V
	549	Required
	550	Required
	551	Required
	552	Required
	553	Required
	554	Business O wner Accep tance
	555	Required
	556	Required
	557	Required
	558	Required
	559	Required
	560	Patient Sa fety Asses sment (OIA )
	561	Required
	562	Required
	563	Required
	564	Required
	565	Required
	566	508 Access ibility (O I&T)*
	567	Required
	568	Required
	569	Required
	570	Required
	571	Required
	572	Code Revie w
	573	Required
	574	Required
	575	Required
	576	Required
	577	Required
	578	Usability Testing (O IA)
	579	Required
	580	Required
	581	Required
	582	Required
	583	Required
	584	Mobile App lication C lassificat ion
	585	1a - Very Low: Non- OI&T**
	586	1 - Very L ow
	587	2 - Low
	588	3 - Medium
	589	4 - High
	590	Compliance Review Bo dy
	591	Does not u tilize VA resource o r OI&T Fun ding
	592	Does not u tilize VA resources
	593	Read only access to VA resourc es
	594	Write acce ss to VA o r external resources
	595	Read and/o r write ac cess to VA or extern al sensiti ve resourc es
	596	User Inter face (OIA)
	597	Required
	598	Required
	599	Required
	600	Required
	601	Required
	602	VA Brandin g (OPIA)
	603	Required
	604	Required
	605	Required
	606	Required
	607	Required
	608	Privacy an d Applicat ion Securi ty (OIA)
	609	Required
	610	Required
	611	Required
	612	Required
	613	Required
	614	Sustainmen t Plan*
	615	Required
	616	Required
	617	Required
	618	Required
	619
	620	System Per formance I mpact Asse ssment (OI &T)*
	621	Required
	622	Required
	623	Required
	624
	625
	626	Enterprise Security
	627	Required
	628	Required
	629	Required
	630
	631
	632	Data and T erminology Standards Complianc e (OIA)*
	633	Required
	634	Required
	635
	636
	637
	638	Not Requir ed for Fie ld Test
	639
	640
	641
	642
	643
	644
	645	In order t o qualify for this c ategory, t he Mobile Applicatio n (MA) mus t meet the following criteria:
	646	Does not a ccess Pers onally Ide ntifiable Informatio n (PII) or Personal Health Ide ntifiers ( PHI) data
	647	Does not a ccess the VA network
	648	Does not r ead and/or write to VA or exte rnal datab ase
	649	Does not s tore data in any VA database
	650	Does not u tilize the VA Mobile Framework
	651	Does not r eceive fun ding (incl uding sust ainment an d future r elease fun ding) from the Offic e of Infor mation and Technolog y (OI&T)
	652	Note: The VAMF is co nsidered a VA resour ce. With t his defini tion, the following is implied :
	653	If an appl ication is hosted in the VA Mo bile Frame work (VAMF ), it cann ot be a Ve ry Low app . It is at least a L ow if it o nly reads pages with in the VAM F or reads data with in the VAM F
	654	If an appl ication us es a servi ce in the VAMF, but is not ins talled in the VAMF, then it mu st be at l east a Low app
	655	The MAE pr ovides dev elopment, test, inte gration, a nd other e nvironment s that pro vide stand ardized mo bile techn ologies an d toolsets . The Web and Mobile Solutions (WMS) tea m maintain s the MAE. The WMS t eam has de fined and continues to define methods fo r using th e tools to streamlin e the proc esses and make the c ompliance steps and documentat ion easier to find a nd read. T hese proce sses are i ntended to speed up the testin g process but still maintain q uality in order to e nsure the products w ork as int ended and pass gover nment regu lations, s uch as Nat ional Inst itute of S tandards a nd Technol ogy (NIST) security and privac y guidelin es, 508 co mpliance, and VA pat ient safet y regulati ons. Tools , such as JIRA and C onfluence (wiki), pr ovide the tracking m echanisms and docume nt managem ent that a llow for t hese strea mlined pro cesses.
	656	Each mobil e applicat ion will d ocument te st scripts and test cases in a Microsoft Excel wor kbook and include th e workbook as an att achment to the appli cation's M aster Test Plan (MTP ). The Req uirements Traceabili ty Matrix (RTM) for the mobile applicati on will be updated t o map the applicable test case identific ation (ID) for the t est cases that provi des test c overage fo r a user s tory. The MTP will d ocument th e overarch ing approa ch and tes t environm ent such t hat the te st cases a nd scripts contained as an att achment to the MTP n eed to onl y address specifics of the mob ile applic ation bein g tested. The HPE SQ A Test Tea m will com plete the test cases and test scripts fo r all appl icable fun ctional an d non-func tional req uirements in scope f or the mob ile applic ation bein g tested.
	657	Currently, the MAP2 program te am is fore casting th at it will take five Sprint it erations t o complete all devel opment and testing a ctivities (up throug h the Syst em Test le vel), for each new a pplication . With tha t in mind, system te sting will be a para llel testi ng activit y that wil l begin on ce the use r stories from Sprin t 1 for a given appl ication ha ve complet ed feature verificat ion testin g and met the defini tion of "d one" by th e VA Busin ess Owner of that ap plication. At the ea rliest, sy stem testi ng for the Rx Refill applicati on will be gin no ear lier than Sprint 2 a nd will be completed by Sprint 5.
	658	Product Co mponent Te st
	659	All compon ents of th e Rx Refil l applicat ion will g o through thorough p roduct com ponent (ak a unit) te sting by t he MAP2 HP E Developm ent team. The produc t componen t testing will follo w processe s as speci fied in th e VA's Mob ile Applic ation Deve lopment Li fe Cycle a nd documen ted using the approv ed templat es. Produc t componen t testing will be pe rformed us ing the de veloper's local work station co mputer. Th e steps in cluded in the proces s include:
	660	Analyze re quirements and desig n model to understan d the appl ication fu nctionalit y and depe ndencies
	661	Identify a ll the ser vices and interfaces affected by the app lication
	662	Specify al l the rout ines or se rvices tha t are call ed from va rious loca tions
	663	Execute te sts on pri oritized o ptions
	664	Execute te sts with d ifferent c ombination s of optio ns and dat a (e.g., t est with m inimal dat a entered and test w ith maxima l data ent ered)
	665	Perform ex ploratory testing (i .e., rando mly exerci se the mod ule, objec t, and opt ions based upon doma in knowled ge, past p erformance , and expe rtise)
	666	Record the actual te st results
	667	Component Integratio n Test
	668	As applica tion compo nents are completed by the Rx Refill MAP 2 HPE Deve lopment te am and int egrated in to the Rx Refill app lication, the applic ation will be tested to ensure functiona lity and r equirement satisfact ion. Compo nent-Integ ration tes ting is pe rformed to expose de fects in t he interfa ces and in teraction between in tegrated c omponents. The MAP2 H PE Develop ment team will execu te the cod e analysis tool Fort ify on the mobile ap plication for their mobile app lication. This tool will analy ze the cod e and prov ide any er rors or wa rnings tha t would be identifie d later du ring V&V o r security testing. The MAP 2 HPE Develo pment team will fix the critic al and hig h items id entified p rior to tu rning the applicatio n over for V&V testi ng.Develop ers are ex pected to test the c omponents of the app lication t hat they a re respons ible for a nd develop ers assign ed to the Scrum team need to t est the ap plication components as a whol e before t urning the applicati on over to the Scrum MAP2 HPE SQA tester team memb er for eac h sprint.T he Compone nt-Integra tion Test will be kn own as dev eloper led testing a nd will oc cur in the MAE Devel opment env ironment. This envir onment con tains mock services for system interface s. After c omponent-i ntegration testing i s complete d, the dev eloper res ponsible f or the app lication w ill provid e a report listing u nit test r esults ind icating th at all uni t test cas es have pa ssed and t he applica tion is re ady for fe ature veri fication t esting. Th e MAP2 HPE SQA Test team membe r assigned to the Sc rum team w ill perfor m feature verificati on testing and work with the o ther Scrum team memb ers to ens ure all de fects iden tified are fixed and retested or resolve d.It is ex pected tha t manual t esting wil l occur du ring this level, but that auto mated test scripts w ill be wri tten by th e MAP2 HPE Developme nt SQA tea m members to facilit ate this T est level. The MAP2 HPE Develo pment and Test Manag ers will h elp determ ine the sc ope of aut omated tes t script d evelopment for this Test level .
	669	System Tes t
	670	Members of the MAP2 HPE SQA Te st team wi ll perform the Syste m Test lev el, which starts onc e the firs t user sto ry is read y for this test leve l. System testing wi ll consist of execut ing functi onal, end- to-end, sy stem-integ ration, fu ll regress ion, perfo rmance, et c. test ca ses in the MAE Devel opment-Tes t environm ent. Test coverage w ill includ e all in-s cope funct ional and non-functi onal requi rements. T he MAE Dev elopment-T est enviro nment will contain l ive interf aces with as many VA enterpris e systems and/or ser vices as p ossible to perform v alid Syste m Tests. M ock servic es will on ly be used where abs olutely re quired (fo r example, if a give n VA syste m does not have a te st environ ment that can be con nected to the MAE). The MAP2 H PE SQA Tes t team wil l be in co ntrol of t he test da ta, and de velopers s hould not have acces s to this environmen t to make changes. I t may be r equired fo r develope rs to have read acce ss such th at they ca n debug is sues when they arise in System Test.Spec ifically, the MAP2 H PE SQA Tes t team wil l perform the follow ing functi ons:
	671	Write the test scrip ts includi ng:
	672	Test Case Descriptio ns
	673	Pre-condit ions/Post- conditions
	674	Test Cases
	675	Test Scrip t specific ations inc luding:
	676	Procedure steps
	677	Verificati on Points (VP)
	678	Expected R esults (ER )
	679	Comments
	680
	681	Update the Requireme nts Tracea bility Mat rix create d earlier by an Anal yst adding the Test Case ID to the matri x
	682	Execute th e test scr ipts
	683	Report res ults based on the Ac tual Resul ts compare d to the e xpected re sults
	684	Create bug issues in JIRA to d ocument de fects
	685	Perform te sting of r emediated defects
	686	As fixes t o the defe cts are pl anned (and put into the backlo g in JIRA) , the Test Team will track the m
	687	When fixed , the defe cts will b e retested by the Te st Team, c losed, or reopened d epending o n the outc ome of tes t executio n
	688	Regression testing w ill occur on new bui lds to ens ure that f unctionali ty that wa s working is still w orking
	689	Update the test scri pts with p ossible ne w tests or new steps to the ex isting tes t scripts as the sof tware is m odified
	690	Create art ifacts nee ded for re lease of t he softwar e, such as :
	691	Defect Log (includin g Software Anomalies report fo r issues s till prese nt in the software) – the defe ct log can be a repo rt output from JIRA
	692	Test Evalu ation Summ ary that p rovides ov erall stat istics and results a bout the S ystem Test level
	693	Performanc e and Load Test
	694	Note: Addi tional inf ormation f or this te st type wi ll be adde d/updated in a futur e Sprint i teration a s needed.P erformance and load testing wi ll be perf ormed by m embers of the MAP2 H PE Develop ment and S QA Test te ams as req uired by t he MAP2 Pe rformance Work State ment (PWS) document, dated 8/2 9/2014. Th e MAP2 pro gram team will revie w all appl icable VA Enterprise NFRs rela ted to per formance a nd load te st require ments for the Rx Ref ill applic ation. If it is dete rmined tha t performa nce and/or load test ing is req uired, per formance a nd/or load test case s and scri pts will b e develope d. The det ermination to execut e a Perfor mance and/ or Load Te st will be based on factors, s uch as the number of users to be using t he new app lication, the types of service s that wil l be execu ted within the envir onment, an d the stat us of prio r performa nce tests (i.e., hav e the func tions been tested be fore). If it is dete rmined tha t a Perfor mance and Load Test is require d, the fol lowing are high-leve l goals to be met fo r the Perf ormance an d Load Tes t:
	695	Validate t hat docume nted Criti cal Succes s Criteria around pe rformance of the int egrated sy stem and i nfrastruct ure, which map to Cr itical Suc cess Facto rs that ar e visible to and agr eed with t he custome r, have be en satisfi ed
	696	Assure the system wi ll perform as requir ed under e xpected us age levels
	697	Identify p oints of s ystem degr adation or bottlenec ks
	698	Identify s ystem capa city or li mitations on specifi c componen ts
	699	Reduce imp lementatio n risk
	700	Identify c auses of p oor perfor mance to t he busines s function s
	701	A System P erformance Impact As sessment w ill be com pleted bas ed on the performanc e test res ults OR th e fact tha t no perfo rmance imp act is exp ected base d on the S DD Addendu m review.
	702	User Funct ionality T est
	703	Note: Addi tional inf ormation f or this te st type wi ll be adde d/updated in a futur e Sprint i teration a s needed.A fter succe ssful comp letion of the System Test leve l to inclu de functio nal, non-f unctional, full regr ession, in tegration, end-to-en d, perform ance and l oad testin g (if appl icable), t he applica tion code will be pr omoted to the MAE In tegration test envir onment for further u ser accept ance testi ng. All te st documen ts /testin g package will be pr esented to the User Functional ity Testin g (UFT) te am testers along wit h a kick o ff call to formalize the begin ning of th e UFT Test level. Da ily status calls wil l also be coordinate d to discu ss issues encountere d during t esting and resolutio n of the i ssues will be docume nted. At t he end of the UFT Te st level, a UFT test approval will be co mpleted by the UFT t eam.Testin g at this level is t ypically p erformed b y members of the bus iness spon sor organi zation tha t have the knowledge of the fu nctional r equirement s, but the y can be p erformed b y actual e nd users. The object ive is to confirm th at the pro duct meets the busin ess need o r business acceptanc e criteria . It is th e responsi bility of the busine ss sponsor to define the conte nts of the UFT and t he methods for perfo rming it. The MAP2 H PE SQA tea m will sup port this Test level as requir ed.Since t he Rx Refi ll applica tion is de veloped us ing an Agi le process , business owner rep resentativ es should have been involved i n the deve lopment pr ocess, and it is mor e likely t hat the UF T will be less inten se and a s hort durat ion. It is expected that user functional ity testin g will be done using the user stories de veloped an d refined early in t he develop ment phase of the pr oject alon g with the same test data used during ea rlier feat ure verifi cation and system te sting.
	704	Enterprise System En gineering Testing
	705	Note: Info rmation fo r the Ente rprise Sys tem Engine ering (ESE ) testing section wi ll be adde d/updated in future iterations as needed .
	706	V&V Test
	707	The V&V Te st will be used to v alidate th e features or functi onal and n on-functio nal testin g complete d by MAP2 HPE SQA Te st team. M embers of the MAP2 H PE SQA Tes t team wil l work wit h the MAP2 HPE Relea se Manager to ensure the appli cation cod e and any required a rtifacts ( i.e., Test Cases, Te st Scripts , updated RTM, etc.) are ready for relea se to the V&V team.
	708	ESE Releas e Process
	709	Members of the MAP2 HPE SQA te am will co ordinate w ith the MA P2 HPE Rel ease Manag er to ensu re require d document ation is s ubmitted t o the ESE Compliance body resp onsible fo r completi ng this ty pe testing on the Rx Refill ap plication.
	710	Initial Op erating Ca pability E valuation
	711	Note: Info rmation fo r the Init ial Operat ing Capabi lity (IOC) Evaluatio n section will be ad ded/update d in futur e iteratio ns.The Ini tial Opera tion Capab ility (IOC ) Evaluati on will be accomplis hed throug h limited release of applicati ons to rea l users in the produ ction envi ronment. T he Rx Refi ll applica tion must pass all r equired co mpliance b ody review s and the V&V Test i n order to be releas ed to the real end u sers. The definition of the re quired com pliance bo dies is de pendent on the mobil e applicat ion. For e xample, mo bile appli cations th at are "Ve ry Low" sy stems do n ot have to be assess ed by the Privacy co mpliance t eam. The M AP2 Releas e Manageme nt process es will be followed before rel easing to production for IOC E valuation.
	712	Testing Te chniques
	713	Note: Addi tional inf ormation f or this se ction will be added/ updated in future it erations a s needed.
	714	Risk-based Testing
	715	Risk-based testing i s a techni que for pr ioritizing testing b ased on te sting the highest ri sk items f irst and c ontinuing to test do wn the ris k prioriti zation lad der as the testing s chedule pe rmits. In an Agile p rocess, it is typica l to imple ment high- risk items in early sprints. T he MAP2 Sc rum teams (i.e., Dev elopers) w ill perfor m their in ternal pro duct compo nent and c omponent-i ntegration testing o n these ea rly sprint s and cont inue testi ng as the agile cycl es continu e. The MAP 2 Scrum te ams will i dentify hi gh-risk ar eas and th e MAP2 Scr um teams ( i.e., HPE SQA Test T esters) wi ll be invo lved early in the pr ocess to t est these items prio r to the f inal devel opment Spr int. For t he System Test, V&V Test, and Compliance Review Te st, all fu nctional, non-functi onal, and compliance requireme nts must b e met. Whi le risk ba sed testin g can be p erformed t o identify high-risk issues fi rst, there is not as much valu e in this approach a s with the user stor y features testing d one by the MAP2 Scru m teams. I n the end, all requi rements mu st be test ed in some manner ev en if it i s through inspection versus ac tual testi ng.
	716	Enterprise Testing
	717	Note: Addi tional inf ormation f or the Ent erprise Te sting sect ion will b e added in future it erations a s needed.
	718	Security T esting
	719	The MAP2 H PE Develop ment and S QA Test te am will de velop test s to valid ate the se curity req uirements and to ens ure readin ess for th e independ ent testin g performe d by the E AS team. T he EAS tea m perform Web Applic ation Secu rity Asses sments (WA SAs) that are an in- depth pene tration te st for com mon vulner abilities, such as S QL Injecti on, Author ization By pass and C ross-Site- Scripting (CSS). WAS As cannot be started until the EAS team receives a completed questionn aire with working te st account s and a fu ll directo ry listing . The MAP2 HPE SQA T est team w ill ensure applicabl e applicat ion Unifor m Resource Locators (URLs) and test acco unts work before the questionn aire is su bmitted to the EAS t eam.In add ition to t he EAS eva luation, t he Network Security Operations Center (N SOC) will scan the a pplication and the c ode for vu lnerabilit ies. The M AP2 HPE De velopment team needs to comple te the NSO C Intake Q uestionnai re prior t o submitti ng the app lication f or the EAS evaluatio n. This pe netration test is pa rticularly important for those mobile ap plications that read and write data to V A systems.
	720	Privacy Te sting
	721	Note: Info rmation fo r the Priv acy Testin g section will be ad ded/update d in futur e iteratio ns as need ed.VHA Pri vacy and A pplication Security offices en sure that mobile app lications adhere to Privacy re gulations and statut es as well as VA pol icy. They use the Pr ivacy and Security c hecklist t o determin e if data is stored, transmitt ed, or ent ered by th e user, pr ovider, or employee. They also determine if there is sensiti ve informa tion like Private He alth Infor mation (PH I) or Pers onally Ide ntifiable Informatio n (PII) st ored on th e applicat ion. If it is, the D ata Securi ty branch will deter mine how t he Rx Refi ll applica tion prote cts the in formation. A Privacy checklist will be c ompleted b y the MAP2 HPE Devel opment tea m. The MAP 2 HPE SQA Testers wi ll work wi th the MAP 2 HPE Rele ase Manage r to ensur e the Priv acy checkl ist is com pleted for the Rx Re fill appli cation.
	722	Section 50 8 Complian ce Testing
	723	The Office of Inform ation and Technology (OIT) Sec tion 508 t ests mobil e content to verify that it co mplies wit h Section 508 standa rds includ ing 1194.2 1 (Softwar e and Plat forms), 11 94.22 Web, 1194.24 ( Multimedia ), and 119 4.31 Funct ional Requ irements. They work to facilit ate access to mobile technolog ies for an yone with disabiliti es.The Sec tion 508 O ffice will manually test VA pl atform-spe cific appl ications d irectly on the devic e using it s built-in accessibi lity featu res and su pported me thods. For example, they test with Voice Over on iO S and Talk back on An droid.The Section 50 8 Office w ill perfor m some aut omated tes ting on we b-based co ntent, but they also perform m anual test s to ensur e the (mob ile applic ation) pro perly impl ements acc essibility technique s on the d evices bro wsers.The MAP2 HPE D evelopment and SQA T est teams will perfo rm 508 com pliance te sting on t he Rx Refi ll mobile applicatio n prior to initiatin g the Sect ion 508 Pr ogram Offi ce to perf orm their independen t testing.
	724	Multi-Divi sional Tes ting
	725	Note: Info rmation fo r the Mult i-Division al Testing section w ill be add ed/updated in future iteration s as neede d.Multi-Di visional t esting is required t o ensure t hat all ap plications will oper ate in a m ulti-divis ion or mul ti-site en vironment recognizin g that an enterprise perspecti ve while f ull suppor ting local health ca re deliver y. If mult i-division al require ments are present in an applic ation's BR D, the MAP 2 HPE Deve lopment an d SQA Test teams wil l verify a nd validat e that the applicati on under t est compli es with th e multi-di visional r equirement s stated p rior to in itiating t he applica ble Compli ance body to perform their ind ependent t esting.
	726	Test Types
	727	Note: addi tional inf ormation f or the Tes t Types se ction will be added/ updated in future it erations a s needed.T able 4 lis ts the fol lowing tes t types th at will be performed under MAP 2. While a ll of thes e test typ es do not list the M AP2 HPE De velopment or SQA Tes t teams, t he MAP2 HP E Developm ent Team a nd the cor responding MAP2 HPE SQA Test t eam must e nsure that the mobil e applicat ion is com pliant in the partic ular area before mov ing the mo bile appli cation pas t the Syst em Test le vel.
	728	Table 4: T est Types
	729	Test Types
	730	Party Resp onsible
	731	Access Con trol Testi ng
	732	MAP2 HPE D evelopment and SQA T eams, VA V &V Team
	733	Build Veri fication T esting
	734	MAP2 HPE D evelopment Team
	735	Code Cover age
	736	MAP2 HPE D evelopment Team, VA Compliance Body
	737	Compliance Testing
	738	VA V&V Tea m and Comp liance Bod ies
	739	Component Integratio n Testing
	740	MAP2 HPE D evelopment Team
	741	Data and D atabase In tegrity Te sting
	742	MAP2 HPE D evelopment and SQA T eams, VA V &V Team
	743	Documentat ion Testin g
	744	VA V&V Tes t Team
	745	Error Anal ysis Testi ng
	746	MAP2 HPE D evelopment and SQA T eams, VA V &V Team
	747	End-to-End Testing
	748	MAP2 HPE D evelopment and SQA T est Team, VA V&V Tea m
	749	Functional Testing
	750	MAP2 HPE D evelopment and SQA T est Team, VA V&V Tea m
	751	Informatio n Assuranc e Testing
	752	MAP2 HPE D evelopment and SQA T est Team, VA V&V Tea m
	753	Installati on Testing
	754	MAE Mainte nance Team
	755	Integratio n Testing
	756	MAP2 HPE D evelopment and SQA T eams, VA V &V Team
	757	Integrated Performan ce and Loa d Testing
	758	MAP2 HPE D evelopment and SQA T eams
	759	Privacy Te sting
	760	MAP2 HPE D evelopment and SQA T eams, VA V &V Team an d Complian ce Bodies
	761	Product Co mponent Te sting
	762	MAP2 HPE D evelopment Team
	763	Regression Testing
	764	MAP2 HPE D evelopment and SQA T eams, VA V &V Team
	765	Section 50 8 Complian ce Testing
	766	MAP2 HPE D evelopment and SQA T est Team, VA V&V Tea m and Comp liance Bod ies
	767	Security T esting
	768	MAP2 HPE D evelopment and SQA T est Team, VA V&V Tea m and Comp liance Bod ies
	769	Smoke Test ing
	770	MAP2 HPE S QA Test Te am, VA V&V Team
	771	Usability Testing
	772	VA V&V Tea m and Comp liance Bod ies
	773	User Funct ionality T esting
	774	VA Stakeho lders
	775	User Inter face Testi ng
	776	MAP2 HPE D evelopment and SQA T est Team, VA V&V Tea m
	777	Productivi ty and Sup port Tools
	778	Note: Info rmation fo r the Prod uctivity a nd Support Tools sec tion will be added i n future i terations. Table 5 de scribes th e tools th at will be employed to support this Mast er Test Pl an.
	779	Table 5: T ool Catego ry or Type s
	780	Tool Categ ory or Typ e
	781	Tool Brand Name
	782	Vendor or In-house
	783	Version
	784	Test Manag ement
	785	MS Excel 2 013
	786	Vendor - H PE
	787	N/A
	788	Defect Tra cking
	789	JIRA – Atl assian 6.2
	790	Vendor - H PE
	791	N/A
	792	Code Analy zer
	793	HP Fortify
	794	Vendor - H PE
	795	N/A
	796	Document M anagement
	797	Confluence (wiki) – Atlassian 6.2
	798	Vendor - H PE
	799	N/A
	800	Performanc e and Load Testing
	801	Apache JMe ter – Open Source
	802	Vendor - H PE
	803	N/A
	804	Configurat ion Manage ment
	805	Stash/Git – Atlassia n 6.2
	806	Vendor - H PE
	807	N/A
	808	DBMS tools
	809	Oracle & M ongoDB
	810	Vendor - H PE
	811	N/A
	812	Functional Test Auto mation
	813	Selenium 2 .5.0
	814	Vendor - H PE
	815	N/A
	816	Web Servic e Test Aut omation
	817	SoapUI – O pen Source
	818	Vendor - H PE
	819	N/A
	820	Database Q uery Tools
	821	Quest -TOA D, Oracle SQLPlus
	822	Vendor - H PE
	823	N/A
	824	Test Crite ria
	825	Process Re views
	826	The Master Test Plan undergoes two revie ws:
	827	Peer Revie w – upon c ompletion of the Mas ter Test P lan
	828	MAP2 HPE T echnical W riter Revi ew
	829	Formal Rev iew – afte r the HPE MAP2 Progr am and Pro ject Manag er approve s the Mast er Test Pl an
	830	The Master Test Plan does serv e as an in put artifa ct used fo r Mileston e 1 and Mi lestone 2 Reviews of the Devel opment pha se.For mor e informat ion on the milestone reviews a ssociated with testi ng, see th e required artifacts and templ ates for P MAS as par t of the V A's Mobile Applicati on Develop ment Life Cycle.
	831	Pass/Fail Criteria
	832	A test wil l be consi dered as s uccessful when it pa sses 100% of the tes t cases.Pe r the Agil e Developm ent Method ology (ADM ) followed by the MA P2 Scrum t eams, all defect(s) found for a given us er story w ill be fix ed and ret ested duri ng the spr int the fe ature(s) w ere develo ped. If fo r some rea son the de fect(s) fo r a certai n user sto ry cannot be fixed a nd reteste d prior to Sprint co mpletion, the defect (s) and ap plicable u ser story will be ad dressed in a subsequ ent sprint .For the S ystem Test , pass cri teria is d efined in each speci fic test c ase; but i n general, a test is considere d as passe d when the functiona lity meets the requi rements as defined w ith no Lev el 1, Leve l 2, or Le vel 3 defe cts identi fied. If a ny test ca se within the overal l test fai ls, then t he whole t est fails. It is typ ical that an applica tion will still be r eleased wi th some Le vel 3 and Level 4 de fects, but it must b e approved by the bu siness own er and the release p rocesses i n order to be approv ed out to production . The open issues ar e provided as part o f the rele ase docume ntation.A test is co nsidered f ailed when the funct ionality d oes not me et the req uirements as defined .
	833	Suspension and Resum ption Crit eria
	834	Suspension : Every ef fort will be made to continue testing wh en failure s are foun d. However , some fai lures can impact pro duct funct ionality s ignificant ly, and ex ecution is no longer possible. Testing w ill be sus pended if functional ity is sig nificantly impacted until a fi x or worka round is p rovided.Re sumption: In general , testing will be re sumed from the point of suspen sion once a fix or w orkaround is provide d. If the fix or wor karound ha s implicat ions outsi de the bou ndaries of the immed iate test case proce dure, it w ill be nec essary to execute ad ditional r egression test proce dures or t est cases. The Projec t Manager, at the re commendati on of the MAP2 HPE S QA Test te am, has th e authorit y to suspe nd testing . Testing will be su spended if :
	835	Test accou nts or ver ifiable it ems are un available or become unstable
	836	A failure occurs tha t prevents the test from conti nuing or i nvalidates any addit ional test ing to be performed or corrupt s the data base
	837	A defect i s discover ed that co rrupts the data with in the dat abase in s uch a way that proce eding woul d cause se vere damag e to the t est enviro nment
	838	The compon ent being tested fai ls or a ma jor compon ent fails. A major c omponent f ailure is one that o ne can rea sonable as sume will result in other test case fail ures. If t here are s o many def ects that continuing testing i s a waste of resourc es, testin g will be suspended.
	839	Testing wi ll resume when the c omponent o r code has been repa ired, rebu ilt and ve rsioned, u nit tested , gone thr ough syste m test, an d is insta lled into the test e nvironment by the MA E maintena nce team. If the cau se of the suspension is due to either un stable or unavailabl e test env ironment, testing wi ll resume when the t est enviro nment beco mes stable and/or av ailable.
	840	Acceptance Criteria
	841	The follow ing activi ties must be perform ed to comp lete the t est and va lidation p rocess:
	842	Updates to test docu mentation have been completed and are un der config uration ma nagement c ontrol on the mobile applicati on wiki pa ge
	843	All requir ed test ty pes have b een comple ted (i.e., Functiona l, 508, Se curity and Regressio n, etc.)
	844	Test cases have been executed according to the tes t plan, an d any devi ations are documente d and appr oved
	845	All compli ance bodie s have app roved the release or stated th at their p articipati on is not required f or the Rx Refill mob ile applic ation
	846	All defect s have bee n analyzed and chang ed to the appropriat e state
	847	All closed defects h ave an ass igned defe ct root ca use
	848	After comp letion of the above activities , the acce ptance cri teria for release of the appli cation is:
	849	For System Test, the Rx Refill applicati on has no Level 1, L evel 2, or Level 3 d efects exc ept as spe cifically accepted b y the busi ness owner .
	850	All defect s that are in the ap plication are docume nted in th e Test Eva luation Su mmary repo rt as know n defects and accept ed by the business o wner.
	851	All MAP2 R elease Man agement ac tivities a re carried out.
	852	The busine ss sponsor or owner and requir ed complia nce bodies have sign ed off on the releas e.
	853	Test Deliv erables
	854	Table 6 li sts the te st deliver ables for the Rx Ref ill applic ation.
	855	Table 6: T est Delive rables
	856	Test Deliv erables
	857	Responsibl e Party
	858	Master Tes t Plan (It erative)
	859	MAP2 HPE S QA Test Pl anner/Engi neer
	860	Master Tes t Plan Che cklist
	861	MAP2 HPE S QA Test Ma nager
	862	Test Execu tion Risks
	863	MAP2 HPE S QA Test Ma nager and Project Ma nager
	864	Test Sched ule
	865	MAP2 HPE S QA Test Ma nager and Project Ma nager
	866	Test Cases /Test Scri pts (Itera tive)
	867	MAP2 HPE D evelopers and SQA Te sters
	868	Test Data
	869	MAP2 HPE D evelopers and SQA Te sters
	870	Test Envir onment
	871	MAP2 HPE S QA Test Ma nager
	872	Test Evalu ation Summ ary and De fect Log ( Iterative)
	873	MAP2 HPE S QA Test Pl anner/Engi neer for S print Iter ations and System Te st VA V&V Team for V &V Tests a nd Complia nce Review s
	874	Requiremen ts Traceab ility Matr ix
	875	MAP2 HPE S QA Test Pl anner/Engi neer for S print Iter ations and System Te st VA V&V Team for V &V Tests a nd Complia nce Review s
	876	Test Sched ule
	877	Table 7 li sts the te sting mile stones for the Rx Re fill appli cation.
	878	Table 7: T esting Mil estones
	879	Testing Mi lestones
	880	Responsibl e Party
	881	Deliver In itial MTP and MTP Ch ecklist fo r all MAP2 Mobile Ap plications
	882	MAP2 HPE T est Manage r
	883	Complete S print 1 Us er Story/U nit Test/S QA Testing
	884	MAP2 HPE D evelopers and SQA Te sters
	885	Complete S print 2 Us er Story/U nit Test/S QA Sprint Testing
	886	MAP2 HPE D evelopers and SQA Te sters
	887	Complete S print 3 Us er Story/U nit Test/S QA Sprint Testing
	888	MAP2 HPE D evelopers and SQA Te sters
	889	Complete S print 4 Us er Story/U nit Test/S QA Sprint Testing
	890	MAP2 HPE D evelopers and SQA Te sters
	891	Complete S print 5 Us er Story/U nit Test/S QA Sprint Testing
	892	MAP2 HPE D evelopers and SQA Te sters
	893	Complete S print 6 Us er Story/U nit Test/S QA Sprint Testing
	894	MAP2 HPE D evelopers and SQA Te sters
	895	Complete S ystem Test ing
	896	MAP2 HPE S QA Test Te am
	897	Complete C ompliance Reviews, V &V Testing , IOC
	898	VA Complia nce Bodies and V&V T est Team
	899	Test Envir onments
	900	A test env ironment i s an envir onment con taining ha rdware, in strumentat ion, simul ators, sof tware tool s, and oth er support elements needed to conduct a test. Simu lators in a service- oriented a rchitectur e, such as used in V A, include "mock ser vices," wh ich simula te the beh avior of V A services . The MAE contains m ock servic es in some areas to control th e interfac es and dat a retrieve d and simu late test scenarios. The test e nvironment s for the Rx Refill applicatio n will be the MAE De velopment and Develo pment-Test environme nts.
	901	Test Envir onment Con figuration s
	902	The MAE in cludes the following environme nts and to ols that c an be util ized by th e MAP2 Pro gram team: Developmen t environm ent – This includes the follow ing servic es and too ls:
	903	Git/Stash – Code rep ositories are provid ed for the mobile ap plication as well as access to the Mobil e Adapter (Health Ad apter) cod e reposito ry to prov ide the de velopment team acces s to the c ommon serv ices provi ded
	904	Jenkins – For buildi ng the sof tware into deployabl e units
	905	Fortify – For scanni ng the sof tware
	906	JIRA – For executing the agile processes , document ing user s tories, cr eating agi le boards, documenti ng softwar e issues, and so on. Complianc e issues a re include d in the J IRA projec t so the d evelopment team can track comp letion of these requ irements a nd attach the approp riate docu ments.
	907	Confluence – For doc umenting t he mobile applicatio n in a wik i format. The wiki c an be used to delive r the docu ments need ed by MAP and the V& V team.
	908	Developmen t integrat ion server s – To inc lude mock services f or standar d VA enter prise serv ices to be called by the Mobil e Adapter services a nd/or dire ctly from mobile app lications
	909	MAE Develo pment – De velopers u se this en vironment for intern al compone nt integra tion, not external i ntegration . It allow s the user s to test deployment of multip le develop er's code from the c ode reposi tory. Feat ures of th is environ ment are:
	910	Mock Servi ces for ex ternal sys tems, such as Identi ty and Acc ess Manage ment (IAM) , Master V eteran Ind ex (MVI), Administra tive Data Repository (ADR), Vi stA (or de v VistA), Medical Do main Web S ervices (M DWS), Corp orate Data Warehouse (CDW), et c.
	911	All test d ata and fa ke patient s/users
	912	MAE Develo pment-Test – MAP2 HP E SQA Test ers will p erform sys tem testin g in this environmen t.Features of this e nvironment are:
	913	Real Test Services f or externa l systems, such as I AM, MVI, A DR, VistA (or dev Vi stA), MDWS , CDW, etc .
	914	Mock Servi ces used w here devel opment int egrations are not al lowed
	915	All test d ata and fa ke patient s/users
	916	MAE Integr ation – Th is environ ment will be used fo r system t esting and to date f or V&V and Complianc e testing. When more resources are obtai ned, this will be a system tes ting envir onment. Fe atures of this envir onment are :
	917	Real Test Services f or externa l systems, such as I AM, MVI, A DR, VistA (or dev Vi stA), MDWS , CDW, etc .
	918	Mock Servi ces used w here neede d such as CDW
	919	All test d ata and fa ke patient s/users
	920	Access to these MAE environmen ts is obta ined throu gh the Web and Mobil e Solution request p rocess. Th e MAP2 HPE Developme nt and SQA Test team s can only have acce ss to the MAE Develo pment envi ronments. The MAP2 C M manager must have access to all MAE de velopment environmen ts for aud iting purp oses. The MAE Mainte nance Team maintains all of th e MAE envi ronments, and this t eam should not inclu de any dev elopers fr om the MAP 2 Program team.
	921	Base Syste m Hardware
	922	Note: Addi tional inf ormation f or the Bas e System H ardware se ction will be added/ updated in future it erations a s needed.T able 8 set s forth th e system r esources f or the tes t effort p resented i n this Mas ter Test P lan.The sp ecific ele ments of t he test sy stem may n ot be full y understo od in earl y iteratio ns; so, th is section may be co mpleted ov er time. T he test sy stem will simulate t he product ion enviro nment as c losely as possible, scaling do wn the con current ac cess and d atabase si ze, and so forth, if and where appropria te. The Sy stem Hardw are Resour ces table will be ta ilored as required.
	923	Table 8: S ystem Hard ware Resou rces
	924	Resource
	925	Quantity
	926	Name and T ype
	927	Test Devel opment PCs
	928	1
	929	HPE-issued Windows 7 laptop
	930	Mobile Dev ice
	931	1
	932	GFE-issued Apple iPa d
	933	Base Softw are Elemen ts in the Test Envir onments
	934	Additional informati on for the Base Soft ware Eleme nts in the Test Envi ronments s ection wil l be added /updated i n future i terations as needed. Table 9 de scribes th e base sof tware elem ents that are requir ed in the test envir onment for this Mast er Test Pl an.
	935	Table 9: S oftware El ements
	936	Software E lement Nam e
	937	Version
	938	Type and O ther Notes
	939	Windows
	940	7.0
	941	Desktop Op erating Sy stem
	942	IOS
	943	7+
	944	Apple Oper ating Syst em
	945	Internet E xplorer
	946	9 and11
	947	Laptop Int ernet Brow ser
	948	Safari
	949	7+
	950	Mobile Int ernet Brow ser
	951	Android St udio
	952	1.5.1
	953	Emulator
	954	Chrome
	955	40+
	956	Laptop Int ernet Brow ser
	957	Firefox
	958	36+
	959	Laptop Int ernet Brow ser
	960
	961	Staffing a nd Trainin g Needs
	962	Note: Addi tional inf ormation f or the Sta ffing and Training N eeds secti on will be added/upd ated in fu ture itera tions as n eeded.Tabl e 10 descr ibes the p ersonnel r esources n eeded to p lan, prepa re, and ex ecute this Master Te st Plan.
	963	Table 10: Staffing R esources
	964	Testing Ta sk
	965	Quantity o f Personne l Needed
	966	VA MA Deve lopment Ph ase
	967	Duration/ Days
	968	Create/Upd ate Master Test Plan – Applica tion-Level
	969	1
	970	Planning/D evelopment
	971	TBD
	972	Establish the Test E nvironment
	973	1
	974	Planning/D evelopment
	975	TBD
	976	Create/Upd ate Test C ases and S cripts
	977	3
	978	Developmen t
	979	TBD
	980	Perform Fe ature Veri fication/S ystem Test s
	981	3
	982	Developmen t
	983	TBD
	984	Test Manag ement Repo rting
	985	1
	986	Developmen t
	987	TBD
	988	Coordinate with V&V Test team and Compli ance Bodie s
	989	3
	990	Developmen t/Complian ce Review
	991	TBD
	992	Table 11 l ists the p ersonnel t hat requir e training . This doc ument does not apply to any VA User trai ning neede d.
	993	Table 11: Training N eeds
	994	Name
	995	Training N eed
	996	Training O ption
	997	Estimated Training H ours
	998	MAP2 HPE D evelopers and SQA Te sters
	999	AMP Traini ng
	1000	Online
	1001	2
	1002	Risks and Constraint s
	1003	Note: Addi tional inf ormation f or the Ris k and Cons traints se ction will be added/ updated in future it erations a s needed.R isks and c onstraints will be t racked in JIRA at th e MAP2 mob ile applic ation-leve l. JIRA wi ll be upda ted as ris ks and con straints a re identif ied.Again, risks are tracked i n JIRA bot h at the m obile appl ication-le vel and th e MAP prog ram-level. Risks tha t affect t he complet eness or e ffectivene ss are the following :
	1004	Lack of En vironments – need to ensure VA will be c onfiguring the MAE I ntegration and Pre-P roduction environmen t to match the confi guration o f the MAE Developmen t-Test env ironment. This is to fully sup port integ rated syst em testing , V&V test ing, and p erformance testing. If the con figuration is not th e same, th e overall test appro ach is com promised.
	1005	If an inte grated MAE Developme nt-Test (i .e., CDW, HDR, Vista , etc.) en vironment is not ava ilable, th en there i s a risk t hat testin g will not be adequa te for VA V&V and pr oduction r elease
	1006	Assuming p erformance and load testing wi ll be perf ormed in t he MAE Dev elopment-T est enviro nment, and this envi ronment is not a clo se match t o the prod uction env ironment, then then there is a higher ri sk that th e migrated applicati on will no t perform as expecte d in the P roduction environmen t
	1007	In the cas e of read- only appli cations, t he pre-Pro duction en vironment can be int egrated wi th other p re-Product ion/Produc tion envir onments fo r UFT test ing, but o bviously a pre-Produ ction envi ronment ca nnot write to a Prod uction env ironment. This needs to be man aged close ly on an a pplication by applic ation basi s and a me thod of te sting cons tructed su ch that it is clear that adequ ate testin g has been performed .
	1008	Test Metri cs
	1009	Metrics ar e a system of parame ters or me thods for quantitati ve and per iodic asse ssment of a process that is to be measur ed. Table 12 describ es the tes t metrics to be capt ured and r eported on for the R x Refill m obile appl ication.
	1010	Table 12: Test Metri cs
	1011	Report Nam e
	1012	Report Typ e
	1013	Report Des cription
	1014	Projected vs. Actual Test Effo rt
	1015	Project Ma nagement
	1016	The Estima ted vs. Ac tual Test Effort rep ort provid es managem ent with a view of h ow well th e project met its ag reed upon delivery t imeline de termined a t project initiation . The data used to c onstruct t his indica tor is as follows:
	1017	Estimated Hours: Est imated hou rly effort associate d with com pleting al l activiti es require d to meet the exit c riteria fo r a given test phase
	1018	Actual Hou rs: Hourly effort as sociated w ith comple ting all a ctivities required t o meet the exit crit eria for a given tes t phase
	1019	Actual Tes t Effort b y Level
	1020	Project Ma nagement
	1021	The Actual Test Effo rt by leve l report p rovides a breakdown of the tes ting effor t by each level for each appli cation in a MA relea se.
	1022	Requiremen t Test Cas e Coverage
	1023	Coverage
	1024	Requiremen ts Test Ca se Coverag e report p rovides a method to measure th e percenta ge of cove rage throu gh test pr ocedures. The data u sed to con struct thi s indicato r is as fo llows:
	1025	Baseline R equirement s: The num ber of req uirements approved b y the team and clien t to be ad dressed in the MA re lease, ite ration, or build und er develop ment
	1026	Requiremen ts Mapped to Test Sc ripts: The number of baseline requiremen ts that ha ve been ma pped to te st scripts for the s pecified r elease
	1027	Overall Te st Case/Sc ript Execu tion Statu s
	1028	Progressio n
	1029	The Overal l Test Pro cedure Exe cution Sta tus Report details t he progres sion and e xtent of t he test ef fort at a given poin t and time and the p ercentage of test ca ses execut ed in addi tion to:
	1030	Total Test Scripts – The numbe r of test scripts sc heduled to be run in the curre nt test cy cle. The t est cycle will be de noted in t he slide
	1031	Scripts to be Execut ed – The n umber of s cripts yet to be run
	1032	Currently Passed – t he number of scripts for the c urrent cyc le that ha ve passed
	1033	First Time Passed – The number of "Curre ntly Passe d" scripts that pass ed the fir st time th ey were ex ecuted
	1034	Daily Test Execution Status
	1035	Progressio n
	1036	The Daily Test Execu tion Statu s reports details th e daily pr ogression of the tes ting effor t versus t he planned progressi on by refl ecting how many scri pts have p assed and failed on a daily ba sis. The r eport capt ures the f ollowing m etrics:
	1037	Test Scrip ts in Rele ase: Numbe r of scrip ts that pr ovide cove rage for t he release
	1038	Test Scrip ts Passed Cumulative Planned: Number of scripts th e test tea m expects to have pa ssed at a given poin t in time
	1039	Test Scrip ts Passed Cumulative Actual: N umber of s cripts tha t have act ually pass ed at a gi ven point in time
	1040	Test Scrip ts Passed Daily: Num ber of scr ipts run i n a given day that h ave succes sfully pas sed
	1041	Test Scrip ts Failed Daily: Num ber of scr ipts run i n a given day that f ailed
	1042	Open Defec ts by Seve rity
	1043	Progressio n
	1044	Open Defec ts by Seve rity Repor t captures the ratio of report ed defects by the se verity lev el and the :
	1045	Total numb er of defe cts identi fied
	1046	Number of defects as sociated t o test cas e/test scr ipt and us er stories /requireme nts
	1047	Percentage of defect s listed b y cause an d severity
	1048
	1049	Attachment A - Appro val Signat ures
	1050	The Master Test Plan documents the progr am's overa ll approac h to testi ng and inc ludes:
	1051	Items to b e tested
	1052	Test appro ach
	1053	Test crite ria
	1054	Test deliv erables
	1055	Test sched ule
	1056	Test envir onments
	1057	Staffing a nd trainin g needs.
	1058	Risks and constraint s
	1059	Test Metri cs
	1060	Review Dat e: Constan ce Murphy, VA MAP2 P rogram Man ager _____ __________ __________ __________ __________ __________ __________ __________ ___Signed: Date:
	1061
	1062	Luz A. Cuf f, VA MAP2 Contracti ng Officer 's Represe ntative __ __________ __________ __________ __________ __________ __________ __________ ______Sign ed: Date :
	1063
	1064	VA MAP2 Bu siness Own er _______ __________ __________ __________ __________ __________ __________ __________ _Signed: Date:
	1065	Attachment B – Defec t Level De finitions
	1066	Level 1 Cr itical - 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.
	1067	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.
	1068	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
	1069	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
	1070	Any defect that caus es corrupt ion of dat a from a r esult of t he system (as oppose d to user error)
	1071	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
	1072	Loss of fu nctionalit y resultin g in erron eous eligi bility/enr ollment de terminatio ns or comm unications not being sent
	1073	Level 2 Hi gh- The de fect resul ts in the failure of the compl ete softwa re system, of a subs ystem, or of a softw are unit ( program or module) w ithin the system. Th ere is no way to mak e the fail ed compone nt(s) func tion. Howe ver, there are accep table proc essing alt ernatives which will yield the desired r esult.
	1074	A major de fect in th e function ality that does not result in corruption of data
	1075	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:
	1076	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 .
	1077	Any defect that does not confo rm to Sect ion 508 st andards
	1078	Any defect that resu lts in ina ccurate or missing r equirement s
	1079	Any defect that resu lts in inv alid authe ntication or authent ication of an invali d end user
	1080	Level 3 Me dium - 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.
	1081	Minor func tionality is not wor king as in tended and a workaro und exists but is no t suitable for long term use
	1082	The inabil ity of a v alid user to access the system consisten t with gra nted privi leges
	1083	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
	1084	Any defect producing cryptic, incorrect, or inappr opriate er ror messag es
	1085	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
	1086	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
	1087	Level 4 Lo w - The de fect does not cause a failure, does not impair usa bility, an d the desi red proces sing resul ts are eas ily obtain ed by work ing around the defec t.
	1088	Minor loss of, or de fect in th e function ality wher e a long t erm use ex ists
	1089	Low-level cosmetic i ssues
	1090
	1091	Attachment C – Test Case/Scrip t – Covera ge
	1092	Attach tes t cases/sc ripts to b e used for the Rx Re fill appli cation.Tes t Case:Des criptionTC Pre Condi tions:
	1093	Pre-Condit ions
	1094	Post-Condi tions
	1095	Acceptance Criteria
	1096
	1097
	1098
	1099	The user/t ester shou ld have ac cess to al l needed a reas like the store to downloa d and inst all the ap p. The use r/tester s hould have the app i nstalled o n the devi ce. The us er/tester should be familiar w ith Mobile apps cont rols, such as slides and spinn ers.
	1100
	1101
	1102	Test Scrip tTest Scri pt Descrip tion:Test Procedure
	1103	Pre-Condit ions
	1104	Post-Condi tions
	1105	Acceptance Criteria
	1106
	1107
	1108
	1109
	1110
	1111
	1112	Auto Imple mentation: Manual Im plementati on: Test I nputs: Tes t Design
	1113	Step
	1114	Type
	1115	Note
	1116	Descriptio n
	1117	1
	1118	Step
	1119
	1120
	1121	2
	1122	VP
	1123	.
	1124
	1125	3
	1126	Step
	1127
	1128
	1129	4
	1130	VP
	1131
	1132
	1133	Attachment D – Test Type Defin itions
	1134	Test Type
	1135	Definition
	1136	Access Con trol Testi ng
	1137	A type of testing th at attests that the target-of- test data (or system s) are acc essible on ly to thos e actors f or which t hey are in tended as defined by use cases . Access C ontrol Tes ting verif ies that a ccess to t he system is control led and th at unwante d or unaut horized ac cess is pr ohibited. This test is impleme nted and e xecuted on various t argets-of- test.
	1138	Benchmark Testing
	1139	A type of performanc e testing that compa res the pe rformance of new or unknown fu nctionalit y to a kno wn referen ce standar d (e.g., e xisting so ftware or measuremen ts). For e xample, be nchmark te sting may compare th e performa nce of cur rent syste ms with th e performa nce of the Linux/Ora cle system .
	1140	Build Veri fication T esting (Pr erequisite : Smoke Te st)
	1141	A type of testing pe rformed fo r each new build com paring the baseline with the a ctual obje ct propert ies in the current b uild. The output fro m this tes t indicate s what obj ect proper ties have changed or do not me et the req uirements. Together with the S moke test, the Build Verificat ion test m ay be util ized by pr ojects to determine if additio nal functi onal testi ng is appr opriate fo r a given build or i f a build is ready f or product ion.
	1142	Business C ycle Testi ng
	1143	A type of testing th at focuses upon acti vities and transacti ons perfor med end to end over time. This test type executes the functi onality as sociated w ith a peri od of time (e.g., on e-week, mo nth, or ye ar). These tests inc lude all d aily, week ly, and mo nthly cycl es, and ev ents that are date-s ensitive ( e.g., end of the mon th managem ent report s, monthly reports, quarterly reports, a nd year-en d reports) .
	1144	Compliance Testing
	1145	A type of testing th at verifie s that a c ollection of softwar e and hard ware fulfi lls given specificat ions. For example, t hese tests will mini mally incl ude: "core specifica tions for rehosting - ver.1.5- draft 3.do c", Sectio n 508 of T he Rehabil itation Ac t Amendmen ts of 1998 , Race and Ethnicity Test, and VA Direct ive 6102 C ompliance. It does n ot exclude any other tests tha t may also come up.
	1146	Component- Integratio n Testing
	1147	Testing pe rformed to expose de fects in t he interfa ces and in teraction between in tegrated c omponents as well as verifying installat ion instru ctions.
	1148	Configurat ion Testin g
	1149	A type of testing co ncerned wi th checkin g the prog ram's comp atibility with as ma ny possibl e configur ations of hardware a nd system software. In most pr oduction e nvironment s, the par ticular ha rdware spe cification s for the client wor kstations, network c onnections , and data base serve rs vary. C lient work stations m ay have di fferent so ftware loa ded, for e xample, ap plications , drivers, and so on at any on e time; ma ny differe nt combina tions may be active using diff erent reso urces. The goal of t he configu ration tes t is findi ng a hardw are combin ation that should be , but is n ot, compat ible with the progra m.
	1150	Contention Testing
	1151	A type of performanc e testing that execu tes tests that cause the appli cation to fail with regard to actual or simulated concurrenc y. Content ion testin g identifi es failure s associat ed with lo cking, dea dlock, liv elock, sta rvation, r ace condit ions, prio rity inver sion, data loss, los s of memor y, and lac k of threa d safety i n shared s oftware co mponents o r data.
	1152	Data and D atabase In tegrity Te sting
	1153	A type of testing th at verifie s that dat a is being stored by the syste m in a man ner where the data i s not comp romised by the initi al storage , updating , restorat ion, or re trieval pr ocessing. This type of testing is intend ed to unco ver design flaws tha t may resu lt in data corruptio n, unautho rized data access, l ack of dat a integrit y across m ultiple ta bles, and lack of ad equate tra nsaction p erformance . The data bases, dat a files, a nd the dat abase or d ata file p rocesses s hould be t ested as a subsystem within th e applicat ion.
	1154	Documentat ion Testin g
	1155	Documentat ion testin g is a typ e of testi ng that sh ould valid ate the in formation contained within the software documentat ion set fo r the foll owing qual ities: com pliance to accepted standards and conven tions, acc uracy, com pleteness, and usabi lity. The documentat ion testin g should v erify that all of th e required informati on is prov ided in or der for th e appropri ate user t o be able to properl y install, implement , operate, and maint ain the so ftware app lication. The curren t VistA do cumentatio n set can consist of any of th e followin g manual t ypes: Rele ase Notes, Installat ion Guide, User Manu als, Techn ical Manua l, and Sec urity Guid e.
	1156	Error Anal ysis Testi ng
	1157	This type of testing verifies that the a pplication checks fo r input, d etects inv alid data, and preve nts invali d data fro m being en tered into the appli cation. Th is type of testing a lso includ es the ver ification of error l ogs and er ror messag es that ar e displaye d to the u ser.
	1158	Explorator y Testing
	1159	A techniqu e for test ing comput er softwar e that req uires mini mal planni ng and tol erates lim ited docum entation f or the tar get-of-tes t in advan ce of test execution , relying on the ski ll and kno wledge of the tester and feedb ack from t est result s to guide the ongoi ng test ef fort. Expl oratory te sting is o ften condu cted in sh ort sessio ns in whic h feedback gained fr om one ses sion is us ed to dyna mically pl an subsequ ent sessio ns.
	1160	Failover T esting
	1161	A type of testing te st that en sures an a lternate o r backup s ystem prop erly "take s over" (i .e., a bac kup system functions when the primary sy stem fails ). Failove r Testing also tests that a sy stem conti nually run s when the failover occurs, an d that the failover happens wi thout any loss of da ta or tran sactions. Failover T esting sho uld be com bined with Recovery Testing.
	1162	Installati on Testing
	1163	A type of testing th at verifie s that the applicati on or syst em install s as inten ded on dif ferent har dware and software c onfigurati ons, and u nder diffe rent condi tions (e.g ., a new i nstallatio n, an upgr ade, and a complete or custom installati on). Insta llation te sting may also measu re the eas e with whi ch an appl ication or system ca n be succe ssfully in stalled, t ypically m easured in terms of the averag e amount o f person-h ours requi red for a trained op erator or hardware e ngineer to perform t he install ation. Par t of this installati on test is to perfor m an unins tall. As a result of this unin stall, the system, a pplication and datab ase should return to the state prior to the instal l.
	1164	Integratio n Testing
	1165	An increme ntal serie s of tests of combin ations or sub-assemb lies of se lected com ponents in an overal l system. Integratio n testing is increme ntal in a successive ly larger and more c omplex com binations of compone nts tested in sequen ce, procee ding from the unit l evel (0% i ntegration ) to event ually the full syste m test (10 0% integra tion).
	1166	Load Testi ng
	1167	A performa nce test t hat subjec ts the sys tem to var ying workl oads in or der to mea sure and e valuate th e performa nce behavi ors and ab ilities of the syste m to conti nue to fun ction prop erly under these dif ferent wor kloads. Lo ad testing determine s and ensu res that t he system functions properly b eyond the expected m aximum wor kload. Add itionally, load test ing evalua tes the pe rformance characteri stics (e.g ., respons e times, t ransaction rates, an d other ti me-sensiti ve issues) .
	1168	Migration Testing
	1169	A type of testing th at follows standard VistA and HeV-VistA operating procedures and loads the lates t .jar ver sion onto a live cop y of VistA and HeV-V istA. The following are exampl es of the types of t ests that can be per formed as part of mi gration te sting:
	1170	Data conve rsion has been compl eted
	1171	Data table s are succ essfully c reated
	1172	Parallel t est for co nfirmation of data i ntegrity
	1173	Review out put report , before a nd after m igration, to confirm data inte grity
	1174	Run equiva lent proce ss, before and after migration
	1175	Multi-Divi sional Tes ting
	1176	A type of testing th at ensures that all applicatio ns will op erate in a multi-div ision or m ulti-site environmen t recogniz ing that a n enterpri se perspec tive while fully sup porting lo cal health care deli very.
	1177	Parallel T esting
	1178	The same i nternal pr ocesses ar e run on t he existin g system a nd the new system. T he existin g system i s consider ed the "go ld standar d", unless proven ot herwise. T he feedbac k (expecte d results, defined t ime limits , data ext racts, etc .) from pr ocesses fr om the new system ar e compared to the ex isting sys tem. Paral lel testin g is perfo rmed befor e the new system is put into a productio n environm ent.
	1179	Performanc e Monitori ng Testing
	1180	Performanc e profilin g assesses how a sys tem is spe nding its time and c onsuming r esources. This type of perform ance testi ng optimiz es the per formance o f a system by measur ing how mu ch time an d resource s the syst em is spen ding in ea ch functio n. These t ests ident ify perfor mance limi tations in the code and specif y which se ctions of the code w ould benef it most fr om optimiz ation work . The goal of perfor mance prof iling is t o optimize the featu re and app lication p erformance .
	1181	Performanc e Testing
	1182	Performanc e Testing assesses h ow a syste m is spend ing its ti me and con suming res ources. Pe rformance testing op timizes a system by measuring how much t ime and re sources th e system i s spending in each f unction. T hese tests identify performanc e limitati ons in the code and specify wh ich sectio ns of the code would benefit m ost from o ptimizatio n work. Pe rformance testing ma y be furth er refined by the us e of speci fic types of perform ance tests , such as, benchmark test, loa d test, st ress test, performan ce monitor ing test, and conten tion test.
	1183	Privacy Te sting
	1184	A type of testing th at ensures that (1) Veteran an d employee data are adequately protected and (2) s ystems and applicati ons comply with the Privacy an d Security Rule prov isions of the Health Insurance Portabili ty and Acc ountabilit y Act (HIP AA).
	1185	Product Co mponent Te sting
	1186	Product Co mponent Te sting (aka Unit Test ing) is th e internal technical and funct ional test ing of a m odule/comp onent of c ode. Produ ct Compone nt Testing verifies that the r equirement s defined in the det ail design specifica tion have been succe ssfully ap plied to t he module/ component under test .
	1187	Recovery T esting
	1188	A type of testing th at causes an applica tion or sy stem to fa il in a co ntrolled e nvironment . Recovery processes are invok ed while a n applicat ion or sys tem is mon itored. Re covery tes ting verif ies that a pplication or system , and data recovery is achieve d. Recover y Testing should be combined w ith Failov er Testing .
	1189	Regression Test
	1190	A type of testing th at validat es existin g function ality stil l performs as expect ed when ne w function ality is i ntroduced into the s ystem unde r test.
	1191	Risk Based Testing
	1192	A type of testing ba sed on a d efined lis t of proje ct risks. It is desi gned to ex plore and/ or uncover potential system fa ilures by using the list of ri sks to sel ect and pr ioritize t esting.
	1193	Section 50 8 Complian ce Testing
	1194	A type of test that (1) ensure s that per sons with disabiliti es have ac cess to an d are able to intera ct with gr aphical us er interfa ces and (2 ) verifies that the applicatio n or syste m meets th e specifie d Section 508 Compli ance stand ards.
	1195	Security T esting
	1196	A type of test that validates the securi ty require ments and to ensure readiness for the in dependent testing pe rformed by the Secur ity Assess ment Team as require d by the A ssessment and Author ization Pr ocess.
	1197	Smoke Test
	1198	A type of testing th at ensures that an a pplication or system is stable enough to enter tes ting in th e currentl y active t est phase. It is usu ally a sub set of the overall s et of test s, prefera bly automa ted, that touches pa rts of the system in at least a cursory way.
	1199	Stress Tes ting
	1200	A performa nce test i mplemented and execu ted to und erstand ho w a system fails due to condit ions at th e boundary , or outsi de of, the expected tolerances . This fai lure typic ally invol ves low re sources or competiti on for res ources. Lo w resource condition s reveal h ow the tar get-of-tes t fails th at is not apparent u nder norma l conditio ns. Other defects mi ght result from comp etition fo r shared r esources ( e.g., data base locks or networ k bandwidt h), althou gh some of these tes ts are usu ally addre ssed under functiona l and load testing. Stress Tes ting verif ies the ac ceptabilit y of the s ystems per formance b ehavior wh en abnorma l or extre me conditi ons are en countered (e.g., dim inished re sources or extremely high numb er of user s).
	1201	System Tes ting
	1202	System tes ting is th e testing of all par ts of an i ntegrated system, in cluding in terfaces t o external systems. Both funct ional and structural types of testing ar e performe d to verif y that the system pe rformance, operation , and func tionality are sound. End to en d testing with all i nterfacing systems i s the ulti mate versi on.
	1203	Usability Testing
	1204	Usability testing id entifies p roblems in the ease- of-use and ease-of-l earning of a product . Usabilit y tests ma y focus up on, and ar e not limi ted to: hu man factor s, aesthet ics, consi stency in the user i nterface, online and context-s ensitive h elp, wizar ds, and ag ents, user documenta tion.
	1205	User Funct ionality T est
	1206	User Funct ionality T est (UAT) is a type of Accepta nce Test t hat involv es end-use rs testing the funct ionality o f the appl ication us ing test d ata in a c ontrolled test envir onment.
	1207	User Inter face Testi ng
	1208	User-inter face (UI) testing ex ercises th e user int erfaces to ensure th at the int erfaces fo llow accep ted standa rds and me et require ments. Use r-interfac e testing is often r eferred to as GUI te sting. UI testing pr ovides too ls and ser vices for driving th e user int erface of an applica tion from a test.