Blog

Monitoring saves your business

Want your business running 24/7? Probably the answer will be yes. So in terms of quality assurance you’ve been doing everything that depends on you: proper QA at development phase, acceptance testing and finally monitoring. Now you’ve got full circle QA, each process works on 100% and everything is seems to be ok... or not?
6 March 2014
General
Quality assurance
The article by a1qa
a1qa

Want your business running 24/7? Probably the answer will be yes. So in terms of quality assurance you’ve been doing everything that depends on you: proper QA at development phase, acceptance testing and finally monitoring. Now you’ve got full circle QA, each process works on 100% and everything is seems to be ok… or not?

Let’s figure it out, what are your monitoring and what are your expectations? Usually you apply hardware monitoring or something equivalent to get sure that your server wouldn’t run out of free disk space or memory. But what can you expect from such approach? Probably that your product, as well as your business, is running. Will it be informative? Certainly not. The only information that could be gathered depending on hardware monitoring is hardware status, not your application status, so the full circle QA looks more like a Pac-man. Yet to avoid this, the best practices of QA outsourcing would tell you to look at the entire pyramid:

In terms of business it might seem ok to monitor only the top of application pyramid – business level. It could be implemented via slightly modified automated tests from development phase or other special tools that can interact at application level. With such monitoring approach you can be sure that the most critical part of your business is well functioning. But this will be never enough in fact. This is the only way to make sure that everything is good for now, but to prevent problems you should go deeper.

The main reason for that is feedback. The quicker is the feedback, the quicker would be reaction in case of emergency. Deeper in this case means faster, but sometimes less relevant. At business level if something goes wrong – it’s absolutely wrong. At application level if something goes wrong – it’s probably wrong, or will go wrong in near future.

If something goes wrong at hardware level it could be either absolutely wrong or not important, with “would go wrong somewhere in the future” between them. So if you want to be sure that your business is up and running – consider extending monitoring from one level of application pyramid to at least two of them, to have faster feedback along with high relevance of result.

The article is prepared by Yan Gabis

More Posts

debated technologies
30 May 2023,
by a1qa
3 min read
a1qa tech voice: Managing director at a1qa, North America, discusses pros and cons of much-debated technologies
Nadya Knysh, Managing director at a1qa, North America, puts a spotlight on 6 current technologies, discussing their positives and negatives.
General
Interviews
Test automation
why-do-bugs-get-missed
17 April 2023,
by a1qa
4 min read
Why do bugs get missed? Learn the problems and tips to avoid them
Still, finding overlooked bugs after the app goes live? Let’s find out why this happens and how to fix it.
Quality assurance
Test automation
6-march-2023-1
21 March 2023,
by a1qa
4 min read
The ultimate QA guide for smoothly migrating to Web 3.0
Find out how businesses can seamlessly migrate to Web 3.0 by relying on quality assurance.
Cybersecurity testing
General
Performance testing
Usability testing
a1qa-articles
31 January 2023,
by a1qa
5 min read
Best of 2022 by executives: 8 most visited a1qa blog posts
Let’s look back and revisit the most visited a1qa articles of 2022!
Quality assurance
Test automation
qa-trends
12 January 2023,
by a1qa
4 min read
The future of software testing: top 4 impactful trends that will dominate in 2023
Consider the major industry trends for the upcoming year to know how to improve current QA strategies and stay ahead of the curve.
QA trends
Quality assurance
Test automation
test-automation
7 December 2022,
by Dileep Marway
3 min read
Release at pace with test automation: What, why, and how to measure success?
An automation-first approach is key to enhancing testing capabilities and increasing overall operational efficiency. However, I would suggest justifying its implementation, so that it can deliver the promised value.
Quality assurance
Test automation
what-is-a-culture-of-happiness
2 December 2022,
by Dileep Marway
3 min read
What is a сulture of happiness for a QA company?
Great culture drives employee engagement and satisfaction, contributes to an impressive work output, and improves organisational performance. But how do we build a culture of happiness? In this blog, I will share more on the answer to this.
Quality assurance
agile-qa
30 November 2022,
by Dileep Marway
3 min read
Agile QA – what is needed for greater flexibility and speed?
What should your QA team focus on to become truly agile, enable quality at speed, and contribute to lasting performance improvement? In addition to introducing test automation, I suggest considering shared responsibility for software soundness.
Agile
Quality assurance
interview-with-dileep
28 November 2022,
by a1qa
9 min read
Interview with Dileep Marway on a series of articles “Agility and speed: Supercharging your business strategies with QA”
We cooperated with the VP of Engineering and Quality at SHL to present you with a series of his blog posts on: culture of happiness, test automation, and Agile-driven QA. Happy reading!
Agile
Quality assurance
Software lifecycle QA
Test automation

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.