Find a way to test Phoenix Presence
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
We're skipping these 4 tests since they're super flaky—they slow down the development process too much to keep. This issue is to add them back and find a way to test Phoenix Presence. (Remains to be seen how critical this is, and whether or not this will be superseded by an all-React canvas/inspector experience.)
Skipped tests from LightningWeb.WorkflowLive.UserPresencesTest to restore and fix for flakiness:
- "When workflow has many visitors, presences is detected and edit is disabled" (in canvas and inspector)
- "When workflow has many visits from same user, multiple sessions are detected and edit is disabled" (in canvas and inspector)
For testing, run with mix test test/lightning_web/live/workflow_live/user_presences_test.exs and with mix test to check for flakes.
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 with test/lightning_web/live/workflow_live/user_presences_test.exs and run mix test test/lightning_web/live/workflow_live/user_presences_test.exs to inspect the skipped presence tests and their flakiness. Restore and stabilize the listed canvas and inspector scenarios, then run mix test to confirm the suite remains reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100