π test: optimize test suite with FakeTimers and race condition fixes #1284
+285
β76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is generated using Hephaestus.
π SPECIAL PR: Test Suite Optimization
β‘ Performance Impact
todo-continuation-enforcer.test.tsexecutor.test.tscallback-server.test.tsconcurrency.test.tsTotal time saved per test run: ~117 seconds π
π Changes
test(todo-continuation-enforcer): use FakeTimers for 15x faster testssetTimeoutwaits withfakeTimers.advanceBy()test(callback-server): fix race conditions with Promise.all and Bun.fetchBun.fetch.bind(Bun)to avoid globalThis.fetch mock interferencePromise.allpattern for concurrent operationsBun.sleep(10)cleanup in afterEachtest(concurrency): replace placeholder assertions with getCount checksexpect(true).toBe(true)with actual verificationsrefactor(config-handler): simplify planDemoteConfig creationtest(executor): use FakeTimeouts for faster testsβ Verification