Description
When having assertion errors in tests, the highest stack frame is used as error location to be displayed.
But often there are irrelevant frames like. Custom assertion functions or helpers used in the tests. Due to this it often happens that error locations have to be traced back to test level.
Describe the solution you'd like
We need an option allowing customization of the stack frames being considered. For now a simple approach should be added: a list of regexes which are then checked in:
https://github.com/CoderLine/mocha-vscode/blob/main/src/runner.ts#L657
It should be a dedicated option which can easily be added to .vscode/settings.json
Describe alternatives you've considered
No response
Description
When having assertion errors in tests, the highest stack frame is used as error location to be displayed.
But often there are irrelevant frames like. Custom assertion functions or helpers used in the tests. Due to this it often happens that error locations have to be traced back to test level.
Describe the solution you'd like
We need an option allowing customization of the stack frames being considered. For now a simple approach should be added: a list of regexes which are then checked in:
https://github.com/CoderLine/mocha-vscode/blob/main/src/runner.ts#L657
It should be a dedicated option which can easily be added to
.vscode/settings.jsonDescribe alternatives you've considered
No response