This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #7 from brain-score/pytest-mark
use pytest.mark instead of pytest.config
- Loading branch information
Showing
6 changed files
with
30 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Unit Tests | ||
## Markers | ||
Unit tests have various markers that denote possible issues in the travis build: | ||
|
||
* **private_access**: tests that require access to a private ressource, such as assemblies on S3 (travis pull request builds can not have private access) | ||
* **memory_intense**: tests requiring more memory than is available in the travis sandbox (currently 3 GB, https://docs.travis-ci.com/user/common-build-problems/#my-build-script-is-killed-without-any-error) | ||
|
||
Use the following syntax to mark a test: | ||
``` | ||
@pytest.mark.memory_intense | ||
def test_something(...): | ||
assert False | ||
``` | ||
|
||
To skip a specific marker, run e.g. `pytest -m "not memory_intense"`. | ||
To skip multiple markers, run e.g. `pytest -m "not private_access and not memory_intense"`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.