Add scripts for test and coverage reports. #351
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jul 21, 2025
This was referenced Jul 31, 2025
Closed
Closed
This was referenced Aug 7, 2025
This was referenced Sep 4, 2025
Open
This was referenced Sep 15, 2025
This was referenced Sep 26, 2025
Bump Ardalis.Specification.EntityFrameworkCore from 7.0.0 to 9.3.1
SHAHZADKHAN779/ECommerceWebsite#5
Open
This was referenced Oct 3, 2025
This was referenced Oct 10, 2025
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.