Check unit tests for unfinished expect()
assertions
#227
Labels
[practice] engineering
Engineering related work
[type] debt
Tech debt, refactors, maintenance issues
Milestone
In doing some updates to the unit tests I couldn't figure out why some succeeded even when they should fail. Turned out they had just a bare
expect(thing)
rather than for exampleexpect(thing).to.be.true
so it wasn't testing athing
. The case I found was in SubmitController but it's a really easy mistake to make given the API and I found at least one other case in SchemaForm where the same thing happens. We should review and fix all the cases and may need to push some issues back to vets.gov as a courtesy if they've forked functionality.The text was updated successfully, but these errors were encountered: