CodeForPhilly / CodeForPhilly/benefit-decision-toolkit
Screener Flow E2E Tests
- Dominant language
- Java
- Stars
- 16
- Forks
- 5
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 24
Description
## User Story
As a dev working on BDT, I would like E2E tests to exist that prevent critical workflows from being broken by added changes.
## Acceptance Criteria
- Create Playwright tests for the following scenarios:
- Creating a Screener
- Creating a Benefit within a Screener
- Configuring a Check for a Screener-Benefit
- Creating a Screener Form
- Testing a Screener Form on the Preview Page
- Publishing a Screener
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the repository's Playwright test setup and the entry points for the Screener workflows. Add coverage for creating a Screener and Benefit, configuring a Check, creating and previewing a Screener Form, and publishing a Screener; done means each listed scenario runs as an end-to-end test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100