aboutsummaryrefslogtreecommitdiff
path: root/tests/chutney/test
Commit message (Collapse)AuthorAgeFilesLines
* integration-e2e-shadow: move artifacts into nodes dirJim Newsome2026-07-231-1/+1
| | | | | This keeps everything together and avoids clobbering previous artifacts, since chutney already creates a unique nodes dir in every run.
* chutney CI: add hidden servicesJim Newsome2026-04-021-1/+4
|
* chutney test: enable loggingJim Newsome2026-04-021-0/+2
|
* chutney test: use unittest frameworkJim Newsome2026-03-091-103/+125
| | | | | | This organizes the code a bit better and gives nicer output. It also separates individual test cases and subcases, continuing to try to complete other tests when one fails instead of exiting.
* chutney test: bump CHUTNEY commit and update to test all endpointsJim Newsome2026-03-041-50/+61
| | | | | | | chutney replaced Node.socksport (a single optional port) with Node.socksport_endpoints (a sequence of bound addresses and ports). Update for compatibility, and test all of the exposed endpoints where relevant.
* chutney test: test all relevant clients, not just an arbitrary oneJim Newsome2026-03-041-53/+56
|
* chutney test: don't shell out to chutney for 'verify' testJim Newsome2026-03-041-2/+3
|
* chutney test: use chutney module to inspect NetworkJim Newsome2026-03-041-29/+31
| | | | | | | | | | | * Gets rid of shelling out to jq. We could also accomplish that with the json module, but this way also gives us: * Better error detection and handling. In particular this lets mypy statically detect trying to access fields of the wrong name or type. It will also make it easier to bump to the latest chutney, which has replaced `socksport` with `socksport_endpoints`, which would be more difficult to work with as json, especially via `jq`.
* chutney test: move some common functionality into a moduleJim Newsome2026-03-041-10/+6
|
* chutney test: convert to pythonJim Newsome2026-03-041-37/+101
|
* Bump chutneyJim Newsome2026-01-211-2/+1
| | | | Bump chutney, and migrate to CLI changes introduced in chutney!101
* chutney ci: make arti-bench bin configurableJim Newsome2025-10-091-1/+2
| | | | Also search several candidate paths.
* chutney CI: store and use jq pathJim Newsome2025-09-291-3/+4
| | | | | | Since we're validating the presence of jq, we might as well handle it consistently with the other dependencies and provide a way to specify where it is.
* chutney ci: remove CHUTNEY_BIN env variableJim Newsome2025-09-291-2/+2
| | | | | | This wasn't a pre-existing environment variable, and now it can be set via command-line if it needs to be overridden. I don't see much reason to use an environment variable here.
* chutney CI: move benchmark from e2e script to `test` scriptJim Newsome2025-09-291-0/+7
|
* chutney ci: move "chutney verify" test from `setup` to `test`Jim Newsome2025-09-291-0/+13
| | | | | | | | | It made sense to have this as part of the setup when the chutney network itself didn't include arti; i.e. this used to be just validating the non-chutney tor network before adding chutney nodes. Now that the chutney network natively includes arti nodes, `chutney verify` is testing those nodes; i.e., testing arti.
* chutney ci test: use chutney net's arti clientJim Newsome2025-06-051-4/+12
|
* chutney dns test: handle multiple addressesJim Newsome2025-06-051-1/+3
|
* Add `tests/chutney/integration-e2e-shadow`Jim Newsome2024-09-181-0/+1
| | | | | This is a wrapper script for running `tests/chutney/integration-e2e` under shadow.
* chutney test: add option to skip tests incompatible with shadowJim Newsome2024-09-181-5/+17
|
* chutney: don't hard-code expected IP address for example.comJim Newsome2024-09-181-2/+6
| | | | | | It looks like it changed at some point. Rather than hard-coding, just do the lookup locally and compare the tor-lookup result against that.
* shell: use /usr/bin/env instead of absolute pathsEmil Engler2023-01-251-1/+1
| | | | | | | | | | This commit changes the shebang in all shell scripts from absolute paths (such as `/bin/bash` or `/usr/bin/python3`) to the `/usr/bin/env` binary with the accompanying interpreter as it's argument. The reason for this are as follows: - NixOS cannot work with absolute paths - BSD systems install their packages in /usr/local/bin
* make almost all scripts use bash and set euo pipefailtrinity-1686a2022-05-251-1/+3
|
* Use port 35353 for testing, not 5353.Nick Mathewson2022-03-151-2/+2
| | | | | Apparently 5353 is commonly used for mDNS, and so counts as "already in use" on many consumer machines.
* comment AAAA test and explain why it's disabledtrinity-1686a2022-03-141-1/+4
|
* add integration test and fill semver_statustrinity-1686a2022-03-141-0/+6