Code Testing

Together with developing a code change it is essential that we have a test plan that covers the changes made and verifies that any adjacent critical functionality continues to work as expected. It may be helpful to develop the test plan first before making the changes to help guide the software development.

The test plan should be reviewed along with the code changes before implementation to ensure that it adequately exercises all the affected code paths. The test plan review should include peers in the EE group and others that may have familiarity with the affected functions.

As much as possible, the test plan should be straightforward to perform, with explicit instructions and expected results clearly spelled out. Here is a template for test plans which may be useful to copy for a starting point: https://docs.google.com/document/d/18VeAjxynjoBEqpQTyLvCGH3y3jCmbsA63jXR2f5l1pw/edit?usp=sharing

Once the changes have been implemented and the test plan has passed, scan the completed test plan and attach the scan to the primary Jira ticket.