Hi all,
We're new to Canvas (this is our pilot semester right now, and this is my first question to the community, so we're really, really new). So far, things are going along relatively smoothly, but as with any transition, some things are a bit perplexing.
Today's bewilderment is deeply troubling, though. In short, I can't replicate the experience of the vast majority of our users (students) in the test environment, and I'm scratching my head to figure out why.
We want to ensure that our end users don't encounter any unexpected issues when an update is applied to the production environment. If they are going to see something new, different, or strange, we want to know about it beforehand and be prepared to respond. To that end, prior to an update's release, we go into our test environment and perform full testing on the updated components using all available account and course roles. This way, we know, for example, that Component X will cause students running Browser Y on Operating System Z to receive an error, and are prepared to advise students of possible solutions.
Well.... that was our practice...
But the Canvas environment is not configured to allow this.
Are we just expected to trust that everything will be okay or is there some special thing we need to do to enable this option?
Please tell me that there's a way to do this and that I'm being dense and haven't just not figured it out yet.
Thanks,
Rodney Hargis
Princeton University
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.