RedHatQE / RedHatQE/widgetastic.core
Two different modes: pedantic(slow)/lax(fast)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 37
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
I was thinking about this before, widgetastic is currently very pedantic with page checking so it is relatively slow. There is a possibility to keep these check obligatory only after events like clicking and the rest would be invoked only if the selenium step triggers an error - like element lookup or such - and after the check the step would be repeated once more. The modes would be switchable.
This should only probably concern changes inside Browser class.
Contributor guide
No contributing guide indexed for this repository
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 inspecting the Browser class and how page checking is currently triggered around Selenium steps. Clarify the intended pedantic and lax behavior, including when checks run and whether a failed step is retried. Done would require an agreed, switchable implementation limited to the Browser class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100