Presentation on theme: "Workflow Diagrams Code Submission and Testing Process."— Presentation transcript:
Workflow Diagrams Code Submission and Testing Process
Code Submission Process User Develops Code Sub- mission Type Submit to Gerrit Submit to OTJ OSEHRA Gold (3) OSEHRA Review (1) VA Review (2) VA Gold (4) VA Review (2) OSEHRA Review (1) Bug Fix or Incremental Change New Module or Additional Capability (1)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. (2)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. (3)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. (4)VA gold as defined by/maintained by VA.
Automatic From Cron Script Submit to Dashboard (4) Testing/Dashboard Submission Nightly Process (1) Download Test Harness (1)Process for Nightly Regression/Unit Tests. (2)Process for verification of changes either as a developer or during review. (3)Changes may be downloaded from Gerrit, the OTJ, or be made as part of ongoing development. (4)The test engine automatically uploads to the dashboard on completion of the tests. No additional user action is required. Adapt Script/Set up Cron Update Test Harness Update VistA Code Execute Nightly Tests Experimental Process (2) Download Test Harness Download VistA Code Apply Changes (3) Upload to Caché / GT.M Execute Tests
VA Intake Process (1) Sufficien t Artifacts ? Interest ? VA Intake OSEHRA Certifies VA Notified (1)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. (2) “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. VA Initial Evaluation Discard Code Submitted VA Certifies ? Request Additional Effort (2) Notify OSEHRA