Now that we sorted out the pipelines and the infrastructure, this PR fixes and consolidates the scripts for testing.
In the tests, we check whether there is LocalDb installed, and if there is then we're using that one for integrations tests. So, if you're on a Windows machine and using VS (the LocalDb usually comes bundled in VS) then you can simply run all the tests through Test Explorer. But, if you're on Linux, then you need to do it through a docker container.
So, we'll have the following scripts:
run-tests.sh - This runs the tests (same as in Test Explorer) but also generates coverage reports in TestResults folder.
run-tests-docker.sh - Runs the tests in Docker container. It will generate reports too and will map to the same folder TestResults in the hosts' machine.
Now that we sorted out the pipelines and the infrastructure, this PR fixes and consolidates the scripts for testing. In the tests, we check whether there is
LocalDbinstalled, and if there is then we're using that one for integrations tests. So, if you're on a Windows machine and using VS (theLocalDbusually comes bundled in VS) then you can simply run all the tests through Test Explorer. But, if you're on Linux, then you need to do it through a docker container. So, we'll have the following scripts:run-tests.sh- This runs the tests (same as in Test Explorer) but also generates coverage reports inTestResultsfolder.run-tests-docker.sh- Runs the tests in Docker container. It will generate reports too and will map to the same folderTestResultsin the hosts' machine.