Simplify test assertions based on error message strings

[dyf]

User story

As a developer, I want simpler, less brittle tests that are less sensitive to changes in error message strings.

Acceptance criteria

• [ ] Tests do not do error message string comparisons

Sprint Ready Checklist

• [ ] 1. Acceptance criteria defined
• [ ] 2. Team understands acceptance criteria
• [ ] 3. Team has defined solution / steps to satisfy acceptance criteria
• [ ] 4. Acceptance criteria is verifiable / testable
• [ ] 5. External / 3rd Party dependencies identified
• [ ] 6. Ticket is prioritized and sized

Notes

Add any helpful notes here.