Develop a beta

Date adopted: 
July 18, 2019
Last update: 
August 17, 2020

When we're developing a beta, we're looking to accomplish the following.

Accessibility

Your testing plan should include assisted digital routes. Through your testing, you should be able to:

  • show how the service or website has evolved to meet the requirements for people with a variety of abilities in a variety of environments;
  • identify non-digital access and support for users who can't access the digital service;
  • demonstrate you've completed end-to-end testing on any assisted journey options you include; and
  • identify accessibility barriers and have a plan to address them.

Content migration

Once the service or website is in UAT, you can begin adding your content in both languages.

French language translation

Your content should be finalized and going through the translation process according to your project translation plan. We recommend you have most content translated and included in UAT so you can test to confirm it works.

Produce beta service or website

The version you build must be able to handle real transactions and work at scale. You also need to keep improving your service, replace existing services and integrate with internal systems.

User Acceptance Testing (UAT)

The project team will test the service or website in UAT. This is your opportunity to ensure the features work as intended.

Vendor demo(s)

The number of demos will depend on the scale of the project and your timeline. The vendor should walk the project team through the service or website to demonstrate the features are working as expected.