Hello to the whole community!
With the team Mr Suricatewe wanted to feed a blog with articles about testing and automation, e-commerce and anything else we find relevant to share with you.
On my side, I have decided to take my digital pen to write, in the next months, some of these articles: between humor or humour posts, blog reviews, surveys and feedbacks, I will do everything to make my interest in testing and automation as exciting as possible.
But who am I?
Let's start by introducing myself:
Michael Granier, Suricate since May 2020 after having progressed 12 years in the voyages-sncf.com, oui.sncf, e-voyageur technologies teams (and congratulations to the advent of SNCF Connect & Tech and the new version of the site) in the fields of testing and quality!
Certified ISTQB level 2 Test Manager specialization, passionate about technology and especially test automation, I participate as a spectator, speaker or facilitator in JFTL and various test clubs (when the health context allows of course...)
The Granier tester ?
For those who have the reference, this is a nice qualification we share internally for my blog posts 😉
Fabien has even planned to find me a nice flowered shirt to make it look more real than real.
Feel free to comment if you absolutely want to see me wear it and keep this nickname for the
next articles (or to spare me :D)!
The test, a strategic choice!
Let's start with an introduction to testing and quality.
In 2022, product quality is no longer an option.
But what is poor product quality?
The first thing that often comes to mind is the business loss that a production incident can cause to your company's turnover.
Even if this is the first indicator that makes people react in high places, you should not neglect the important impact on the end user, and that will strongly affect your e-reputation, much more complex to recover than a financial loss.
The latter, very easily and regularly damaged since the advent of social networks, is a very important indicator for Internet users, regular or future customers.
Anomalies, whether functional or not, are very often linked to a flaw in the validation cycle before release.
One solution: invest in a test strategy adapted to your context that will take into account all its aspects, functional or not, and that will allow you to implement the right types of tests at the right place, from the code to the interface!
The objective of a test strategy is above all to place the right tests in the right place to measure the quality of your application in order to detect flaws and defects to be corrected, and this, at the right time, that is to say, of course, before going into production...
This avoids turning an anomaly into a fatal incident that will provoke the ire of the Internet against you (Burn the witch!!).
A whole balance to put in place
And yet, the test in a project budget is still regularly seen as a cost center that is given priority, because it is difficult to quantify its concrete gains...
Sadly, the last wheel of the carriage on which it is sometimes obvious to cut back, to the great displeasure of the teams... and of the future customers.
However, it is quick, simple, but very inadvisable (believe me) to see the costs of non-quality of your product if no testing is put in place.
Quality and testing are intrinsically linked: testing is essential to measure quality and, logically, to implement the best practices necessary to improve it.
Attention, doing quality is not doing testing, it is a general state of mind that must be established in the project team 😉
And we must also be careful not to fall into the opposite trap, called over-quality, by performing too many tests.
There is a balance to be set up to have an optimal return on investment, including in the validation of your applications.
Once this strategy is in place, it will be time to couple it with an effective automation strategy, which will then allow you to deploy in production with a product of controlled quality, and to meet another need: validate and deliver faster and more often in production !
We will naturally talk about automation in a future article!
Stay Tuned...
