Make integration tests runnable on Windows

Summary

Fixes #8 (closed) and #7 (closed) and #9 (closed)

Focus

Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

README.md

@@ -33,6 +33,29 @@ or manually via
    path to the pem file in the `CAOSDB_SERVER_CERT` environment variable.
 7. Run with `ctest` in the build directory.
 
+### Windows ###
+
+On windows, you still need to build and create a conan package from
+linkahead-cpplib using conan-create or the make.ps1 script in the
+cpplib repo.
+
+This repo also provides a make script `make.ps1` to run the
+integration tests on Windows. You need to create a python virtual
+environment and install the requirements from linkahead cpplib or
+recycle the one you used to create the package there:
+
+```sh
+python -m venv .venv  # Choose any path you like for your venv
+.venv/Scripts/Actvate.ps1
+pip install ../linkahead-cpplib/requirements.txt  # You may need to change the pass to cpplib here
+```
+
+Then build and run the tests with
+
+```sh
+make.ps1 all
+```
+
 ### Troubleshooting ###
 
 - If you don't have `clang-tidy` installed, you can run the first `cmake` command with