test: add load tests for burst throughput, worker pool, and goroutine leaks #196
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/ttheart!196
Loading…
Reference in a new issue
No description provided.
Delete branch "test/add-load-tests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Add load testing in
test/load_test.go:Why
Validate that the server handles load without resource exhaustion and the worker pool effectively limits concurrency.
Testing
go test ./test/and pre-commit passBreaking Changes
None.
Closes #129
Closes #126
Closes #127
Closes #128
Review
Solid load tests. All 3 pass with race detector. Lint and vet clean.
Results:
TestLoadBurstRequests: 100 concurrent requests in 87ms → ~1150 req/sTestWorkerPoolEnforcesConcurrency: 50 × 50ms sleep commands with pool=5, completed in ~1s (correctly limited by semaphore)TestNoGoroutineLeak: goroutines before=2 after=2, diff=0 — no leakDesign: Tests the 3 key operational concerns — burst throughput, worker pool enforcement, and goroutine lifecycle hygiene. Non-critical assertion in worker pool test (timing dominated by 1s sleep), but the exercise and logging provide diagnostic value.
No blocking issues.
APPROVED