Skip to end of metadata
Go to start of metadata

Overview

Any change to the Rice data layer that requires a database alteration (i.e. table change, new foreign key, incex, etc), needs to be tested properly. This document describes how to do that.

Note: Database Changes cannot be made to patch releases (i.e. 2.0.1, 2.0.2) because patch releases are designed to be drop-in replacements for the minor version and contain only bug fixes.

Making the Database Change

Please follow these instructions: Making Database and Bootstrap Data Changes

Unit Tests

A contributing developer would need to write proper unit tests to exercise their change(s).

Once again, please follow these instructions: Making Database and Bootstrap Data Changes, making sure to validate your unit test(s) against all of the proper environments as described in the "Migrating Through Environments and Testing From the App" section.

Sample App and Web Tests

As outlined in the Rice Contribution Policies, it is recommended that a developer validates any web changes in the sample application. Once again, please follow these instructions: Making Database and Bootstrap Data Changes, making sure to validate your functional and web test(s) against all of the proper environments as described in the "Migrating Through Environments and Testing From the App" section.

  • No labels