write-sglang-test

SGLang CI tests use CustomTestCase to standardize test creation. You register the test at module scope using the appropriate register_*_ci call, ensuring consistent test layouts and proper tooling coverage across the SGLang repository.

To register E2E tests for SGLang CI pipelines, place the test files under the test directory and use register_*_ci calls at module scope. This enforces repository guidelines for test placement and workflow integration.

Server fixtures in SGLang unit testing provide the necessary server environment for test execution. They are integrated into test files alongside model selection configurations to ensure consistent and repeatable server-based testing workflows.

Yes, mock testing is supported within SGLang CustomTestCase workflows. The skill documents best practices for integrating mock testing alongside server fixtures and model selection to validate test scenarios without full deployment.

The correct test placement structure for SGLang repository tests requires placing unit tests and E2E tests under the designated test directory. All tests must be properly registered with register_*_ci calls to integrate with CI pipelines.

SGLang server-based tests require server fixtures and model selection configurations defined within the test files. The testing framework uses CustomTestCase to enforce rules and provide templates, ensuring consistent test layouts without external dependencies.