For configuring E-Commerce to talk to the LMS, you'll need to use a fully qualified domain name or IP address assigned to your machine. In this case, assuming we're using a machine with the IP address of 192.168.33.10.
Review the release notes, configuration changelog, and automatic upgrade scripts and determine if any configuration variables need to be updated etc.
Deploy a new single-VM instance from scratch using the new release candidate and validate it (see below).
Deploy a new multi-VM instance from scratch using the new release candidate and validate it (see below).
Deploy/use a single-VM instance from the previous release, then change its branch to use the new release candidate, deploy the upgrade, and then validate it
Deploy/use a multi-VM instance from the previous release, then change its branch to use the new release candidate, deploy the upgrade, and then validate it
Validation procedure for each deployment:
This manual testing procedure is designed to cover some of the more common failure modes / deployment errors encountered:
Make sure user registration works.
Make sure you received the activation email. If using an external SMTP server (e.g. SES), verify that the email was actually sent via that external service and not directly from the EC2 instance.
Make sure that the activation link in the email works.
Make sure course creation works.
Log into the studio and create a new course.
Add a new unit to the course.
Make sure the "Preview" link works correctly.
Test course in the LMS.
Log into the LMS as a staff user.
Click through each of the tabs ("Home", "Course", "Discussion", ...) to make sure the section loads correctly.
Go to the "Course" tab and make sure the "View unit in Studio" link works correctly.
Go to the "Discussion" tab and submit a new post, and add an image. Make sure the image is uploaded to S3/ObjectStorage successfully, and is displayed in the post correctly.
Go to the "Instructor" tab and select "Data Downloads" section. Click the "Download profile information as a CSV" button and wait until the report is generated. Make sure the link to the report works correctly.
Make sure tracking logs are being synced to S3 (We always want to sync tracking logs even if the instance is not currently using analytics. Note that tracking logs don't rotate until they're larger than 1Mb.)
If using Insights: make sure link from "Instructor" tab points to Insights correctly and make sure that OAuth between LMS and Insights works.
If using a custom theme:
Make sure the theme looks ok in general.
Pay special attention to discussion forums and the wiki (they are using different layouts).