Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

test: move crate-local integration tests into testsuite

未关闭
#2,109 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
testing

调研方向

Read testsuite/AGENTS.md and inspect the listed crate-local tests/ directories alongside testsuite/Cargo.toml. Choose one directory for a separate migration, starting with its test targets and dependencies; the devolutions-gateway tests may require making __debug__ knobs reachable. Done means the tests live in the testsuite crate's single test binary and still exercise a shipped binary or a public library API.

由索引模型根据 Issue 内容生成。

描述

testsuite/AGENTS.md states the policy: new integration tests go in the testsuite crate's single test binary, so the suite links once and runs as one process, and a test either drives a shipped binary or exercises the public API of a library crate under crates/.

Nine crates still carry Cargo-discovered tests/ directories that predate the policy; only testsuite/Cargo.toml sets autotests = false:

  • devolutions-gateway/tests/ (config.rs, dvls_compatibility.rs, jmux.rs, preflight.rs, token_security.rs, traffic.rs, webapp.rs)
  • crates/transport/tests/
  • crates/jmux-proto/tests/
  • crates/jmux-proxy/tests/
  • crates/http-client-proxy/tests/
  • crates/agent-tunnel-proto/tests/
  • crates/traffic-audit-libsql/tests/
  • crates/video-streamer/tests/
  • crates/devolutions-gateway-ai/tests/

Migration is deliberately deferred. Until it happens, the policy applies to new tests: add them to testsuite, not to a crate's own tests/.

Moving each directory is a candidate for its own pull request, since the devolutions-gateway tests in particular link the binary crate and may need __debug__ knobs to become reachable from outside.

[!NOTE]
Human-tuned, LLM-assisted content.

主要语言
Rust
星标
164
派生
30
平均合并
1 天 13 小时
30 天内合并 PR
84

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Devolutions/devolutions-gateway 的其他 Issue

查看 Devolutions/devolutions-gateway 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。