Client Side Error Handling and Reporting

[mmarcotte]

Pre-Conditions

Acceptance Criteria

• [ ] As a sysadmin, I need to know when users experience JavaScript errors in order to know when the system fails in the browser so that I can identify and fix bugs.

Mobile Design/Considerations

Security Considerations

• [ ] Does this work make you nervous about privacy or security?
• [ ] Does this work make major changes to the system?
• [ ] Does this work implement new authentication or security controls?
• [ ] Does this work create new methods of authentication, modify existing security controls, or explicitly implement any security or privacy features?

Notes

This is one thing that HoneyBadger, Sentry, and the like do well. Essentially, we should have a clean failsafe error handler that makes an API call with the error information to an API endpoint that simply logs the error for us to discover and triage in Kibana.

Tasks

Definition of Done (Updated 8-3-20)

Product Owner

• [ ] Acceptance criteria have been met

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
• [ ] Paired w/Mark on data migration work (if applicable)
• [ ] 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)
• [ ] Module dependencies are up-to-date and are at the latest resolvable version (npm update)
• [ ] Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects
• [ ] Lambdas include CloudWatch logging of users, inputs and outputs
• [ ] Interactors should validate entities before calling persistence methods
• [ ] Code refactored for clarity and to remove any known technical debt
• [ ] Rebuild entity documentation
• [ ] Acceptance criteria for the story has been met
• [ ] Deployed to the dev environment
• [ ] Deployed to the stage environment

[adunkman]

Experienced an issue just now where a null reference was causing a user error (logged out) — this would have allowed us to see the issue before a user reported it.