Skip to content

Ocyss/srs-auth / .agents/skills/internal-codemap-for-srs

internal-codemap-for-srs

Verified

Route SRS and Oryx code tasks to the smallest relevant trusted codebase map and verification guidance. Use whenever support, development, debugging, review, or maintenance work requires locating, choosing, reading, modifying, testing, or verifying SRS or Oryx code. Covers the first-generation C++ origin and edge media server, its State Threads dependency, the next-generation Go server, browser publishers and players, the SRS Docker image toolchain, SRS testing, and the Oryx Go backend, React dashboard, integrated runtime, packaging, installers, releases, and tests. Use as the code-navigation dependency of parent support and development skills; the parent skill remains responsible for the user-facing workflow and result.

FileKindSize
SKILL.mdskill md6.3 KB
references/browser-clients.mdmarkdown2.2 KB
references/cpp-server.mdmarkdown23.1 KB
references/dev-docker.mdmarkdown8.3 KB
references/go-server.mdmarkdown6.8 KB
references/oryx.mdmarkdown16.9 KB
references/testing.mdmarkdown2.8 KB

references/testing.md

View on GitHub
# SRS Testing and Verification Map

Use this reference after `skills/internal-codemap-for-srs/SKILL.md` determines that a task requires tests, verification, reproduction, or benchmarking.

## C++ Media Server Verification

`trunk/src/utest/` — Unit tests for internal functions, classes, parsers, codecs, and configuration without starting SRS. Links directly against SRS source and uses mocks such as `MockSrsConfig`.

- Build and run: `cd trunk && ./configure --utest && make utest && ./objs/srs_utest`
- `srs_utest_ai01`–`ai24` — AI-written tests
- `srs_utest_manual_*` — Manually written tests
- `srs_utest_workflow_*` — Workflow and integration tests

`trunk/3rdparty/srs-bench/blackbox/` — Black-box tests against a self-managed SRS process. Each test starts SRS with `NewSRSServer()`, uses FFmpeg or FFprobe to publish and play, verifies output, and manages the server lifecycle.

- Build in `trunk/3rdparty/srs-bench/`; binary: `./objs/srs_blackbox_test`
- `rtmp_test.go` — RTMP
- `hls_test.go` — HLS
- `srt_test.go` — SRT
- `rtsp_test.go` — RTSP
- `hevc_test.go` — HEVC
- `dvr_test.go` — DVR
- `http_api_test.go` — HTTP API
- `mp3_test.go` — MP3

`trunk/3rdparty/srs-bench/srs/` — E2E protocol tests against an externally started SRS server. Uses real Pion WebRTC, RTMP, and HTTP API clients.

- Build in `trunk/3rdparty/srs-bench/`; binary: `./objs/srs_test`
- `rtc_test.go` — WebRTC
- `rtmp_test.go` — RTMP
- `srs_test.go` — General SRS workflows

`trunk/3rdparty/srs-bench/` — Performance and load benchmark, not a correctness test suite. The `./objs/srs_bench` binary simulates concurrent WHIP, WHEP, RTMP, reconnecting, DVR, plaintext RTC, and Janus workloads and reports metrics without pass/fail assertions.

`skills/srs-develop/scripts/` — Cross-component integration verification owned by the parent development skill. For every standalone SRS runtime change in either the Go proxy or C++ media server, run the complete matrix in `skills/srs-develop/references/integration-tests.md` after component-native tests. The `proxy-*` names identify the entry topology, not a proxy-only scope; these scripts also verify SRS origin, edge, Redis, and protocol interoperability.

## Verification Types

| Type | Server running? | Tests | Network | Pass/fail |
|---|---|---|---|---|
| Unit | No | Isolated internal logic | No | Yes |
| Black-box | Yes, self-managed | Whole-server behavior | Yes | Yes |
| E2E | Yes, externally managed | Protocol workflows | Yes | Yes |
| Cross-component integration | Self-managed by scripts | Proxy, origin, edge, routing, and protocol interoperability | Yes | Yes |
| Benchmark | Yes, externally managed | Performance and capacity | Yes | No, metrics only |

Use the smallest relevant test during iteration, then run the complete required suite defined by the parent development workflow before declaring the task verified.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall