Retro Improvement: No blockers with testing w/prod-like data

[mariahkannenberg]

As a development team, so that we can move work through the pipeline more quickly, I need to test stories with prod-like data without being blocked.

Pre-Conditions

Acceptance Criteria

• Stories are not blocked from being tested in a Court environment with prod-like data by the end of Sprint 77.

Notes

• Two pieces to this - batches get clogged + we only have 1 migration environment

Tasks

• Figure out why stories are taking more than a few days - deep dive
• Explore having a different environment with prod-like data to test

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:

• [ ] Be immediately actionable for the development team
• [ ] Be focused on users
• [ ] Include a narrative. “As a , so that I can __, I need _____.”
• [ ] Include user-centric acceptance criteria that expresses the users' needs
• [ ] Include user-centric testing scenarios
• [ ] Include preconditions (story dependencies)
• [ ] Not include design or technical solutions
• [ ] Include non-standard testing, deployment, documentation, browser, mobile or security requirements, as well as any requirements for 3rd-party integrations

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 4-14-21)

Product Owner

• [ ] Acceptance criteria have been met and validated on the Court's migration environment
• [ ] Add scenario to testing document, if applicable (https://docs.google.com/spreadsheets/d/1FUHKC_YrT-PosaWD5gRVmsDzI1HS_U-8CyMIb-qX9EA/edit?usp=sharing)

UX

• [ ] Business test scenarios to meet all acceptance criteria have been written
• [ ] Usability has been validated
• [ ] Wiki has been updated (if applicable)
• [ ] Story has been tested on a mobile device (for external users only)

Engineering

• [ ] Automated test scripts have been written
• [ ] Field level and page level validation errors (front-end and server-side) integrated and functioning
• [ ] Verify that language for docket record for internal users and external users is identical
• [ ] New screens have been added to pa11y scripts
• [ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• [ ] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
• [ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• [ ] Interactors should validate entities before calling persistence methods
• [ ] Code refactored for clarity and to remove any known technical debt
• [ ] Acceptance criteria for the story has been met
• [ ] Deployed to any Flexion environment for UX Review
• [ ] Deployed to the Court's migration environment

[mariahkannenberg]

https://app.zenhub.com/files/152320868/c6fa24b1-0440-44c6-9498-4d833b0b9c5b/download

[mariahkannenberg]

https://app.zenhub.com/files/152320868/384ef714-b8ac-4e9f-92d3-693839a8f9a3/download

[codyseibert]

just documenting instances of this happening: we encountered two blocked stories on batch 11 that couldn't get deployed to court's migration because they were blocked by batch 10 today. Stories #8955 and #9011 10/20/2021