1 / 6

Workflow Diagrams

Workflow Diagrams. Code Submission and Testing Process. Code Submission – Bug Fix. Developer. User Develops Code. Bug Fix or Incremental Change. Submit to Gerrit. OSEHRA. OSEHRA Review (1). OSEHRA Gold (3). Notify VA. VA. VA Review (2). Notify OSEHRA. VA Gold (4).

marieortiz
Download Presentation

Workflow Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workflow Diagrams Code Submission and Testing Process

  2. Code Submission – Bug Fix Developer User Develops Code Bug Fix or Incremental Change Submit to Gerrit OSEHRA OSEHRA Review (1) OSEHRA Gold (3) Notify VA VA VA Review (2) Notify OSEHRA VA Gold (4) • 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.

  3. Code Submission – New Capability Developer User Develops Code New Capability Submit to OTJ OSEHRA OSEHRA Review (1) OSEHRA Gold (3) Notify VA VA VA Review (2) Notify OSEHRA VA Gold (4) • 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.

  4. Nightly Testing/Dashboard Developer Automatic From Cron Script Automatic From Cron Script Automatic From Cron Script Nightly Process (1) Nightly Process (1) Download Test Harness Download Test Harness Adapt Script/Setup Cron Adapt Script/Setup Cron Update Test Harness Update Test Harness Update VistA Code Update VistA Code Execute Nightly Tests Execute Nightly Tests Submit to Dashboard (2) Submit to Dashboard (2) Display Results Nightly Process (1) Download Test Harness Adapt Script/Setup Cron Update Test Harness Update VistA Code Execute Nightly Tests Submit to Dashboard (2) OSEHRA VA • Process for Nightly Regression/Unit Tests. • The test engine automatically uploads to the dashboard on completion of the tests. No additional user action is required.

  5. Experimental Testing/Dashboard Developer Download Test Harness Download Test Harness Download Test Harness Submit to Dashboard (3) Submit to Dashboard (3) Submit to Dashboard (3) Experimental Process (1) Download VistA Code Apply Changes (2) Upload to Caché / GT.M Execute Tests Experimental Process (1) Experimental Process (1) Download VistA Code Download VistA Code Apply Changes (2) Apply Changes (2) Upload to Caché / GT.M Upload to Caché / GT.M Execute Tests Execute Tests OSEHRA Display Results VA • 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.

  6. VA Intake Developer Code Submitted Additional Artifacts OSEHRA OSEHRA Certifies VA Notified VA (1) Discard Request Additional Effort (2) Interest? Sufficient Artifacts? VA Certifies? Notify OSEHRA VA Initial Evaluation • 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.

More Related