recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(cfold): canonicalize custom test layout
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-06-12 16:08:18 +00:00
parent 87928a9096
commit 44e02425ab
110 changed files with 306 additions and 241 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
tests/mumble/PARITY.md
View File

@ -12,9 +12,9 @@ publishes 64738 on the cc-ci host so the on-host (cc-ci-run) protocol tests conn
| recipe-maintainer test (`recipe-info/mumble/tests/`) | what it verifies | cc-ci test | same thing? |
|---|---|---|---|
| `health_check.py` | mumble server listening on TCP 64738 | `functional/test_tcp_health.py` | yes — TCP connect to 64738 (host-published) |
| `mumble_connect.py` | full TLS protocol handshake: TLS connect, server Version, auth accepted (no Reject), channel list present, ServerSync handshake completes, welcome text | `functional/test_protocol_handshake.py` (+ `functional/_mumble_proto.py`, adapted from the corpus's stdlib protobuf/protocol code) | yes — same handshake; asserts tls_connect + version + auth_accepted + channel presence + ServerSync |
| `web_client.py` | mumble-web client reachable over HTTPS, HTTP 200, page contains `Mumble` + `config.js`, valid HTML | `functional/test_web_client.py` | yes — same 200 + body markers (`Mumble`, `config.js`, `<!DOCTYPE html>`) |
| `health_check.py` | mumble server listening on TCP 64738 | `custom/test_tcp_health.py` | yes — TCP connect to 64738 (host-published) |
| `mumble_connect.py` | full TLS protocol handshake: TLS connect, server Version, auth accepted (no Reject), channel list present, ServerSync handshake completes, welcome text | `custom/test_protocol_handshake.py` (+ `custom/_mumble_proto.py`, adapted from the corpus's stdlib protobuf/protocol code) | yes — same handshake; asserts tls_connect + version + auth_accepted + channel presence + ServerSync |
| `web_client.py` | mumble-web client reachable over HTTPS, HTTP 200, page contains `Mumble` + `config.js`, valid HTML | `custom/test_web_client.py` | yes — same 200 + body markers (`Mumble`, `config.js`, `<!DOCTYPE html>`) |
No recipe-maintainer mumble test is omitted — all three are ported. No `DECISIONS.md` non-port
entry is needed for mumble.
@ -27,10 +27,10 @@ prove our deploy-time configuration propagated into the running murmur server an
delivered over the real protocol (version-independent — they assert OUR configured markers, not
hard-coded upstream values):
1. `functional/test_welcome_text_roundtrip.py` — deploys with a unique `WELCOME_TEXT` marker
1. `custom/test_welcome_text_roundtrip.py` — deploys with a unique `WELCOME_TEXT` marker
(`recipe_meta.EXTRA_ENV` → `MUMBLE_CONFIG_WELCOMETEXT`); asserts that exact marker surfaces in the
server's ServerSync `welcome_text` delivered to a connecting client. (create config → read back.)
2. `functional/test_server_config_limits.py` — deploys with a distinctive non-default `USERS=42`
2. `custom/test_server_config_limits.py` — deploys with a distinctive non-default `USERS=42`
(max-users cap → `MUMBLE_CONFIG_USERS`); asserts the server's ServerConfig message reports
`max_users == 42` (and a well-formed `allow_html`), proving the recipe wires deploy-time
server-capacity policy into the running server.

0
tests/mumble/functional/_mumble_proto.py → tests/mumble/custom/_mumble_proto.py
View File

0
tests/mumble/functional/test_protocol_handshake.py → tests/mumble/custom/test_protocol_handshake.py
View File

0
tests/mumble/functional/test_server_config_limits.py → tests/mumble/custom/test_server_config_limits.py
View File

0
tests/mumble/functional/test_tcp_health.py → tests/mumble/custom/test_tcp_health.py
View File

0
tests/mumble/functional/test_web_client.py → tests/mumble/custom/test_web_client.py
View File

0
tests/mumble/functional/test_welcome_text_roundtrip.py → tests/mumble/custom/test_welcome_text_roundtrip.py
View File