Trying to organise the tests, part 1 #405
Closed
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.
In the Bijectors test suite there are two kinds of AD tests:
Check that the manual implementation of
Bijectors.logabsdetjac
returns the same numerical result as an AD backend (I think we should ideally like to always use FiniteDifferences, but in some cases we use ForwardDiff). This usually involves a manual call toForwardDiff.jacobian
or similar.Check that AD backends can differentiate through Bijectors code. This uses the
test_ad
function.Generally these fall under the 'interface' / 'AD' test suite respectively.
But there are a couple of stragglers where the
test_ad
function is being called in the interface tests. This PR gets rid of the exceptions.This PR also streamlines CI a bit:
min
andlts
separately (our min compat is 1.10.8 and lts is 1.10.10 so it's really no different).