dequelabs/axe-core

axe-core timeout with mock timer in JS unit tests

Open

#3,055 创建于 2021年6月30日

在 GitHub 查看
 (9 评论) (6 反应) (0 负责人)JavaScript (5,457 star) (783 fork)batch import
help wanted

描述

Product: axe-core

Expectation: axe-core does not timeout when timer is mocked in JS unit tests

Actual: When mock timers are used with axe (e.g. jest.useFakeTimers()), tests fail with error "Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Timeout"

Motivation: Mocking timers are common in JS unit tests. Getting axe-core to work as expected even when mock timers are being used would be great. The timeout issue occurs even with other third-party mock timer libs such as @sinonjs/fake-timers - so it is not a problem just with Jest.

Something about mocking timers results in axe timeout - not sure why ?

贡献者指南

技术栈
javascript
领域
testingaccessibility
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
JavaScript unit testingaxe core basicsunderstanding of fake timers
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
Investigate how axe core uses timers (e.g., setTimeout, setInterval) in its asynchronous checks. Look at the source code in the 'lib' directory for any reliance on real timers. Review the comments in the issue for potential causes and proposed solutions. Consider if there is a need to detect mock timers or provide a configuration to disable timer dependent features.