Just wanted to share a quick 2-minute example of Tenon testing itself (original video, sped up 2.5x)
Tenon uses Webdriver.io and Mocha/ Chai/ Should to perform end-to-end testing of every possible user interaction on the Tenon.io website. Along the way, it also performs accessibility testing. First, it tests general page templates – navigation, header, and footer for 3 distinct layouts. Then, it goes through the user interactions and tests only the distinct portions of the page(s) that it hasn’t tested before.
As the video progresses, you’ll see the testing occur on the left side of the screen. On the right side of the screen you’ll see the production version of the Tenon.io. That view features the “card” for the project into which we submit the tests as the total number of test runs and number of issues is incremented accordingly.
This type of testing is extremely powerful, especially at scale. It allows for you to integrate accessibility testing into your normal QA automation without treating it as a separate process.
This video has no sound.