Resume work

[ehmatthes]

I had to step away from this project, but I'd like to resume the push to a 1.0 release. I believe the biggest issue is ensuring correct functionality on Windows for all three platforms. I haven't tested on Linux, but there's enough similarity with macOS that any Linux issues should be quick to resolve.

Initial work:

• [x] Run unit tests.
• [x] Run integration tests.
  • [x] platform.sh
  • [x] fly.io
  • [x] heroku
• [x] Open a new issue to focus current work without getting bogged into a bunch of smaller issues that are less critical. #212
• [x] Do a quick review of previous issues to prioritize current work. (In #212)

[ehmatthes]

Unit tests

• [x] Currently, one test fails. I believe the issue is when configuring for poetry on Heroku deployments:

  =================================================== short test summary info =================
  FAILED platforms/heroku/test_heroku_config.py::test_requirements_txt[poetry] - AssertionError
  =========================================== 1 failed, 89 passed, 3 skipped in 26.76s ========

Okay, test infrastructure is pretty good to work with. I can see from the output the path to the test requirements file that was incorrect, and the reference file is in the unit_tests/platforms/heroku/reference_files/ directory. The path to the test file doesn't work, though, because other tests after the failing test wrote over that file.

Fix: run pytest -x, which should end on that failed test, and I should be able to look at the incorrect requirements file. To be even more efficient, only test the platform that's generating the failure: pytest -x platforms/heroku.

Failed because Poetry is more precise about versions, I believe.

• [x] Update poetry reference requirements file so unit tests pass,
• [x] Figure out why other tests didn't fail, since last unit test run was on Django 4.1, and current latest version is 4.2.
  • req_txt approach pins project to Django 4.1.4. Pipfile generates a * version.
• [x] Make an issue to update unit tests docs to show how to run tests in a more diagnostic way, as described above. (implemented instead of opening issue)
• [x] Add a root-level conftest.py that generates a clean reminder to cd into unit_tests/ before calling pytest.

[ehmatthes]

Integration tests

• [ ] Run platformsh integration test.