cloudfour / cloudfour/pleasantest

Consider using visibility checks from actionability within toBeVisible

Open
#74 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
175
Forks
2
Avg merge
1m
Merged PRs (30d)
1

Description

The checks that toBeVisible performs are pretty limited because it is designed to work with jsdom, where there is no real rendering engine. Since we have the benefit of having a real browser, we could make the checks more complete by replacing the implementation. It would probably even be possible to share the implementation with our visibility checks from the actionability checks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the toBeVisible implementation and the visibility checks used by actionability checks. Compare their current behavior in a real browser, then determine whether the checks can be shared; done means toBeVisible performs the more complete browser-based visibility checks without losing its existing purpose.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
testing
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.