Skip to content

Latest commit

 

History

History
25 lines (15 loc) · 1.1 KB

test_strategy.md

File metadata and controls

25 lines (15 loc) · 1.1 KB
Raw

Integration tests

To test, you need to manually build mimir and then simply launch:

cargo test

Integration tests are spawning one ElasticSearch docker, so you'll need a recent docker version. Only one docker is spawn, so ES base has to be cleaned before each test.

To write a new test:

  • write your test in a separate file in tests/
  • add a call to your test in tests/tests.rs::test_all()
  • pass a new ElasticSearchWrapper to your test method to get the right connection string for ES base
  • the creation of this ElasticSearchWrapper automatically cleans ES base (you can also refresh ES base, clean up during tests, etc.)

Geocoding tests

We use geocoder-tester to run real search queries and check the output against expected to prevent regressions.

Feel free to add some tests cases here.

When a new Pull Request is submitted, it will be manually tested using this repo that loads a bunch of data into the geocoder, runs geocoder-tester and then add the results as a comment in the PR.