How to Troubleshoot
<SERVICE-NAME> can be found in
make -f .stoobly/docker/Makefile <WORKFLOW-NAME>/services
<WORKFLOW-NAME> by default can either be record, mock, or test
After Scaffolding an App
After Running a Workflow
Double check expected containers are running
Ensure the proxy container for each service is running
e.g.
docker ps | grep <WORKFLOW-NAME>-<SERVICE-NAME>.proxy-1
To learn about which containers should be running, see here
If the workflow is either
record
ormock
ensure the gateway service is runninge.g.
docker ps | grep <WORKFLOW-NAME>-gateway.service-1
Gather logs to trace request
Ensure that a request gets routed to the correct service container
To learn more about request service flow, see here
To view service logs run:
make -f .stoobly/docker/Makefile <WORKFLOW-NAME>/logs
To view gateway logs run:
make -f .stoobly/docker/Makefile <WORKFLOW-NAME>/logs options="--container service --service gateway"
Use validate workflow command
To learn more about the command, see here
After Unexpected 5xx Error
Ensure CA certs are installed
Run either of the following:
make -f .stoobly/docker/Makefile ca-cert install
stoobly-agent ca-cert install
For manual installation, see https://docs.mitmproxy.org/stable/concepts-certificates/
After 499 Status Code (Mock Not Found)
Double check if the correct scenario is used
Double check if request exists in the scenario
By default the UI is configured to run on http://localhost:4200
Double check rewrite rules
See
.stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/bin/configure
To learn more about rewrite rules, see here
Double check lifecycle hooks
See
.stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/lifecycle_hooks.py
To learn more about lifecycle hooks, see here
Double check match rules
See
.stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/bin/configure
To learn more about match rules, see here
After Incorrect Response Returned
Double check if the correct scenario is used
Double check if request exists in the scenario
By default the UI is configured to run on http://localhost:4200
Create an Endpoint to enable component specific matching
To learn more, see here
Last updated
Was this helpful?