You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and then change one of the files in test/pacts/ (either manually or by running my unit tests), the change is not reflected in subsequent requests to the server without restarting it.
run Acceptance tests using Cypress and the pact-stub-server
I'd like to keep Cypress, the pact-stub-server, and the unit-test suite all running in the background so I can develop continuously. As it is, I need to restart the Docker containers after every change.
Possible Solutions
PactSource::Dir could watch the directory rather than walk it during load.
The pact-stub-server Dockerfile could use something like notify-rs to watch the directory and restart the server process on changes (after a debounce period)
The text was updated successfully, but these errors were encountered:
Another use-case: it would be nice to start the pact-stub-server in a GitHub Action using services, but that will start it before I have a chance to run unit tests and output pact files.
mefellows
changed the title
Server does not obey changes to pact files
Feature request: Live update stubs
Nov 23, 2022
Problem
If I run the server as follows:
and then change one of the files in
test/pacts/
(either manually or by running my unit tests), the change is not reflected in subsequent requests to the server without restarting it.Why this matters
Following the Writing Consumer Tests guide, our process is:
test/pacts/…
filesI'd like to keep Cypress, the pact-stub-server, and the unit-test suite all running in the background so I can develop continuously. As it is, I need to restart the Docker containers after every change.
Possible Solutions
PactSource::Dir
could watch the directory rather than walk it during load.The text was updated successfully, but these errors were encountered: