User Acceptance Testing

For the past weeks, I have been writing a lot about the tools we use here at Optimus in order to create great mobile applications. Continuing with this trend it is time to check how we perform acceptance testing.

Acceptance testing is a type of testing that happens once all of the code for a given sprint has been finished and this code has passed through our testers, these are the last two steps before we signoff on the build. Here at Optimus happens this type of testing happens in two stages:

  • First the internal product owner (normally a business analyst) performs the testing as if he were the customer. The product owner performs the search in two ways: he first goes over the acceptance criteria that were agreed upon and then a free test is performed where the owner just uses the application as if he were a normal user.
  • After the product owner accepts the build then it is passed on to the customer to perform user acceptance testing and the close the sprint.

Performing this type of testing can be tricky, mainly because it takes quite a bit of time and effort to deploy the builds to different devices in different platforms.
Here at Optimus, because of differences between the platforms (iOS, Android and Windows Phone) we have a different process for each.

  • iOS: For iOS apps we use a great SaaS for application testing through the cloud: TestFlight. This application allows us to send the build to different devices in many parts of the world. We can see how they look in iPads, iPhone 4, iPhone 5, iPod Touches and other iOS devices very easily. All we do is download the TestFlight app in these devices, sign these devices up with TestFlight and, once a build is ready, directly download it from the Testflight app to our device. TetsFlight is great because we can deploy the application to as many devices as we want.
  • Android: For Android what we do is to directly download the .APK file to the phone, this automatically installs the application in our device, but this has to be done manually for each device.
  • Windows: For Windows it is the biggest hassle; there are several steps that need to be taken. First of all you have to have Windows developer tools in your machine as well as have Zune software. You also have to register your device before you can download the application to the device.

As you can see three are very different and for sure the easiest one is iOS through TestFlight.

We look forward to make this acceptance testing process more streamlined with the announced addition of Android and Windows support by TestFlight. This will allow us to spend less time setting tests up and devote more time to testing.

If you have any questions about user acceptance testing or any other aspect of mobile app development, please don’t hesitate to contact us and take advantage of our one hour free consultation.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *