dequelabs/axe-core

axe-core timeout with mock timer in JS unit tests

Open

#3,055 opened on 2021年6月30日

GitHub で見る
 (9 comments) (6 reactions) (0 assignees)JavaScript (5,457 stars) (783 forks)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
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.
axe-core timeout with mock timer in JS unit tests · dequelabs/axe-core#3055 | Good First Issue