What will you do if you need to release a product but constantly find new issues, and fixing them leads to a new regression phase?

Assess the criticality of new issues. Determine which are showstoppers for the release and which can be fixed in the next sprint or patch. Conduct a joint meeting with the development, testing, and product management teams to decide on further actions. Options:

• Postpone the release until critical issues are fixed.
• Release with known non-critical issues documented.
• Release a hotfix (patch) immediately after the release to fix critical issues.

Alongside the decision-making:

• Focus efforts on testing critical parts of the functionality.
• Effectively communicate the status and issues found. Use shared task boards (Jira, Azure DevOps, etc.).
• Analyze the causes of the recurring issues:
  • Insufficient test coverage (manual or automated).
  • Problems with the development process (code review, coding culture).
  • Rushing in development and testing.
  • Insufficient requirements specification.

If necessary, strengthen regression testing, prioritizing it. Additional resources or reallocation of tasks within the testing team may be required. Automate the most frequent and critical regression scenarios if possible within tight deadlines. After the release, conduct a retrospective to identify and eliminate root causes of problems.