Nick-Minutello
Nick-Minutello
Not sure about the `stop` in your tests
Add another instance of the same issue. Resorted to using: ``` import NodeHttpAdapter from "@pollyjs/adapter-node-http"; import FSPersister from "@pollyjs/persister-fs"; ``` ``` const config = { adapters: [NodeHttpAdapter ], persister: FSPersister...
Have a look at the documentation for test framework integration. We had a bit of difficulty getting things working because the documentation & behaviour didn't match. https://netflix.github.io/pollyjs/#/examples?id=jest-node-fetch https://netflix.github.io/pollyjs/#/examples?id=typescript-jest-node-fetch https://netflix.github.io/pollyjs/#/test-frameworks/jest-jasmine
Excellent. Thanks. Got it working. I like your organisation of recordings more than the default with jest. Any chance of this making a release?
This still appears to be an issue. Any resolution planned?
It is possible, reaching into the internals .... ``` proxy._server.address().port ```
Up-vote from me! Is there anything (aside from time/attention) that is holding this up? Some technical complexity that needs to be resolved ?
Question: After applying the changelog (which is actually supplied by 3rd party) as the 'admin' user, we need to update the (Oracle) permissions so that the 'app' user has CRUD...
Is there any particular reason why **executeSql** is _not_ in the maven integration?
Not sure if the solution in the forum works, but quite possible it's a lack of understanding on my part.