gsadmin/Firelink
1
0
Fork 0
mirror of https://github.com/nimbold/Firelink.git synced 2026-08-22 00:46:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(ci): use Windows-compatible Torrent RPC integration test

Browse Source
This commit is contained in:
NimBold
2026-08-01 20:09:57 +03:30
parent 92092e9844
commit bb64c4cd52
5 changed files with 106 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src-tauri/tests/README.md
+7 -6
View File
@@ -36,9 +36,9 @@ npm run smoke:torrent
Use `node scripts/smoke-torrent.js --binary /path/to/aria2c` when validating a
packaged or target-specific Aria2 binary.
Run the HTTP-boundary Torrent probe harness with a controllable local JSON-RPC
server. It drives the production Aria2 RPC client through scripted status,
outage, race, cancellation, and daemon-termination cases:
Run the HTTP-boundary Torrent RPC integration test. It drives the production
Aria2 RPC client through a local JSON-RPC server and verifies successful
requests plus HTTP gateway errors:
```sh
npm run test:torrent:rpc
@@ -51,6 +51,7 @@ npm run smoke:torrent:failure-paths
```
Native CI runs this failure-path smoke after staging the target-specific
bundled engines on macOS, Windows, and Linux. Windows also runs the filtered
HTTP-boundary RPC harness explicitly because its general Rust job compiles the
library tests without executing them.
bundled engines on macOS, Windows, and Linux. Windows runs this RPC
integration test through its target-qualified `cargo test --tests` step;
the general Rust job compiles the library tests without executing the
known-broken Tauri library harness.