Getting started with test automation (CI) integration

We will be retiring Continuum for Protractor in October. If you have any questions or concerns, please reach out to your Customer Success Manager.

Our Test Automation integration will allow you to leverage our accessibility tests as part of your automated testing by evaluating work and sending the accessibility results into the platform, or by creating validation checks for accessibility while testing.

We currently support five major test automation platforms including:

• Cucumber
  • Cucumber and Cucumber JDK
• Jest
• Mocha
• Cypress
• Protractor

If you would like to learn more about getting started with our Test Automation feature, please request support for more information related to your testing platform of choice.

Best practices for automated testing

As you get started with automation testing in your development process, there are some good best practices to keep in mind while your teams adjust to account for accessibility. As some general notes, it’s important to remember that:

• Pushing results to the platform is easy – after you set up your integration, the platform will accept and store all results sent to it from your integration.
• Less is more – running too many scans of your platform will create an overwhelming number of results to review, so it is important to take a balanced approach when deciding what to push to the platform.

To help balance these two principles, we recommend the following as a place to get started:

• In the case where accessibility is integrated into general UI automation together with general regression, we recommend only sending specific runs/accessibility results into the platform.
• In cases where a separate accessibility-specific UI automation is implemented, we recommend establishing a regular cadence for your accessibility tests to be run.
• Regardless of your setup, the general best practice to push anywhere between 1 - 14 accessibility scans per week into the platform for review and analysis.