Skip to content

Quality Engineering: A Pragmatic Approach

Hello World.

Quality Assurance is at a turning point. For too long, this role has been summarized as end-of-chain validation or script writing, but those days are over.

I am a Quality Engineer currently in the field, and I am starting this blog today to step outside the boundaries of traditional QA and document a different path.

My Vision: Quality at the Service of Delivery

We often read that quality is “everyone’s responsibility” or that we must “aim for zero defects.” That looks great on a slide, but operational reality is different.

Over the years and projects, I have forged a simple conviction: Quality must not be a bottleneck, but a development accelerator.

If your test suite takes 2 hours to run, its operational utility is drastically reduced. It no longer fits into a fast Agile development cycle but forces the team into monolithic deployments. The result: feedback arrives too late, context is lost, and delivery is slowed down.

Here, I want to advocate for a “Lean” engineering approach:

  1. Protect Trust: A test that fails randomly (flaky) is worse than no test at all because it erodes the team’s confidence in the CI. There are only three viable options: fix it, delete it, or isolate it (quarantine) immediately so as not to block the flow.
  2. Strategic Automation: The goal is not to automate 100% of manual tests, but to build robust safety nets that allow developers to refactor and evolve the software without fear.
  3. Tech as a Lever: Using modern tools to reduce friction between development and production.

What Will We Talk About?

This blog will serve as public documentation for topics I deal with daily:

You won’t find grand academic theories here, but concrete feedback from the field, code that actually runs, and a vision focused on efficiency.

Looking forward to exchanging with you.

Jean-Michel


Share this post on: