Learn System Before Solving Release & Testing Challenges

 

I read this question on The Test Chat posted on 31st January 2026.

Hi, As we know that due to AI, development is happening at a much greater speed. Adding CI/Cd to it, companies are deploying daily releases.

Now consider you're a QA manager and you're assigned to a new project. Since it's a new development, Automation is not feasible as new features and changes are constantly happening. Also note that adding new resources to the QA team is not in budget.

How would you scale manual testing to cope up when the speed of development is a daily release ?

Please do not use ChatGPT 😁

The Question Posted on The Test Chat

Not sure if this is an interview question or a question posted from one's current context.

Here are my interpretations of the question to start. It will evolve as I discuss further.

1. What system is being discussed in the question?
• Having no idea on what is the system being discussed, all our discussions will be vague and irrelevant.
2. The said situation is possible and a common daily happening in startups and tech enterprises.
3. The daily releases are a common operations.
• But, the question is what are being released daily?
• How many releases in a day?
• How the teams orchestrate the release management? How the dependent interfaces are informed about it?
4. What is missing in this question?
• It does not say which all interfaces of the system as part of a product are changing constantly.
• Also, it does not say how these interfaces are connected and how they are interdependent.
• Does the change in one interface affect the other? If so, how?

I see the above questions should be worked upon for first.

Testing has to align with the speed of product's development.  In other words, today, the testing is all about the speed for first and then feedback at the fastest knowing the risks -- risk focused with AI in the arena than bug focused.  That is, by enabling the solutions of AI, the priority of me as a tester will be to focus over risk for first and than the bugs.

This is not a testing problem as such from the description of question.  It is the problem of seeking the clarity and how to be an enabler -- release enabler.

Once the clarity is available, one need to work on how to execute the testing and automation as an engineering activity in the chaos, yet deliver the serving releases.  

Me reasoning the above questions for first before working on scaling and executing the testing and automation, will be of super help.

Me having no clarity on the system and its interfaces dependency, but, working to streamline efforts with testing and automation for a super fast paced daily releases, is an engineering risk.