-
Notifications
You must be signed in to change notification settings - Fork 48
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
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.
base repository: matplotlib/pytest-mpl
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.16.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: matplotlib/pytest-mpl
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.16.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 8 files changed
- 1 contributor
Commits on Jun 15, 2022
-
I've removed the `workflow_dispatch` trigger from `update-changelog.yaml` as the `workflow_dispatch` event does not have the release details in its payload so I doubt this would run successfully.
Configuration menu - View commit details
-
Copy full SHA for 391a608 - Browse repository at this point
Copy the full SHA 391a608View commit details -
Needed to be manually added as the automated workflow failed
Configuration menu - View commit details
-
Copy full SHA for c050129 - Browse repository at this point
Copy the full SHA c050129View commit details
Commits on Jun 16, 2022
-
Merge pull request #169 from ConorMacBride/fix-changelog-branch
Rename default branch to `main`
Configuration menu - View commit details
-
Copy full SHA for 48e652f - Browse repository at this point
Copy the full SHA 48e652fView commit details
Commits on Jun 25, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 4e5981a - Browse repository at this point
Copy the full SHA 4e5981aView commit details -
Use a wrapper to intercept and store the figure
Rather than overriding the low level `pytest_pyfunc_call`, we can wrap the test function in a wrapper that stores its return value to the plugin object.
Configuration menu - View commit details
-
Copy full SHA for af96b02 - Browse repository at this point
Copy the full SHA af96b02View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3a22789 - Browse repository at this point
Copy the full SHA 3a22789View commit details -
Configuration menu - View commit details
-
Copy full SHA for 76a560d - Browse repository at this point
Copy the full SHA 76a560dView commit details -
Configuration menu - View commit details
-
Copy full SHA for d9d380d - Browse repository at this point
Copy the full SHA d9d380dView commit details
Commits on Jun 29, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 32b9a12 - Browse repository at this point
Copy the full SHA 32b9a12View commit details -
Handle tests which do not complete
If the return value hasn't been added to the dictionary, it means that the user's test didn't reach the end. This means that it raised an exception or was otherwise stopped early by pytest (skipped, failed, etc). In any case, we should not proceed with figure testing and use the result that pytest has already determined. Fixes #172
Configuration menu - View commit details
-
Copy full SHA for d84892b - Browse repository at this point
Copy the full SHA d84892bView commit details
Commits on Jul 22, 2022
-
Merge pull request #171 from ConorMacBride/fix-unittest
Fix tests which exit before returning a figure or use `unittest.TestCase`
Configuration menu - View commit details
-
Copy full SHA for 310ee99 - Browse repository at this point
Copy the full SHA 310ee99View commit details
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 v0.16.0...v0.16.1