Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

πŸ—‘οΈ Remove references to nightly tests #2048

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 0 additions & 32 deletions .github/workflows/nightly.yml

This file was deleted.

2 changes: 0 additions & 2 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -205,8 +205,6 @@ src = ["src", "tests"]
# Unlike Flake8, default to a complexity level of 10.
max-complexity = 15

[tool.ruff.per-file-ignores]
"tests/nightly/tools/benchmarking/test_benchmarking.py" = ["E402"]

[tool.ruff.pydocstyle]
convention = "google"
Expand Down
21 changes: 6 additions & 15 deletions tests/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,15 +98,12 @@ Here's a brief explanation of each:
from being committed to the repository. They can include things like style
checks, unit tests, and static analysis.

- `pre-merge`: These tests are run before code is merged into a main or release
branch. They are typically more extensive than pre-commit tests and may
include integration tests, performance tests, and other checks that are too
time-consuming to run on every commit.
- `unit`: These tests are run before code is merged into a main or release
branch. These are used to test individual components.

- `nightly`: These are tests that are run on a regular schedule, typically once
per day ("nightly"). They can include long-running tests, extensive test
suites that cover edge cases, or tests that are too resource-intensive to run
on every commit or merge.
- `integration`: These tests are also run before the code is merged into a main
or release branch. These test whether the components work together. These focus
mainly on training, exporting and inferring models via the API and the CLI.

- `trivy-scan`: Trivy is a comprehensive, open-source vulnerability scanner for
containers. A `trivy-scan` would check your project's dependencies for known
Expand All @@ -124,18 +121,12 @@ To run the pre-commit tests
tox -e pre-commit
```

To run the pre-merge tests
To run the unit and integration tests

```bash
tox -e pre-merge
```

To run the nightly tests

```bash
tox -e nightly
```

To run the trivy-scan

```bash
Expand Down
20 changes: 0 additions & 20 deletions tox.ini
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@ skip_missing_interpreters = true
envlist =
pre-commit
pre-merge-py{38,39,310}
nightly
snyk-scan

[testenv]
Expand Down Expand Up @@ -47,25 +46,6 @@ commands =
--ignore=notebooks/400_openvino \
--ignore=notebooks/500_use_cases/501_dobot

[testenv:nightly]
basepython = py310
passenv = {[testenv]deps}
ANOMALIB_DATASET_PATH
deps =
coverage
pytest
flaky

commands =
; 0. Install Anomalib first.
pip install .[full]

; 1. Run Coverage for the nightly tests.
coverage erase
coverage run --include=anomalib/* -m pytest tests/legacy/nightly/
coverage report -m --fail-under=33
coverage xml -o {toxworkdir}/coverage.xml

[testenv:trivy-scan]
basepython = py310
passenv = TRIVY_DOWNLOAD_URL
Expand Down
Loading