feat(#377): list failing tests

[renancaraujo]

Description

Adds a listing of failing tests after a test run as proposed on #377

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[felangel]

This is awesome!
Should we log them via stderr? Also what about if test descriptions are really long? Do we want to handle truncating or just let the names wrap?

[renancaraujo]

Changed to output the suite paths. I see no problem on wrapping them. What do you think?

[renancaraujo]

Also changed to output via stderr. I was going to wrap everything on red but since the Logger.error does that for us, it was not necessary.

[renancaraujo]

Changed it to have an output including line and column, as well as the path of to the suite.
The only problem is that the suite is always identified as ./test/.test_runner.dart when optimization is on (default).

Without optimization, the output is:

Failing Tests:
 - <path to cwd>/test/src/widgets/the_real_test_file.dart:30:5

With optimization, the output is:

Failing Tests:
 - <path to cwd>/test/.test_runner.dart:30:5

[renancaraujo]

Update: Changed to retrieve the test location from the stack trace. In this way, the right path is recovered regardless of the optimization being true of false .
Also added a prefix to show if the test failed or resulted in an error:

Failing Tests:
 - [FAILED] test/example_test.dart 4:5
 - [ERROR] test/example_test.dart 5:5

[felangel]

[felangel]

LGTM 💯