bdd_features_base_dir is relative to pytest rootdir #573
Conversation
Codecov ReportBase: 98.50% // Head: 98.52% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #573 +/- ##
==========================================
+ Coverage 98.50% 98.52% +0.02%
==========================================
Files 32 32
Lines 735 745 +10
Branches 16 16
==========================================
+ Hits 724 734 +10
Misses 9 9
Partials 2 2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
The pytest rootdir is the directory containing pytest.ini (or similar): https://docs.pytest.org/en/latest/reference/customize.html#rootdir This allows you to run pytest when the current working directory isn't the same as the directory containing the tests. I need to do that because in my system, the directory containing the tests is on a read-only filesystem.
|
Rebased onto master now that #572 is merged. |
|
@youtux thanks for the very quick review of all my recent pull requests. This is the last one (for now, at least). This was my initial goal before I got sidetracked with the other fixes & tidy-ups. :-) This fixes invoking pytest from a directory outside of the rootdir. The behaviour hasn't changed for users who invoke pytest from the same directory as the rootdir (i.e. most users). |
|
LGTM! Would you mind adding an entry to the change log file with this? I think it's worth adding the fix there |
The pytest rootdir is the directory containing pytest.ini (or similar):
https://docs.pytest.org/en/latest/reference/customize.html#rootdir
This pull request allows you to run pytest when the current working directory isn't the same as the directory containing the tests. I need to do that because in my system, the directory containing the tests is on a read-only filesystem (and my tests themselves write files to the current directory).
TODO:
pytesterfixture instead oftestdir#572 and rebase.