In our previous blog post, we described how easy it is to connect to ngrok to allow Tenon to test your local environment. Today we’re going to add ngrok to the grunt-tenon-demo. Everything in this post is on Github and in the add-ngrok branch of the grunt-tenon-demo.
One of the most frequent questions we get is “How do I test my local environment?” We love this question, because it means that the user is venturing into Extreme Accessibility. Unfortunately, Tenon doesn’t have a way to connect to someone’s local environment. But you can do this with a service like ngrok. Lets’ walk through how do connect your local environment to ngrok and test with Tenon.
The best feature of an automated testing tool is also its worst: The ability to go through large amounts of code and find errors that don’t require a human to find. Using an automated tool you should be able to test hundreds of pages in a matter of minutes. Finding the average number of pages per site is difficult. Some old data suggests that the average number of pages is 273, whereas some newer data says the average site has many times more. But for simplicity’s sake, let’s assume you test 200 pages. Tenon finds an average of 51 errors per page. This means that if you scan 200 pages with an average of 51 errors per page, Tenon will find 10,200 errors. Holy cow!
Sample code for this post is available on Github: grunt-tenon-demo.
Actually, there’s not much that Tenon doesn’t integrate with. This is the entire point behind our “API First” philosophy. Our goal, in fact, is to continually seek ways to develop and demonstrate the full power of Tenon.