Research and preparation
The company’s objective was to deliver an exceptional customer experience through a companion app. TTT Studios met with EMV’s stakeholders to better understand its potential users and the trends in the broader industry. A competitor analysis of similar vehicle applications was conducted based on decision criteria. During this exercise, TTT not only identified a core set of features to give EMV a competitive advantage, but also built with scalability top-of-mind.
Discovery sessions are an integral part of our process. Working with our clients, we use this time to identify the business goals, understand user needs and expectations, and co-create an action plan to execute on the client’s vision. Over the course of two days and using the information gathered during our research and project preparation, we held a series of workshops with EMV to define the project’s product vision, personas, and user journeys.
We conduct user testing to objectively assess the software and validate its Information Architecture, Information Flow, User Experience, and Interface Design.
Using lookback.io, we ran EMV’s testing participants through two scenarios for the mobile app and five for the web admin. The results of the mobile test were overwhelmingly positive and we achieved an average ease of use score of 4.2 out of 5. The app features were streamlined based on the test user’s recommendations and feedback. Similar to mobile testing, web admin testing was successful, resulting in a satisfaction score of 5/5.
On top of the end-to-end manual functional testing, an open-source test automation framework called Appium was used to carry out the automated testing for the mobile application. This tool is easy to set up with our existing toolbox. TTT has adopted tools like Appium, Experitest, and eclipse to push the boundaries of what we can achieve for our clients and continuously optimize our processes. Our written JAVA test scripts act like a “robot” to mimic human behaviour, which allows us to check if the code tested generated a server response. This testing method not only expedited the QA process, but ensured every possible scenario was tested consistently and reliably.