Tests to write
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] [Browser testing -> UI](https://circleci.com/docs/2.0/project-walkthrough/#install-and-run-selenium-to-automate-browser-testing)
- [ ] Overlay tab loading/present
- [ ] Trigger element for modal present on page (e.g. button w/click listener)
- [ ] Modal opens/loads
- [ ] Form successfully submits
- [ ] Analytics events successfully fire
- [ ] [Cookie set when successful submit](https://github.com/GSA/recruiter/projects/1#card-2671096)
- [ ] How to check that partner agencies haven't disturbed GTM code?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or existing test entry points. Start by locating the browser-test setup and the embeddable form flow, then trace the UI, modal, submission, cookie, analytics, and Google Tag Manager paths. Done means the listed browser scenarios are covered, including checking that partner agencies do not disturb GTM code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- analytics, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100