Improve unpaid overage feature spec coverage
Problem
@vij
:
question: this looks to have gone from the singular
has_unpaid_overage
to the plural, but the frontend changes look to still use the singular - have I missed something or does this mean the unpaid overages logic is not working / will always befalse
? If so, I think that probably means we're missing some feature/E2E test coverage as it wasn't picked up already?🤔
Changing the backend attribute name for has_unpaid_overages
without changing the associated frontend name did not cause test failures.
Proposal
Add additional testing to validate the behavior when the user has unpaid overages so that this type of bug would be caught.
Edited by Laura Callahan