What is the Canvas beta environment?

Document created by jivedocs@instructure.com Employee on Jun 13, 2018Last modified by Erin Hallmark on Aug 19, 2019
Version 2Show Document
  • View in full screen mode

    Official Canvas Document

Canvas white logo

 

 

What is the Canvas beta environment?

Canvas beta is a working environment offered as a complimentary service by Instructure. The beta environment is for testing and QA review before code is released to the production environment; it is refreshed every week to display the same content in the production environment. New code can be introduced to the beta environment at any time.

 

The beta environment is separate from the Canvas test environment, which is used for testing all aspects of Canvas, especially user data.

 

Why should I use the beta environment?

The beta environment can be used to test new and updated features before they are released to the production environment. Use of this environment is optional, and feature testing is not mandatory. All available functionality is described in the Canvas Release Notes. However, the beta environment can be used to anticipate any problems that may occur before the production release, especially if an institution is using custom applications, cascading style sheets (CSS), or JavaScript (JS).

 

Not all functionality is supported in the beta environment and some features, specifically LTI tools, may still use production data. Therefore, content can be affected even if the feature or tool is accessed from the beta environment.

 

What should I expect in the beta environment?

Our Canvas development teams are constantly developing Canvas and committing changes to our master code base. That master code base includes thousands of automated tests that execute every time a developer commits new code. The Canvas beta environment is a working environment that receives a copy of the master code base every two weeks as part of the Canvas Deploys

 

The beta environment is a working environment used by Canvas engineers to confirm and ensure performance and feature accuracy, prepare for upcoming features, resolve bugs, and perform backend maintenance. Other changes can be added to the beta environment at any time, such as to resolve new behaviors currently in the code. Although significant testing has been completed in the master environment, the beta environment is primarily designed to catch any contrary behaviors before they reach the production environment.

 

How do I access the beta environment?

Canvas admins and instructors can access the beta environment by adding beta in their Canvas URL (e.g. yourinstitution.beta.instructure.com). Learn how to access the environment directly as noted in the Canvas guide for each user role:

 

How do I find out about changes in the beta environment?

New and updated functionality that affects user workflows is included in the code base every two weeks but is not functionally enabled until the release date indicated in the Canvas Releases page. Learn more about the release schedule in What is the Canvas release schedule for beta, production, and test environments?

 

Notable changes to the beta environment that are part of the scheduled two-week deploys are indicated in the Canvas Deploys page.

 

What limitations are in the beta environment?

The beta environment is managed by the same engineers who manage the production and test environments. While the beta environment is an important resource to our customers, the beta environment does not include any service-level agreements (SLAs) for fixes or feature updates. Additionally, status updates and incident reports are not provided for any disruptions that occur.

 

The beta environment includes certain limitations as noted in the Canvas guide for each user role:

 

What happens to my content in the beta environment?

The beta environment is refreshed weekly. Any content added to or modified in the beta environment will be overwritten by content in the production environment every Saturday. Beta is not available for use when the environment is being refreshed.

1 person found this helpful

Attachments

    Outcomes