testSetValueChangeEvent is slow
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.6k
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
It turns out, that searching for element (even by id), when it's not there takes a lot of time. For example for MinkSelenium2Driver it takes 5 seconds to figure out that element isn't there.
Maybe we need to change way how test works by having all elements on page upfront and just asserting their content instead.
If you run ChangeEventTest on it's own without other tests, then it's super fast. It maybe some commulative effect, that the more tests you run in a browser window the slower they run.
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 with ChangeEventTest and run it both alone and with the broader browser test suite, comparing the time spent searching for absent elements. Investigate whether accumulated browser state causes the slowdown; done means the test remains fast in the full suite while retaining its intended assertions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100