cholly75
commented
2 years ago More detailed test cases to be added based on solution approach; the high level test cases are essentially DAWSON workflows as they operated today.
Closed cholly75 closed 2 years ago
cholly75
commented
2 years ago More detailed test cases to be added based on solution approach; the high level test cases are essentially DAWSON workflows as they operated today.
rachelschneiderman
commented
2 years ago Court operating hours: 8am-5pm EST
DAWSON must be up until midnight on the weeknights to be available to folks trying to meet filing deadlines
Court does not make any guarantees that its systems are available on the weekends when the court is open.
cholly75
commented
2 years ago Chris to write spike story for slice of this - starting with petitioner uploading petition flow to see what changes would need to be made for eventual solution.
Chris to confirm with court what intermediate measures might be acceptable in terms of getting to the "gold standard"
Both stories to be added to the epic.
As a DAWSON user, so that I can use the application any time that I require, I need to be able to continue to use the application during deployment activities.
DAWSON deployments currently interrupt user activity at the end of deployment activities. By allowing users to continue working during and after deployments, we can provide both a better user experience and more frequent deployment opportunities.
This story should provide continuous service to a user during and post-deployment activities.
Pre-Conditions
Acceptance Criteria
Notes
Tasks
Test Cases
Write Operations
Read operations
Operation-Agnostic Test Cases
Data format change: create data prior to deployment that will be affected by a format change in the migration step of the deployment. Submit the data during the time after color-switch but before the old color is taken offline. Confirm that the data is migrated properly into the new format in the new color post-deployment.
User token refresh: Establish a user session prior to the deployment; time this such that the token refresh period occurs during the appropriate time during the deployment/migration. Confirm that the token refresh takes place in a manner that does not interrupt the user experience.
Test with failed/interrupted deployment scenario
Story Definition of Ready (Created on 9/26/21)
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 10-6-21)
Product Owner
UX
Engineering