codeforboston / codeforboston/cliff-effects
Write tests for prompt-related components
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
It's just really annoying to keep trying to test the prompts every time there's a change.
There are two prompts. One is the feedback form, always triggered by the feedback prompt. It's always the same. The other is the feedback prompt, which is triggered by almost everything else. The text in the feedback prompt and the callbacks when its buttons are pressed can change, though, depending on what triggered it to show.
- [ ] Ensure listeners trigger prompt that asks user for feedback. Listeners:
- [ ] Error
- [ ] Feedback button
- [ ] Reset client fixed button
- [ ] Reset client 'Predictions' button (make sure same as other reset button)
- [ ] React click to navigate to Home page
- [ ] Correct functionality for prompt asking users for feedback (text and buttons) after triggered by:
- [ ] React click to navigate to Home page: Leave, Stay, Feedback
- [ ] Error: Reset, Stay, Feedback
- [ ] Reset client fixed button: Reset, Stay, Feedback
- [ ] Reset client 'Predictions' button (make sure same as other reset button): Reset, Stay, Feedback
- [ ] Feedback prompt
- [ ] Triggered by feedback button
- [ ] Submits feedback
- [ ] Cancel shows prompt that triggered it, if there was one, or goes back to client otherwise
- [ ] Listeners trigger browser prompts:
- [ ] Browser leave
- [ ] Browser reload
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names prompt-related components and listeners but no files or existing test entry points. Start by locating the feedback and browser prompt components and the listed Error, reset, navigation, feedback-button, leave, and reload listeners. Done means tests cover each trigger, prompt text and button callbacks, feedback submission and cancellation, and browser prompts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100