Best posts made by inna

According to me cases somewhat would be like:

1. Man is using stairs made of concrete to go down (positive)
2. Man is using Stairs made of wood or rope (positive)
3. Man is going down and steps are incomplete (negative)
4. Man is going down via rope and stairs and half way its broken (negative)
5. Man is using rope rope and wood stairs and Rope is not able to hold the weight of man. (Negative)
6. Just a floor above ground no stairs are present (Negative)
7. Man is falling from building (Negative)

It's not clear which repository you are migrating to TFS from? It is also not clear why to use Microsoft technologies (available in view of TFS) when there are repositories that have proven themselves to be excellent? For example GIT, SVN, etc.

But if you really want to use Visual Studio Test Professional, then the Microsoft documentation says that there is such a possibility: https://docs.microsoft.com/en-us/vsts/build-release/test/continuous-test-java

I had a similar situation in one of the projects. A separate test database is created before starting the tests and the structure of the prod database is copied into it and filled with fake data. Then it is removed.

Tests use a mock object to work with a database, where a test database is substituted instead of a prod.

Sometimes you need to run non-destructive tests on existing records in a prod or stage database; or if it is not convenient to update the test data - you can switch the used database.