Run unit tests on Windows

[ehmatthes]

Running unit tests on Windows should go a long way toward making sure everything works on Windows.

• [x] Set up a Windows 11 VM.
• [x] Clone project.
• [x] Install requirements.
• [x] Run unit tests.
• [x] Changelog
• [x] PR
• [x] Merge

[ehmatthes]

Working notes

• Inside the virtual environment on Windows, pip install --upgrade pip fails. It wants python -m pip install --upgrade pip.

[ehmatthes]

• Error: related to tzdata
• Go to tmp dir; try running simple_deploy in that env.
  • Most of the unit test output from the unit_tests/ dir looks normal, but it doesn't look like django-bootstrap5 was installed. I can manually install this in the temp test dir, and then simple_deploy --help works. ???
  • I can install django-bootstrap5 from vendor/, from within the temp test dir.
  • Okay, destroyed venv in temp dir. Tried running same install command from setup script. Failed at installing Django, because tzdata issue:

    ERROR: Could not find a version that satisfies the requirement tzdata; sys_platform == "win32" (from django) (from versions: none)
    ERROR: No matching distribution found for tzdata; sys_platform == "win32"

• I believe this is when it's trying to install Django? Maybe asgiref? Maybe tzdata? Anyway, after this pip freeze shows nothing. So, I think it moves on to installing django-simple-deploy, which is how it ends up with some packages installed.
• Relevant SO post?
• GPT: Django requires tzdata on Windows. So, add tzdata to vendor/.
• [x] Download tzdata to vendor/.
• In test dir, I can activate b_env and run simple_deploy --help and simple_deploy, with appropriate output. But pytest platform_agnostic_tests/test_valid_cli_commands.py fails.

  
  =============================================================== FAILURES ============
  _______________________________________________________ test_help_output[req_txt] __________________

tmp_project = WindowsPath('C:/Users/eric/AppData/Local/Temp/pytest-of-eric/pytest-4/blog_project0') capfd = <_pytest.capture.CaptureFixture object at 0x000002178B03A210>

def test_help_output(tmp_project, capfd):
    """Call `manage.py simple_deploy --help`."""
    valid_sd_command = "python manage.py simple_deploy --help"

  stdout, stderr = msp.call_simple_deploy(tmp_project, valid_sd_command)

C:\Users\eric\django-simple-deploy\unit_tests\platform_agnostic_tests\test_valid_cli_commands.py:22:

---

C:\Users\eric\django-simple-deploy\unit_tests\utils\manage_sample_project.py:161: in call_simple_deploy sd_call = subprocess.Popen(split(sd_command), stdout=subprocess.PIPE, stderr=subprocess.PIPE, text=True) C:\Users\eric\AppData\Local\Programs\Python\Python311\Lib\subprocess.py:1024: in init self._execute_child(args, executable, preexec_fn, close_fds,

---

- All platform-agnostic tests pass. There were issues with conversion of commands on Windows. GPT was really helpful in sorting through these. For the record, it did not suggest clear fixes, there was a lot of back and forth, but so much more efficient than SO and documentation dives.

[ehmatthes]

Testing heroku

• When I first wrote simple_deploy, Heroic was supported on all three OSes. So let's start testing with that platform.
• Test for heroku fails, but I can go to the test dir and run manage.py simple_deploy --platform heroku --unit-testing, and it configures the project.
• Note: All unit tests still pass on macOS at this point.
• There was an issue in conftest.py, run_simple_deploy(), where the regex for finding the platform was os-specific.
• All Heroku tests pass.

[ehmatthes]

Testing fly_io

• Test fails. In temp dir, I'm getting an unclean git status issue.
• There was an issue with the re in utils.write_file_from_template(). Fixed this, and 7 tests pass.
• .dockerignore is different on Windows, because it doesn't need to include .DS_Store.
• All Fly and Platform.sh tests pass.
• Entire test suite passes. Just to note durations:
  • ~2019 intel MacBook Pro: ~22s
  • 2022 Mac Studio M1 Max: ~12s
  • 16GB Windows Vm on Studio: ~43s