Hi, I am having trouble running tests that use local files. What is the correct way to include files as resources for testing? My directory layout is like this • pants.toml • pants • service ◦ BUILD ◦ examples ▪︎ data • data.csv ◦ sub_dir_1 ▪︎ BUILD ▪︎ <other files> ◦ test ▪︎ sub_dir_2 • BUILD • test_service.py service/BUILD has this:

resources (
    name="test-data",
    sources=["./examples/data/*"],
)

pex_binary(
    name="service",
    entry_point="service.py",
    platforms=[
        "current",
        "manylinux2014-x86_64-cp-39-cp39",
    ],
    dependencies=[":test-data"],
)

test/sub_dir_2/BUILD has this:

pex_binary(
    name="test_service",
    entry_point="test_service.py",
    dependencies=["service:test-data"],
)

I am trying to package everything as a pex file. A test in test_service.py uses the files as such:

path = str(pathlib.Path(__file__, "../../../examples/data/data.csv").resolve())
do_something_with(path)

Checking the sandbox, indeed, the files don't exist(actually no resources exist). However, I do see the files in the packaged .pex archives. I am trying to run the test as such

./pants --keep-sandboxes=on_failure test service/test/sub_dir_2/test_service.py -- -k test_csv

I am using pants 2.13.0. I would really appreciate any pointers on how to go about including files in tests. TIA, CSN

Try loading the file using a resource loading API, such as https://docs.python.org/3/library/importlib.html#module-importlib.resources

Hi @happy-kitchen-89482, Thank you very much for the quick response! Adding explicit dep (on the resources target) to the python_sources and in python_tests worked. ref. why pex_binary: I am a pants noob (and a big fan after using it!). When I ran tailor on the directory, it created both a pex_binary and a target for python_tests. Since I was able to list the tests, I naively assumed things were as they must be. This is what my BUILD in test/sub_dir_2 looks like:

python_tests(
    name="tests",
    sources=["test_service.py"],
    dependencies=["service:test-data"],
)

python_sources()

pex_binary(
    name="test_service",
    entry_point="test_service.py",
)

Thank you so much for the help! qq: Is there a way to force pants to rerun the tests? I wanna experiment a bit with my setup and pants returns the memoized results.

Ah! I’m guessing your

test_service.py

has an

if __name__ == '__main__'

stanza in it? That will cause

tailor

to guess that it’s a binary and generate a

pex_binary

target for it.

I run it through pytest and indeed there is that stanza! Is it safe to delete the binary target?

It is, unless you plan to run this file like a binary, but generally you can just run it as a test, it sounds like?

Yes sir, that is pretty spot on. Again, thank you so much for the help!

You’re welcome!

I must admit I don’t know the answer to this question. I picked up this repo from a coworker to test out build systems. I have only ever run this with pytest and now that you mention it, does seem curious. Let me check and revert back.

Thanks for closing the loop!