WordPress / WordPress/openverse
Consider SSR vs. CSR in end-to-end tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 380
- Forks
- 290
- Avg merge
- 3h 17m
- Merged PRs (30d)
- 8
Description
Problem
We often have rendering issues that involve discrepancies between the client-side rendered page and the server-rendered version, due to the multiple ways of fetching data with Nuxt and Vue.
Description
Could we find a way to run all of our e2e tests in both SSR and CSR, and compare those images? Maybe something simple like a wrapper that runs each test twice, once directly on the route being tested and once on the route being tested after a client-side navigation from a different page. There might be even simpler ways of doing this that don't involve test changes or setup code.
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 the existing e2e tests and their setup, then trace a route loaded directly versus after client-side navigation. Done means the suite can exercise both SSR and CSR paths and compare their rendered images without requiring each test to be rewritten.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100