Simply Testable Updates #113: We're Profitable(!), Pre-Beta New Test Results, Currency In Transactional Emails
Feburary 18, 2015
|This is the online archive for the Simply Testable weekly behind-the-scenes newsletter.
Subscribe to get weekly updates on the latest changes and the newest planned features.
This is the 113th 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.
It's Been a While
It has been about 3 months since the last weekly updates newsletter. I halted development for a while to focus on issues outside of work, most of which related to rennovating a home that I purchased on October 25.
The service has been ticking over nicely and I've kept an eye on things. Nothing broke, most likely due to the system stability improvements released at the end of September and the performance re-working deployed towards the middle of October.
Weekly updates emails are back from now onwards.
We're Profitable (Yay!)
In the last few weeks, I successfully signed up a new enterprise customer which took us over the line into profitability. We're by no means living in luxury and taking ridiculous salaries, but our revenues do now cover server and software licensing costs.
Pre-Beta New Test Results
I'm continusing work on making test results more relevant and more easy to navigate. These changes aim to tackle a number of issues with the current presentation of test results.
I recently deployed changes introducing per-task-type reports.
Whereas test results are currently a list of error and warning counts by URL, the new per-task-type reports present results specific to a task type (such as HTML validation or CSS validation) and can be viewed from a by-error perspective (a list of errors and the pages on which they are found) or from a by-page perspective (a list of pages and the errors on each page).
These new reports help you focus on specific site-wide issues you may be looking to address. Taking HTML validation as an example, you can now easily find all pages across a site that contain images that lack an alt attribute. Or taking broken link checking as an example, you can now easily find all pages across a site that contain links that result in a 404.
These new per-task-type reports are in a pre-beta stage. They have been released live as they introduce no changes to any current pages and aren't linked to from anywhere. If you know how to find the new reports you can play around with them, although be aware that things are likely to change regularly over the coming weeks.
If you want to view the per-task-type results for a given test right now, you can do so by entering in the appropriate URL manually (pre-beta, remember?).
Append (in the correct form) the task type to the end of the current main test results URL path. For example, if your test results were at https://gears.simplytestable.com/http://example.com//1/results/, you can view the per-task-type reports by appending to the URL html+validation, css+validation, js+static+analysis or link+integrity (https://gears.simplytestable.com/http://example.com//1/results/_html+validation).
Currency In Transactional Emails
If you opt for a custom enterprise plan, we will bill you in whichever currency you prefer. After all, if you're paying us extra for a custom plan, why wouldn't we?
Until recently, currency values in transactional emails (invoices, payment succeeded confirmations) were hard-coded to UK pounds (GBP, £).
This initially made sense as all of our standard premium plans are billed in GBP. That was until our most recent enterprise customer opted to be billed in US dollars.
If you're one of our enterprise customers who has a custom plan not billed in GBP, you'll now see pricing values presented in the correct currency. Phew.
I'm continuing work on providing more clear test results. This is part of a larger project to not only present more clear test results but also to make it easier to find what you need in test results. This will lead on to being able to provide an analysis of results at the site level not just the page level.
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.