-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trial Sessions Page: Public View #10460
Comments
UX Notes: |
Test Cases1) Public user can now accesses the new Scheduled Trial Sessions Page; page loads and matches the mockup.
Expected Results:
2) Public user applies filters; results list displays the correct data based on the filters selected.Part 1
Expected Results:
*Repeat this test but instead choose Remote Part 2
Expected Results:
Part 3
Expected Results
*Repeat this test, but add in additional filters for Location and Judge 3) Public user applies multiple filters; results list displays correct data; User manually removes some of the filters by clicking on the "x" in the pill; results list refreshes with the updated filters
Expected Results:
*Repeat this test by removing multiple filters by clicking on the x in the pill container. Results list will update each time a filter is removed. 4) Repeat the tests above on a mobile device
|
As a member of the public, so that I can easily see what trial sessions are upcoming, I need a public view of the calendared Trial Sessions.
Currently, the Court maintains a web page populated with PDF files to inform the public of scheduled trial sessions. Since this information can become outdated over time and require re-publishing new files when a change is made and since the Trial Sessions in DAWSON are always up to date, we would like a public-facing version of the Trial Sessions page to be made available in place of the current web page.
Note that this story and #10461 should be released together; a feature flag may be necessary to facilitate separate deployments for each.
Pre-Conditions
Acceptance Criteria
Notes
Tasks
Test Cases
Story Definition of Ready (updated on 12/23/22)
The following criteria must be met in order for the user story to be picked up by the Flexion development team.
The user story must:
Process:
Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.
Definition of Done (Updated 5-19-22)
Product Owner
UX
Engineering
efcms-local.json
, 3 local s3 files corresponding to that docketEntryId have been added toweb-api/storage/fixtures/s3/noop-documents-local-us-east-1
test
environment if prod-like data is required. Otherwise deployed to anyexperimental
environment.staging
environment.The text was updated successfully, but these errors were encountered: