@jan-molak I did a base version, but I have to ask you - are stack format library independent? Because if that's not the case, then we need parser for every one of them.

(also you tried to chat with me on serenity chat, but there were some encryption issue)

Hey@In1th - you can use the existingErrorStackParser.
Here's an example ofhow to turn aStackFrame into aFileSystemLocation

Ok I have done some refactoring and added a flag to add tests for snippets, but I don't see any integration test using console reporter. Should I add a new integration test project for that or did I miss anything?

I don't see any integration test using console reporter

Console reporter is reasonably simple and doesn't require a separate integration test module.
Have a look atConsoleReporter.spec.ts.

The best way to test it is to pump a stream of events into it and then assert on the output.

To generate a stream of events you can:

• write an example failing test with a global error (e.g. clone thePlaywright Test template)
• attach aStreamReporter inthe config and grab its output

Since the events generated by all the test runners are identical, we don't need to test the console reporter with each test runner, just with the events.

Ok, I have it!

Though it doesn't have code highlighting, and it's not so smart as playwright's.

Just need ok for this layout, still gotta figure out how to add user path to tests and how to change console reporter static methods to support snippets

@In1th - Looks awesome, great work so far!