Transcript Testing and intake process

Workflow Diagrams
Code Submission and Testing Process
Code Submission Process
Bug Fix or
Incremental
Change
User
Develops
Code
(2)
(3)
(4)
VA
Review
(2)
OSEHRA
Review
(1)
Submission
Type
New
Module or
Additional
Capability
(1)
Submit to
Gerrit
OSEHRA
Gold (3)
Submit to
OTJ
OSEHRA
Review
(1)
VA Gold
(4)
VA
Review
(2)
Reviewer is required to download code/tests, execute tests and evaluate the code. Referral is either back to Gerrit for additional
modifications/abandonment or for acceptance. OSEHRA review may include manual functional testing.
VA certification process as defined by VA. Two types of feedback can come out of the VA process – Bug Fixes which require recertification
by OSEHRA, and requests for additional artifacts such as BRDs, ICRs, Requirements Documents, Test Plans, etc.
OSEHRA gold version may need to be separate from VA gold unless we can identify a mechanism whereby the VA can accept code outside
its area of interest such as pediatrics packages, open source versions of redacted code, etc.
VA gold as defined by/maintained by VA.
Testing/Dashboard Submission
Automatic From Cron Script
Nightly
Process
(1)
Download
Test
Harness
Adapt
Script/Set
up Cron
Update
Test
Harness
Update
VistA Code
Execute
Nightly
Tests
Submit to
Dashboard
(4)
Experimental
Process (2)
(1)
(2)
(3)
(4)
Download
Test
Harness
Download
VistA Code
Apply
Changes
(3)
Upload to
Caché /
GT.M
Execute
Tests
Process for Nightly Regression/Unit Tests.
Process for verification of changes either as a developer or during review.
Changes may be downloaded from Gerrit, the OTJ, or be made as part of ongoing development.
The test engine automatically uploads to the dashboard on completion of the tests. No additional user action is required.
VA Intake
VA Intake Process (1)
Code
Submitted
OSEHRA
Certifies
VA Notified
VA Initial
Evaluation
Request
Additional
Effort (2)
Interest
?
Discard
(1)
(2)
Sufficien
t
Artifacts
?
VA
Certifies
?
Notify
OSEHRA
This is our understanding of the process as the VA intends to implement it based on our discussions with VA developers. We will need to
adapt to whatever process the VA implement.
“Additional Effort” can either be a request for additional artifacts (BRD, ICRs, Requirements Documents, Testing), a notice of a bug, or a
request for additional development prior to acceptance. Artifact requests do not require additional OSEHRA effort other than potentially a
cursory review. Code changes will require eventual recertification by OSEHRA; although, that can follow formal acceptance of the changes
by the VA.