Shipping of new features in an agile environment, fast and frequent releases have to be manually tested for multiple mobile devices
Choosing the appropriate technique helps to combine the fast, near-development tests with frequent and thorough regression tests
Improved decision making for management, increased confidence of releases
TWINT offers a mobile payment solution in Switzerland, with a free mobile application for end-customers, while merchants also enjoy better fee rates compared to regular solutions. They have now over 1.5 million registered users, for whom they offer quick mobile payments in shops, webshops, vending machines or at parking automats, easy access to donation options and participation in cashback campaigns.
We started to work with TWINT 2 years ago, with a team of an experienced test manager and three certified testers. Since then, we have tested 7 major releases, 15 minor releases and 14 releases of the frontend component.
The test manager plans all testing related activities, tracks the testing progress, and intervenes in case of deviations from the plan.
We write and maintain the test case documentation based on the existing requirements specifications; we also take care of preparing the test data so that we are able to execute the tests in the next phase.
The testers run the prepared test cases according to the test plan, on the defined test levels: this means detailed tests of new functionality, or regression test runs in order to ensure that each functionality, which was delivered in previous releases, still works as required after the integration of new additions to the software.
Our test manager prepares test reports to provide the necessary information for the project stakeholders (release management, product owners) about the quality level of the tested applications and informs them in a timely manner about project and product risks, together with proposed solutions for their mitigation.
Our team works as an integrated part of the whole project team of TWINT:
We are testing the whole TWINT ecosystem, which consists of 3 applications: native mobile applications on iOS and Android for the end-customers, a web application for TWINT’s own service desk and a web application for merchant self-registration and self-administration. We are also responsible for ensuring that the integration of these applications with the products or services of 3rd party vendors works correctly.
During a release, we cover the following test levels:
The TWINT project holds a special place in our hearts because of its focus on testing as a service: not being able to control the whole development process and being part of a distributed team brings very special challenges, which we embrace as new learning opportunities to be able to support our customers efficiently.