🧪 tests

[juftin]

Summary

This project needs unit (and integration?) tests.

Acceptance Criteria

New tests. I will keep this issue open until I feel like there's sufficient coverage though.

Notes

Some elements of this project can be tough to test without an actual hatch CLI running - hopefully I can make use of the click.CliRunner for this.

[oprypin]

Mm I'll probably not pitch in at all regarding tests. It's a bit much for me to try to understand right now.

I was actually thinking something like literally running hatch and checking that it still installs and runs the project, like, the actual steps that you surely took many times manually to check if it still works after all our refactors.
What happens if we mess up the lock file, then try to run. Then the same with DISABLE environment variable.
The tests would be written in Bash or something.

[juftin]

Yeah this is a tough one to test - I'm going to do my best to try to do some of that bash style testing inside the pytest framework. Honestly just using the plugin to install the testing and linting environments in its own CI/CD is an integration test on its own.

hatch-pip-compile/.github/workflows/tests.yaml

Lines 50 to 59 in 6cbb581

	- name: Install Hatch
	run: |
	python -m pip install --upgrade pip wheel
	python -m pip install -q hatch pre-commit
	python -m pip install -q "${{ github.workspace }}"
	hatch --version
	- name: Test Suite
	run: |
	echo "::add-matcher::.github/workflows/matchers/python.json"
	hatch run +py=${{ matrix.python }} matrix:cov

[juftin]

🎉 This issue has been resolved in version 1.8.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀