Qa anatomy, or fully charged package of quality
- AK
- Feb 19, 2018
- 3 min read
Imagine chaos around you. One day you go to work, and after arriving you write 2 lines of code, drink a cup of coffee, have a small morning-talk with your table-neighbor and push your small changes to production without notifying QA member. It’s only 2 lines, there is no risk…By the way your friend already did a “mandatory” code review for you at the same time as telling you about yesterday’s cool party in the new bar close to the office. 1 hour later you hear people in the corridor saying “something is wrong, it looks like we need to do a rollback,” but you don’t pay any attention because you haven’t made any changes to your product recently.
(2 lines couldn’t possibly count — it’s not serious)…
Let’s switch our focus to another place.
The purpose of this story is not to blame a developer for pushing something without QA (though it’s possible to continue the discussion in a “who fucked up production” direction).
This is a small story about the “anatomy” of the QA guild.
Who they are ? What do they do? When should we call them for testing ?
Do not leave anyone without a role for testing the application quality.
The strategy for testing : from day one until the launch, all the people that are involved with the project should test it. It’s a collaborative process.
As a test Engineer I try to get in early in the project. Then it’s possible to provide early feedback to the back-end and front-end developers.
How do you define the role of QA people in the team?
These are the people that are going to give a clear perspective to the developers when they need accurate and critical feedback. They will deliver this information throughout the team, at the right time, to the right person, with the right description and guidance.
Test Engineers are a “must-have” — not “nice-to-have” — part of the team if you want to deliver a quality product.
They have their methods, and they use all kinds of different tools. People in the world of quality do functional or explanatory tests to verify end-to-end scenarios that the users of the product will go through. Test engineers have to write down individual flows and procedures and test them thoroughly during the lifetime of the product. They have to test on different operating systems, different screens, and various devices. It is a painful process, but necessary.
That’s why I am aware of sites with worldwide web statistics.
Do you know that two-thirds of the global population are now mobile subscribers, and that mobile has greater reach than any other technology*? The 5 billion mobile subscriber milestone was reached in Q2 2017.
5G continues to occupy thought space as the next big thing in mobile.
But can you imagine that 4G, however, will dominate in terms of volume for at least the next 10 years *?
I have information about Windows/Mac and cross-browsers usage from different countries and continents.
It’s a fact that three-quarters of people with a mobile phone already use it for the internet — it’s what you expected, isn’t it ?
I once heard that whoever has information may, if desired, have everything.
Nice, isn’t it?
As a woman i like presents that are in boxes of any color or type,but as a woman with QA experience I know there is a big difference between black, gray, and white boxes. ;)
As a team we all know that we always have to maintain a shippable product. We have to deliver a steady flow of code from the team’s cave to the user’s home.
Let’s deliver not just a product. Do more. Go forward.
Let’s deliver for customers a product that is full of quality.
P.S. And don’t forget that curiosity killed the cat but didn’t kill any QA members :)
コメント