Closed mekanix closed 2 years ago
@syphar do you think, we can check it out?
Hello! I'd like to dig into this issue. Could you help narrowing it down initially? I mean, currently I have no clue where to start.
@mekanix thank you!
you would need to split the problem:
For each failing test we do assertions on the pytest output, and we need to see what's wrong.
One thing we directly see is:
'SKIPPED [1] /usr/ports/devel/py-pytest-translations/work-py37/pytest-translations-2.0.0/pytest_translations/po_spelling.py:73: aspell dictionary for language de not found.'
Which seems to be a missing dictionary for the tests.
It would be awesome if you can add FreeBSD tests to our testing pipeline, there are perhaps some helpers you can use ( like https://github.com/marketplace/actions/freebsd-vm , but I didn't dig deeper) .
I'm aware the output-line matching is not the optimal way to test this extension, but it's all we have here :)
I just remembered to look, pytest version is 4.6.11. I would have to upgrade that first and get back to translations. I'll keep you posted.
As for tests, I'll have to set it up for some of my projects, now that you shared marketplace. Thank you!
Upgrading pytest fixed half of the failing tests while installing de-hunspell fixed the other half, as enchant is built with hunspell by default.
I have to play a little with freebsd-vm action and I'll send PR for it. Thank you!
that is awesome! 🎉
It's all in the ports now and Pytest is upgraded, too. I will leave this issue opened until I write CI for it, if you don't mind.
I am happy to report that latest version is in FreeBSD ports. All tests are now enabled and when the next build of packages is finished pytest-translations will be updated. Thank you!
I'm trying to write FreeBSD and I'm stuck on testing. I would be really glad if you could help me resolve this.