Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 9 commits
- 15 files changed
- 1 contributor
Commits on Jun 14, 2024
-
-
-
Cover Test.Hspec.Junit.Config.Env in tests
This was best accomplished by extracting a pure function to test with.
-
Support interpolating {base} in JUNIT env settings
In a monorepository of multiple packages using JUnit, there is no way (via ENV configuration) to avoid each package overwriting the lasts test file, since anything you set will be used uniformly by all the test suites, as they are a single process. By adding a very simple interpolation of `{base}` by the basename of the current directory, this can be avoided without resorting to in-code configuration by setting something like `JUNIT_OUTPUT_NAME={base}.xml`. Arguably, that would be a better default than the current `junit.xml`, but moving to that would be a breaking change, and incorporating `{base}` generally through all the settings feels useful anyway. -
-
-
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.1.1.0...v1.1.2.0