python-visualization / python-visualization/folium
Use Playwright for integration tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 2.3k
- Avg merge
- 17h 22m
- Merged PRs (30d)
- 11
Description
We currently use Selenium to test the examples in our documentation for errors. This is useful, but it doesn't catch features silently failing. This happened in our v0.19.0 release.
We need tests that actually verify the expected elements are visible on the page. This requires work: for each example we have to define what elements are expected, possibly after clicking on some other element.
I'd like to try to use Playwright for this. It looks pretty easy to use. It also integrates with Pytest. I'll give this a shot on a couple examples to see if this approach works well. If so, we can apply it to all examples.
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 reviewing the existing Selenium-based integration tests for the documentation examples and how they run with Pytest. Try Playwright on a couple of examples, defining the expected visible elements and any required clicks. Done means the approach detects silently failing features and can be applied consistently to all examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, python
- Domain
- documentation, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100