Dash Integration tests use `time.sleep` instead of timeouts
Open
Nobody has claimed this yet.
feature
P2
testing
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Dash integration tests are taking longer than they need to because they use time.sleep instead of timeouts to wait for elements to appear on the page.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Dash integration tests that call time.sleep and review how those tests wait for page elements. Replace the fixed sleeps with element-appearance timeouts, then run the affected integration tests; done means the waits are timeout-based and the tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100