ooni-probe-cli/QA
Simone Basso 596eab4a42
fix(QA): rundocker.sh => rundocker.bash
H/T @lorenzoPrimi
2022-09-08 10:09:30 +02:00
..
.dockerignore refactor: enable QA tests and jafar self test (#208) 2021-02-03 13:20:37 +01:00
.gitignore QA: refactor, cleanup, fix, and simplify (#938) 2022-09-07 14:55:36 +02:00
common.py QA: refactor, cleanup, fix, and simplify (#938) 2022-09-07 14:55:36 +02:00
dockermain.sh QA: refactor, cleanup, fix, and simplify (#938) 2022-09-07 14:55:36 +02:00
minioonilike.py refactor: enable QA tests and jafar self test (#208) 2021-02-03 13:20:37 +01:00
README.md fix(QA): rundocker.sh => rundocker.bash 2022-09-08 10:09:30 +02:00
rundocker.bash QA: refactor, cleanup, fix, and simplify (#938) 2022-09-07 14:55:36 +02:00
webconnectivity.py fix(probeservices): use api.ooni.io (#926) 2022-09-02 16:48:14 +02:00

Quality Assurance scripts

This directory contains quality assurance scripts that use Jafar to ensure that OONI implementations behave. These scripts work with miniooni.

Run QA using a docker container

Run test in a suitable Docker container using:

./QA/rundocker.bash $nettest

Note that this will run a --privileged docker container.

Diagnosing issues

The Python script that performs the QA runs a specific OONI test under different failure conditions and stops at the first unexpected value found in the resulting JSONL report. You can infer what went wrong by reading the output of the miniooni command itself, which should be above the point where the Python script stopped, as well as by inspecting the JSONL file on disk. By convention such file is named $nettest.jsonl and only contains the result of the last run of $nettest.