local-it/e2e_tests
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

remove PYTHONPATH stuff

Browse source
This commit is contained in:
Daniel 2023-12-07 17:16:15 +01:00
parent 9121128935
commit 607606f51e
1 changed files with 0 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -20,8 +20,6 @@ The cli command abratest has 3 **required arguments**:
- `--recipes_dir`: directory of all available abra recipes - `--recipes_dir`: directory of all available abra recipes
- `--output_dir`: target directory for all test results - `--output_dir`: target directory for all test results
It is also absolutely necessary, that python can import from `recipes_dir`. This can be achieved by adding the path to the `PYTHONPATH` environment variable **before** the python interpreter is started, i.e. before `abratest` is called.
### env_paths [string] ### env_paths [string]
The variable env_paths consists of one or more paths pointing at .env files. The paths are separated with ";". These .env files are actually configuration files for `abra` recipes, but `pytest-abra` uses the same files for test configuration. The variable env_paths consists of one or more paths pointing at .env files. The paths are separated with ";". These .env files are actually configuration files for `abra` recipes, but `pytest-abra` uses the same files for test configuration.
@ -72,11 +70,6 @@ The class `RunnerWordpress` will be imported via
from wordpress.tests_wordpress.runner_wordpress import RunnerWordpress from wordpress.tests_wordpress.runner_wordpress import RunnerWordpress
``` ```
which requires that python can find and import from the module `wordpress`. One way to achive this is by adding recipes_dir to the environment variable PYTHONPATH before
i.e. abratest cannot do this itself
-> workaround?
todo
# Usage # Usage
To use pytest-abra, follow these steps: To use pytest-abra, follow these steps: