Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Communicate with testers and demo site committers about timing of upcoming release.
  • Ensure the Managers Guide, UI Interactions, Test Tracking Spreadsheet and demo site are up to date for the process of testing and documentation.
  • Recruit help with testing, bug reporting and documentation. 
  • Ensure testing and documentation is complete. 


This testing process complements test coverage and regression testing in the code but does not replace it. This testing is meant to facilitate browser, platform, feature, (basic) usability and completion, and accessibility. 

Major release process:

Beta Release: All major features are complete. 2-3 weeks

  • Beta release on demo site

  • Basic testing for major problems and release completeness.

  • Beta release is announced

  • First draft of documentation is done

  • First round of testing and bug reporting begins

  • Institutions have a chance to report bugs or ask for a PR to be considered for inclusion in release

...

  • Once Final Release is ready, at least 1 in-production institutions should upgrade before wide release (This may not be doable, but would be good if there are institutions willing to do this, could rotate and plan ahead to help curb)

  • Final Release is announced widely

Minor release process: 

  • Follows the Major release process on a much more compressed timeline.

  • Upgrade demo site, retaining data. In the occasion that data needs to be wiped for whatever reason, this is fine. Mostly we want to test that data and users migrate smoothly.  

...