Skip to content

Latest commit

 

History

History
20 lines (16 loc) · 1.44 KB

README.md

File metadata and controls

20 lines (16 loc) · 1.44 KB

Steps to Run Locally

  1. Have docker installed
  2. Open a command prompt
  3. cd <REPO_ROOT>/integration-tests/docker-cts-listing-page-api
  4. docker-compose up --force-recreate
    • This is being run without the detached (-d) option so that it can be easier to stop. You can choose however you want to run it.
  5. cd <REPO_ROOT>/integration-tests
  6. ./bin/load-integration-data.sh -- this loads the test data
  7. ./bin/karate ./features -- This runs the tests
    • ./bin/karate -w ./features will watch the feature files and rerun when they are changed. So good for devving tests

Notes

  • Docs for understanding how to run Karate standalone
    • Specifically this has to do with the magic naming of the logging config which is really why I am posting this here!
  • We have docker for dev testing because ES will no longer run on higher Java versions, this is the easiest way to get it up and running.
  • .NET running locally on a Mac cannot talk to ES because of how NEST always uses the host name to connect to ES and ES exposes the Virtual Machine's hostname/IP that runs Linux on the Mac.
  • You need to use the --force-recreate option to docker-compose up or run docker-compose rm after shutting down the cluster. If the elasticsearch container is not removed, it keeps its data, and any restarts will leave the cluster in a bad state.