Tests failing on Windows

[ldkv]

Tests with tilde (~)

These tests involve tilde ~ will fail on Windows simply because the symbol is not recognized by Windows.

Suggestion

Put them in a separate tests that are skipped if running on Windows.

test_hash_path

This test fails on Windows (or maybe different environment, different Python version, etc.), the hardcoded value is not always the same.

Suggestion

The hardcoded value is flaky and not really deterministic, we should remove it. What's important is to test the behavior of the hash function, which is producing the same hash with the same input.

uvlink/cache in path string

This test and this test fail on Windows due to the path string is resolve differently, uvlink/cache would become uvlink//cache.

Suggestion

Replace:

assert "Cache Location:" in result.stdout
assert "uvlink/cache" in result.stdout

with:

assert f"Cache Location: {cache_dir}" in result.stdout

Or just remove the assert for uvlink/cache entirely.

[c0rychu]

Thanks for catching these!

For the test_hash_path, it does pass these OS, Python versions combination testing on CI, though:

uvlink/.github/workflows/ci-tests.yml

Lines 17 to 18 in 47acf29

	os: [ubuntu-latest, macos-latest]
	python-version: ["3.12", "3.13", "3.14"]

But we can think about it if that is the behavior we want to require.

For the others, I'll need to check them later when I have more time. :)

[c0rychu]

Just add a comment:
The reason behind the hard-coded hash for "/" for the test on Unix-like OS is that I want to make sure I have backward compatibility for upcoming updates. But again, if it's worth having breaking changes, I'm open to changing that.

[c0rychu]

fixed by #24