So Google has acquired Appurify? It is not enough

01/07/2014

So, Google has bought a testing company.

This is great news as we have long been saying that it’s not a very good idea to use your users as basic level (or beta release level for that matter) testing platform.

Users these days need a tested product in the market, or they will just delete your app, demand a refund and give you the dreaded no star review.  The excellent article in SD Time by Josh Galde makes that very clear.

But what does it mean that Appurify has joined Google?

It means that the Android App development process has another really useful step in it.  The Appurify Mobile Platform adds the ability to functionally test your app on a range of real devices ‘in the cloud’.  AQuA has always held firm on the need for testing on real devices so that is great.

It allows the developer to script and replay tests across a range of devices and that covers a strong element of compatibility testing.  Again this is great, and is a service that’s also available from a number of other vendors – AQuA endorsed testing service Keynote for example – and if Google includes the tool within its developer suite, then we should see fewer blatant app/device compatibility failures.

However, it isn’t the whole story, and isn’t enough!

A good Quality app comes from a process of good quality assurance, backed up by structured testing that includes functional testing, device compatibility testing, UI testing, non-functional testing, performance testing and basic testing that the app behaves well on the device.

Whist we welcome the use of the ‘real device in the cloud’ testing, we encourage developers to refer to the AQuA Best Practice Guidelines and also test their app against the AQuA Testing Criteria - both of which are free to everyone via the AQuA website – which will help them get a fully rounded QA process to deliver a great quality app.

› back