Basic acceptance testing for 1.1.0 deliverables
Here's what we should test to make sure that 1.1.0 behaves as advertised.
Please add more cases as needed. In each case, it would be nice to have integration testing, but we should at a minimum test these cases by hand.
Successful cases
-
Configure Arti with a single bridge, not using a pluggable transport. -
Configure Arti with a single bridge, using obfs4. (#332 (closed)) -
Configure Arti with a single bridge, using snowflake. (#333 (closed)) -
Configure Arti with multiple bridges, including a few nonexistent ones.
In each of the successful cases, we should:
- Observe that we can browse and download successfully.
- Observe that the log messages are reasonable-looking at level
info
and higher. - Observe (using instrumentation,
lsof
,tcpdump
, or similar) that Arti is only connecting as it is told.
You can get bridges from bridges.torproject.org
.
Failing cases
-
Configure arti to use bridges, using only a single nonexistent bridge. -
Configure arti to use bridges, using multiple nonexistent bridges.
In the failing cases we should:
- Observe that the log messages are reasonable-looking at level
info
and higher. - Observe (using instrumentation,
lsof
,tcpdump
, or similar) that Arti is only connecting as it is told.
Complex cases
-
Configure a list of bridges, and turn enable_bridges on and off. Make sure that Arti behaves correctly.
Edited by Nick Mathewson