Issue to be solved
In the latest cadence release, we updated the error messages to be a lot more descriptive, but the testing framework still shows pretty vague errors.
For example, if you have an incorrect argument lablel, it just shows incorrect argument label but doesn't tell you what the wrong label is or what the correct label should be. Another example is if an argument is the incorrect type, it just says mismatched types but doesn't tell you what the mismatched types are or what is expected, so it is difficult to debug errors with so little information.
Suggested Solution
Update the testing framework to surface all the information from the errors that it receives from Cadence