Today, we released a completely redesigned version of our website. We’re exited about it because we think it better shows off the great features we have to offer. Be sure to check the new testCloud out!
Now we’d like to take a minute and talk about the process up to and before the launch, because we think its pretty insightful as to how effective crowd software testing can be.
So, the run up is basically this, we built a static site in Middleman, using Twitter Bootstrap v3, which was all in all a great experience. Where necessary, we just interfaced via CORS to our backend app for things like customer sign-up and the free trials. We worked and tweaked, localized it for our German version, fixed display bugs, and got it to a point we were happy with.
Okay, at this point, most developers would probably launch it right? I mean, we weren’t seeing any bugs in our browsers, our tests were running fine, but we didn’t launch, instead we ran a crowd test on our platform, something we always do for larger features.
And the results were amazing. We were able to fix a plethora of display bugs in browsers, resolve obscure CORS errors in Firefox, translate missing translations or messed up localized keys on obscure pages, and fix it all before the launch. Now, as a developer you definitely have a better feeling on deployment. Now you know your localization is good even on that obscure back page, and that sign-up is still working even for users on some outdated browser.
This is the power of crowd testing. Give us a try and let it do the same for you!