How to organize work with migrations in doctrine when testing code by features?

Question

Doctrine ORM

I would like to implement Git Flow with functionality testing by features:
-> the developer makes his feature (for example, changes the code and database)
-> the docker image with the feature is assembled
-> the tester rolls the image to the stage server and checks the entire project
-> if everything is fine, then the code is rolled out to production.
When there are no changes in the database structure, then everything is very beautiful. But we use a relational database (mysql). B if the database changes, then the problem arises of what to do with the results. If we just kill and roll on the default dump, then there may be a situation when we lose some kind of Dataset that the tester has been doing for a long time. It seems to me ideal to be able to roll back the changes that are made in a particular feature, but I have not yet found a single ready-made solution.
Whether someone can describe as the relational DB in such situation?

Answer 1

there is some separate script which rolls on the base collected from migrations - test data.
when building a project on a test environment, each time structure migrations are performed from scratch and test data is rolled over.