What is your quality assurance process for new releases?

This article has moved to our new Help Center and will no longer be updated on this page. Please see the Help Center for the newest version.

For every new version of SpiderOak that we consider releasing, even if it only includes a very basic change from the last version, our policy includes comprehensive testing on all supported platforms and configurations. Testing is performed both by humans and machines.

We've created an extensive automated simulation and testing environment which continuously stresses the software in the most grueling ways we can build, with across-the-board integrity verification at each step.

Most releases are continuously stressed for at least 24 hours before being pushed out for general distribution.

We also occasionally have beta releases of SpiderOak available to beta testers before a general release. If you're interested, you can read our release notes and contact us about becoming a beta tester.