Not run/Skipped test reporting

[knekylen-smith]

Created a reporter that notifies when tests are not executed after max time is reached.

[mcalcote]

@knekylen-smith Are there any hero instructions that can be included in the description?

[knekylen-smith]

@knekylen-smith Are there any hero instructions that can be included in the description?

To be honest I am not sure. Building it was a success and testing it would require a case where one test runs past the max time allowing for another test to not be run to see it in action.

[mcalcote]

❓ @dcruver I noticed the new classes didn't have the Codice header info. Is that required?

[jhunzik]

@knekylen-smith Are there any hero instructions that can be included in the description?

To be honest I am not sure. Building it was a success and testing it would require a case where one test runs past the max time allowing for another test to not be run to see it in action.

You could probably just set the time limit very low and a sleep that exceeds it in an itest.

[knekylen-smith]

@knekylen-smith Are there any hero instructions that can be included in the description?

To be honest I am not sure. Building it was a success and testing it would require a case where one test runs past the max time allowing for another test to not be run to see it in action.

You could probably just set the time limit very low and a sleep that exceeds it in an itest.

Good idea I will try that

[jhunzik]

Were you able to test this somehow to confirm that the new reporting works? Also, I know this project doesn't have a lot of testing, but it could help to add some units tests to prevent regression going forward.

[knekylen-smith]

I am working on testing that method that you suggested. I haven't officially made progress as I started working on something else, but I will implement the changes you guys are suggesting and also test them out today.