Jakob Sagatowski

This is a good suggestion. I'll add it into the 1.2.0.0 milestone, but it might be pushed to 1.3.0.0, depending on whether I or any contributor has time to look...

> Duplicate of #54? Yepp. Good that someone is awake. So many comments and issues now that I think I'm getting senile. I'll leave this open and close both this...

No problems. You're welcome to implement! Just don't forget to read the [contribs](https://github.com/tcunit/TcUnit/blob/master/CONTRIBUTING.md).

Moved this to release 1.3.0.0.

@RodneyRichardson I've assigned this issue to you. If you feel you don't have the time to look into it, just un-assign yourself. Edit: https://github.com/tcunit/TcUnit/blob/master/CONTRIBUTING.md

Anyone else care to take a look into this?

Hey @NoidMasha ! It's highly appreciated that you want to look into this. I've just bumped the discussion over at #159, and hopefully we'll manage to get that PR implemented...

I'll start reviewing this PR as soon as [this PR](https://github.com/tcunit/TcUnit/pull/159) is completed/merged. Once it's merged, you will most likely need to merge from trunk again as the changes in the...

Hi @slacAWallace & thanks for this great suggestion! Although I think your suggestion makes a lot of sense (I too have tests that can take a lot of time to...

@slacAWallace Would it be a good solution/option for you to have a parameter that you can set (through the GVL_Param_TcUnit), that if it is set, if an assertion fails, the...