Simply Testable Updates #31: Staying Signed In, Backups In Place
March 13, 2013
|You're receiving this email because you joined Simply Testable's updates list.
This is the 31st of weekly progress updates on the development of Simply Testable, a brand new automated web frontend testing service providing one-click testing for your entire site.
Highlights from this week:
You can now stay signed in
The Simply Testable sign in form lacked, until recently, a 'stay signed in' option.
When account creation launched back on 9 November 2012, an option to stay signed in was intentionally not added. Adding such a feature required more work and with there at the time being no registered users there was no clear demand for this.
I noticed when building our backup tools that very few full-site tests were created by signed-in users. There are many possible reasons for this being the case and one of them is that users who had created an account were not signing in when returning to run further tests.
There aren't yet any particular benefits to signing in since you can run tests just as well if you are not signed in. That will be changing over the next few months when different levels of accounts and paid plans are introduced.
Now seemed like a good time to quickly add in a 'stay signed in' option.
Core application backups are in place
I mentioned last week that core application backups were mostly working.
This work is now complete, the core application has been upgraded and hourly database backups are now being created, stored on the production server and copied to a remote backup server.
At present there is nothing to stop the database contents changing whilst a backup is being created and there is a chance that not 100% of the data in the backup can be restored.
I'm continuing to work on a means of putting the whole Simply Testable system into a read-only state to ensure that database contents don't change whilst backups are being made.
It's possible at the moment to put the core application into a read-only state. I'm now working on changes to the web interface and the worker applications to ensure that once the core application resumes from a read-only state all operations return to normal.
I hope to have these changes completed over the next two weeks. These are significant changes but are worth putting in place now as they will be of use not only when creating backups but also to better manage the service
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.