Simply Testable Updates #62: Share Private Test Results, Filter Results By Test Type, Towards Testing Absolutely Any Site
October 23, 2013
|You're receiving this email because you joined Simply Testable's updates list.
This is the 62nd of weekly progress updates on the development of Simply Testable, your professional automated web frontend testing service providing one-click testing for your entire site.
Highlights from the past week:
Share Private Test Results
share private test results
filtering results by test type
working towards testing absolutely any site
Your tests are private if you run tests when you are signed in. You then need to be signed in if you want to re-visit past test results.
This isn't too great if you want to share the results of your tests. You might want to share results with colleagues or with third parties, such as clients for whom you are offering web testing services.
You can now unlock private tests, allowing anyone within whom you share the results URL to view the results.
This new feature is covered in more detail in the announcement blog post.
Filtering Results By Test Type
The list of results you're staring at features a range of issues for a range of URLs.
Now you think about it, you only really wanted to figure out which pages contain broken links. You could run the test again and select only link integrity testing. But who wants to wait 10 minutes for that?
Let's see, you think, looking at the test results. CTRL-F, "link integrity". Chrome is now highlighting all occurrences of "link integrity" in the page, that should make things easier.
Scroll, scroll ... found one!, make a note of that. Scroll, scroll ... found another one! Make a note of that too. Scroll, scroll ...
Well, that's how you used to have to handle it. Hardly fun at all.
You can now filter results by test type. If the test you ran covered a range of checks, you can how show only the results that matter to you.
Did I mention you can share private test results? Did I mention you can filter results by test type? Here you go: here is both for a test I carried out whilst writing this.
Working Towards Testing Absolutely Any Site
When the service first launched you could only run full-site tests for sites with simple sitemaps.
There was a whole range of sites you couldn't test but it was better than nothing and allowed me to focus on building a great testing tool instead of building a great sitemap reading tool.
As the need to test a broader range of sites grew, I added support for:
With each change the subset of the Internet that could be tested grew a little. And along with each change came a new set of problems.
Sites that use indexed sitemaps and compressed sitemaps tend to do so because they have many, many, many URLs to list. I encountered a site this week that has 1396 compressed sitemaps each listing about 8,000 URLs. I can't even count that high with my limited ten fingers.
I've now applied a timeout across the entire operation of retrieving a sitemap for the purpose of collecting URLs to test.
If you're in the quite small subset of the Internet that has such large sitemaps that someone has to start using all their fingers and all their toes to count them you're in luck.
I'm also working on correctly identifying and rejecting tests for sites that can never be tested, specifically for sites that have unroutable domains and sites that have an unroutable IP in the URL such as http://127.0.0.1.
I'm currently working on the long-promised and so far not-delivered new test center (or test dashboard if you prefer). I've sorted out some UI issues that were concerning me regarding listing recent test and providing a full test history.
For this to work for the public user (under which all tests run if you are not signed in), I need to ensure that absolutely every single test that is started ends up finishing in one way or another, hence the above focus on ensuring that the entire Internet can be tested if needed.
As always, if you'd like to see web testing you find boring handled automatically for you, add a suggestion or vote up those that interest you. This really helps.
Feedback, thoughts or ideas: email email@example.com, follow @simplytestable or keep an eye on the Simply Testable blog.