Problem
download() waits for a hard-coded 100 ms timeout before validating the created download item. Framework-agnostic tests cannot control that delay without runner-specific fake timers, and the testing kit must not depend on Jest, Rstest, Vitest, Sinon, or similar libraries.
Proposed follow-up
Introduce a narrow scheduler or delay seam in production code, preserving runtime behavior while allowing deterministic tests to substitute the wait.
Until this follow-up is implemented, testing-kit integration coverage should keep only the necessary real-time success and BlockDownloadError scenarios and document that wall-clock timing is not deterministic.
Problem
download()waits for a hard-coded 100 ms timeout before validating the created download item. Framework-agnostic tests cannot control that delay without runner-specific fake timers, and the testing kit must not depend on Jest, Rstest, Vitest, Sinon, or similar libraries.Proposed follow-up
Introduce a narrow scheduler or delay seam in production code, preserving runtime behavior while allowing deterministic tests to substitute the wait.
Until this follow-up is implemented, testing-kit integration coverage should keep only the necessary real-time success and
BlockDownloadErrorscenarios and document that wall-clock timing is not deterministic.