The stability of our application is one of our main priorities. What actions have we taken and where are we going? Read more here.
At Adfinity, quality and customer satisfaction have always been priorities. Especially in recent years, the growth of our users and our teams in this area has enabled us to make a big leap forward and set many new processes in motion for the stability of the application. Which and with which results?
In all phases from development to the implementation of the solution at our customers, your satisfaction is our top priority. That is why we do our utmost to provide you with a high-quality product that is as stable as possible.
Stability and innovation, an essential balance
In the world of application development we generally see two schools:
- advancing the product as much as possible by bringing new functionalities at the expense of stability
- slowing down the functional evolution of the product in order to eventually reduce the number of bugs and thus have a more stable application
As you know, we at EASI don't like concessions! Why not an innovative AND stable product?
Ensuring this balance is the challenge of the quality team. How do we do that?
A test team for a zero-bug objective
An official Adfinity quality team has been in place since 2018.
One of the most important tasks is to test the application and make sure there are no bugs when the version is installed with you.
The visible part of the iceberg is the validation of new major releases to ensure that new developments and historical behavior of the application integrate well. So for a full month there are two people dedicated to this. It is also an intense period for the development team that guarantees continuous adjustments to ensure the follow-up of the points.
However, quality is not only about this test "sprints". It is a long-term plan, and from now on, every new development is therefore validated for the "official" test phases: technically by a product manager of the development team and qualitatively by the quality team.
These two complementary visions ensure that the development fits well with the analysis, that it is technically and functionally efficient.
From a test point of view alone, for our last major release (1.5), this was the equivalent of 17% of the time spent on development, i.e. more than a hundred days.
How does the quality team work?
We have systematically built up and elaborated test scenarios for the usual processes of the application.
We validate with "levels" during the official validation phase, i.e. we first check the basic flows used by the majority of our users. Then we increase the complexity of the tested cases.
These tests constantly evolve and complement each other in order, for example, to integrate the new functions of the previous version.
We also carry out our tests on various databases in order to adapt to the specific characteristics of each sector.
How do you measure the effect on saturation?
Parallel to the tests, the quality team monitors satisfaction with the different solutions we propose. For example, in 2018/2019, we already carried out satisfaction audits among our cloud and OCR customers. Based on the results, we have taken the necessary actions and monitored the evolution to ensure an improvement of the situation.
What about 2020?
We expect 3 major releases in 2020. We have already set aside more time for the official validation, but also for upstream testing of new features. In total, the budget for quality has almost doubled for 2020!
We are planning a lot of new features, but we are not afraid of this because we have strengthened our processes within the development and testing team to ensure the stability of our next releases.
If you would like to know more about our way of testing you can always contact your consultant.