With the recorded cases prepared as tests, you can start rewriting the application and checking its behaviour as you go. Give the agent the requirements for the new version, review differences and complete the checks that the database recordings cannot cover.
Provide a test environment where the rewritten application can load the recorded starting data and make changes freely. You can run the tests locally or in a separate test environment. If you reuse the connected database, confirm that its contents can be replaced for testing. Tell the agent how to build and run the new project.
Ask the agent to implement the agreed requirements and run the recorded cases as each part is ready. Each test starts from the recorded data, runs the corresponding action in the new app and compares the resulting changes. Review failures to decide whether they indicate an implementation problem, a test setup issue or an intentional change that needs an updated expectation.
Work through the separate checks agreed during Coverage, including screen responses, emails, external systems and cases you did not record. Confirm any intended behaviour changes with the people responsible for the application. Keep the test results and review notes with the project, then use your usual release process to plan the move to the new version.
Passing these tests confirms the database changes for the selected cases. Release readiness also depends on your remaining checks and migration requirements.
Next: use the results to plan your release, or return to the Migrations overview.