How was your process of working with requirements and test cases organized? Shift-left approach?

In our process of working with requirements and test cases, we applied the shift-left approach, which means moving testing and validation of requirements to the earliest stages of development.

This included:

• Early involvement of QA in discussions of requirements and design.
• Joint creation of test cases with analysts and developers during the specification phase.
• Automation of tests that were run during the build and integration stages (CI).

This approach allowed us to identify defects and non-conformities of requirements before coding began, reducing the cost of fixing errors and speeding up the development cycle.

Example:

• After writing requirements, QA immediately created test cases and checked them with the team.
• When requirements changed, test cases were updated and run automatically.

This ensured quality and transparency at all stages.