-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing tests issues #89
Comments
devtools::test("~/Documents/workflows/EMODnet/EMODnetWFS")
#> ℹ Loading EMODnetWFS
#> Loading ISO 19139 XML schemas...
#> Loading ISO 19115 codelists...
#> Loading IANA mime types...
#> No encoding supplied: defaulting to UTF-8.
#> ℹ Testing EMODnetWFS
#> ✓ | F W S OK | Context
#>
#> ⠏ | 0 | client
#> ⠋ | 1 | client
#> ⠹ | 3 | client
#> ⠴ | 6 | client
#> ⠧ | 1 7 | client
#> CrulAdapter disabled!
#> HttrAdapter disabled!
#>
#> x | 1 10 | client [1.6s]
#> ────────────────────────────────────────────────────────────────────────────────
#> Failure (test-client.R:37:5): Services down handled
#> Snapshot of `check_service(req_fail)` has changed:
#> old vs new
#> - "An exception has occurred. Please raise an issue in https://github.com/EMODnet/EMODnetWFS/issues"
#> + "Service creation failed"
#>
#> * Run `snapshot_accept('client')` to accept the change
#> * Run `snapshot_review('client')` to interactively review the change
#> ────────────────────────────────────────────────────────────────────────────────
#>
#> ⠏ | 0 | filter
#> ⠋ | 1 | filter
#> ⠙ | 2 | filter
#> ⠹ | 3 | filter
#> ⠸ | 4 | filter
#> ⠼ | 5 | filter
#> ⠴ | 6 | filter
#> ⠧ | 8 | filter
#> ✓ | 9 | filter [4.3s]
#>
#> ⠏ | 0 | info
#> ⠋ | 1 | info
#> ⠸ | 4 | info
#> ⠦ | 7 | info
#> ⠋ | 11 | info
#> ✓ | 13 | info [7.1s]
#>
#> ⠏ | 0 | layer_attributes
#> ⠋ | 1 | layer_attributes
#> ⠹ | 3 | layer_attributes
#> ⠸ | 4 | layer_attributes
#> ⠏ | 10 | layer_attributes
#> ⠹ | 13 | layer_attributes
#> ✓ | 14 | layer_attributes [3.0s]
#>
#> ⠏ | 0 | layers
#> ⠋ | 1 | layers
#> ⠇ | 9 | layers
#> ⠋ | 11 | layers
#> ⠇ | 19 | layers
#> ⠋ | 21 | layers
#> ⠙ | 22 | layers
#> ⠼ | 25 | layers
#> ⠴ | 26 | layers
#> ✓ | 27 | layers [13.7s]
#>
#> ⠏ | 0 | vendor-params
#> ⠋ | 1 | vendor-params
#> ✓ | 1 | vendor-params [0.8s]
#>
#> ══ Results ═════════════════════════════════════════════════════════════════════
#> Duration: 30.5 s
#>
#> [ FAIL 1 | WARN 0 | SKIP 0 | PASS 74 ] Created on 2022-04-04 by the reprex package (v2.0.1) |
So bizarre! Running
Snapshot file at
|
Closed in favor of #93 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tests seem to be failing locally and in #88. I've re-run and created new snapshots in the last commit but am still getting 3 failing tests I could do with some help on.
Firstly, what I did:
Deleted the fixtures in
tests/testthat/fixtures/
and then randevtools::tests()
. However this resulted in (and would only be triggered when this folder was empty) the new snapshots are still generated in foldertests/testthat/tests/testthat/fixtures
rather thantests/testthat/fixtures/
. I imagine that is not the wanted behaviour. How di you manage to get theThe result is that I seem to have ended up in a loop where, when I accept some changes to snapshots after
devtools::test()
they are accepted in thetests/testthat/tests/testthat/fixtures
but then when I re-run the tests it doesn't seem to recognise that fixtures exists and tries to re-snapshot them! So I am wondering whether is is checkingtests/testthat/fixtures/
, finding it empty triggering snapshotting but then snapshotting is saved intests/testthat/tests/testthat/fixtures
?The text was updated successfully, but these errors were encountered: