Get FileNotFoundError when use relative path as file_body

[cyj5230]

I put all my test data into 1 folder, say /mnt/c/users/me/documents/repo/test/tavern/latest/test_data
while the test yaml is in /mnt/c/users/me/documents/repo/test/tavern/latest/folder/test.yaml

json: !include ../test_data/file.yaml -> this works
file_body: ../test_data/file.bin -> this doesn't work, get FileNotFoundError
file_body: {full_path}/file.bin -> this works
file_body: test/tavern/latest/test_data/file.bin -> this works

Is it possible to unify the relative path logic, so that I can use similar file path for !include and file_body? Thank you.

[michaelboulton]

This isn't impossible but it is a bit fiddly because loading files with !include is handled using the TAVERN_INCLUDE_PATH and the path of the file the include is actually in, but loading files to send in a request is handled by requests so it works relative to the directory the tests are run in