write-sglang-test

Writing SGLang unit tests requires using CustomTestCase, appropriate mocks, and standard test utilities to validate engine features. This approach ensures correct test placement, follows repository conventions, and maintains defensive resource cleanup to prevent leaks.

Adding SGLang feature tests to CI requires literal CI registration with the correct backend, suite, estimated runtime, and model settings. You must configure nightly settings and select the smallest suitable model or mock strategy to ensure reliable integration.

Use mocked unit tests for isolated engine features or middleware to ensure speed, and server-based end-to-end tests for request routing or server APIs. Choose JIT kernel tests for hardware-specific operations and performance tests for benchmarking model behavior.

SGLang server tests leak resources when avoiding CustomTestCase or defensive cleanup protocols. Applying standard SGLang server fixtures and proper lifecycle handling prevents flaky failures by ensuring all test resources are correctly released after execution.

Yes, you can use standard SGLang test utilities for JIT kernel tests by applying CustomTestCase and appropriate fixtures. This ensures correct test placement, defensive resource cleanup, and proper CI registration with suitable models and backends.

The best way to prevent flaky failures in SGLang integration tests is implementing CustomTestCase with server fixtures and defensive resource cleanup. This manages test lifecycles properly and ensures reliable CI execution without resource leaks.