Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Configure Pytests on Feature Flags (#764)
### Feature or Bugfix <!-- please choose --> - Bugfix ### Detail - Move `tests/modules/test_loader.py` to `tests/base/test_loader.py` as originally the test_loader tests were being excluded because of the `ignore_module_tests_if_not_active()` function in `tests/conftests.py` - Added `@pytest.mark.skipif(...)` decorators to skip tests if the module features are not enabled in `config.json` - Originally this was failing on some of the `test_dataset_location.py` tests when `modules.datasets.features.file_actions` was set to `False` in `config.json` ### Relates ### Security Please answer the questions below briefly where applicable, or write `N/A`. Based on [OWASP 10](https://owasp.org/Top10/en/). N/A ``` - Does this PR introduce or modify any input fields or queries - this includes fetching data from storage outside the application (e.g. a database, an S3 bucket)? - Is the input sanitized? - What precautions are you taking before deserializing the data you consume? - Is injection prevented by parametrizing queries? - Have you ensured no `eval` or similar functions are used? - Does this PR introduce any functionality or component that requires authorization? - How have you ensured it respects the existing AuthN/AuthZ mechanisms? - Are you logging failed auth attempts? - Are you using or adding any cryptographic features? - Do you use a standard proven implementations? - Are the used keys controlled by the customer? Where are they stored? - Are you introducing any new policies/roles/users? - Have you used the least-privilege principle? How? ``` By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
- Loading branch information