I've noticed the following test failures happen intermittently.
The only pattern I can deduce that at least one test is likely to fail after switching branches that require running npm i (i.e. b/c dependencies have changed). For example between main and c/node-fetch-3.2.10.
Reproduction
check out c/node-fetch-3.2.10 and git pull
npm i
npm test
I see one failure like:
Chrome 112.0.0.0 (Mac OS 10.15.7) invite-users should not send any request for zero-length username array FAILED
Error: Expected true to equal false.
at <Jasmine>
at packages/arcgis-rest-portal/test/groups/invite-users.test.ts:138:36 <- packages/arcgis-rest-portal/test/groups/invite-users.test.js:108:51
run npm test again, no failures
repeat, unable to get that test to fail after a couple attempts
check out main and git pull
npm i
npm test
I see a new test fail:
Chrome 112.0.0.0 (Mac OS 10.15.7) ArcGISIdentityManager Client side oAuth 2.0 .beginOAuth2() without PKCE should authorize via implicit grant in a popup FAILED
Error: Expected 22 to be 21.
at <Jasmine>
at packages/arcgis-rest-request/test/ArcGISIdentityManager.test.ts:1171:60 <- packages/arcgis-rest-request/test/ArcGISIdentityManager.test.js:893:70
run npm test again, no failures
repeat, unable to get that test to fail after a couple attempts
Describe the bug
I've noticed the following test failures happen intermittently.
The only pattern I can deduce that at least one test is likely to fail after switching branches that require running
npm i
(i.e. b/c dependencies have changed). For example betweenmain
andc/node-fetch-3.2.10
.Reproduction
c/node-fetch-3.2.10
andgit pull
npm i
npm test
I see one failure like:
npm test
again, no failuresmain
andgit pull
npm i
npm test
I see a new test fail:
npm test
again, no failuresLogs
No response
System Info
Additional Information
This might be specific to #1021, but I thought I'd open an issue just in case it pops up elsewhere.