-
Notifications
You must be signed in to change notification settings - Fork 182
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
39 additions
and
0 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Dangerzone Testing | ||
|
||
Dangerzone has some automated testing under `tests/`. | ||
|
||
The following assumes that you have already setup the development environment. | ||
|
||
## Run tests | ||
|
||
Unit / integration tests are run with: | ||
|
||
```bash | ||
poetry run make test | ||
``` | ||
|
||
## Run large tests | ||
|
||
We also have a larger set of tests that can take a day or more to run, where we evaluate the completeness of Dangerzone conversions. | ||
|
||
```bash | ||
poetry run make large-test | ||
``` | ||
|
||
### Test report generation | ||
|
||
There are two kinds of reports produced: junit report, test analysis report. | ||
|
||
The Junit report is stored under `tests/test_docs_large/results/junit/` and it is composed of the JUnit XML file describing the pytest run. | ||
|
||
The second kind of report is used to analyze the errors generated during the conversion. It can only be done after test training. It is obtained by running: | ||
|
||
```bash | ||
cd tests/docs_test_large | ||
make report | ||
``` | ||
|
||
### Updating large tests | ||
|
||
The goal of these tests is to compare the current code revision with a past one and make sure there are no regressions | ||
|