matomo-org / matomo-org/matomo-for-wordpress
run wdio in docker container with firefox
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 145
- Forks
- 35
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
Right now, wdio (used for e2e tests) is run outside of a container, so the version of the browser it uses depends on the host environment. Which means running them locally will result in screenshots that are slightly different from screenshots in github actions.
To speed up development w/ regard to fixing/writing e2e tests in the future, we should add an image with the needed browsers to a docker image, and run wdio through it. This will ensure parity with github actions when running the tests locally (or when different developers run the tests on different OSes/machines/etc.).
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
The issue concerns the wdio end-to-end test runner and the Docker image used for local and GitHub Actions execution; start by locating those configuration and workflow entry points. Verify that the container includes the required Firefox browser and that wdio runs through it, with local screenshots matching GitHub Actions screenshots.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100