Resolve paths in tests

[blink1073]

Attempt to fix https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=476179&view=logs&jobId=656edd35-690f-5c53-9ba3-09c10d0bea97&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d

[codecov-commenter]

Codecov Report

Merging #245 (3a96127) into main (2788986) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #245   +/-   ##
=======================================
  Coverage   69.34%   69.34%           
=======================================
  Files          20       20           
  Lines        1631     1631           
=======================================
  Hits         1131     1131           
  Misses        500      500           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2788986...3a96127. Read the comment docs.

[bollwyvl]

Cool, thanks. It does still seem a bit odd that the tests are separated out, but not the test_data.

Of additional note: we're also having to do special stuff to handle the the yml file.

I wonder if the yml path should be hoisted to someplace in the programmatic API... not the parsed data, though, I guess, unless we pre-generated is JSON... yaml parsing in the hot path of a request (or even a server startup) seems to be an anti-feature.

[blink1073]

It does still seem a bit odd that the tests are separated out, but not the test_data.

We needed test_data that is used by the pytest_plugin (settings, workspace files, etc.).

In general including tests in your package is not supported by pytest, and we had had to strip out the translation tests due to path length restrictions on Windows.