| Reporter |
Ryan Leach (ryantheleach)
|
|---|---|
| Created | Apr 9, 2018 10:18:58 AM |
| Updated | Apr 9, 2018 10:18:58 AM |
| Subsystem | No Subsystem |
| Assignee | Unassigned |
| Priority | Normal |
| State | Submitted |
| Type | Feature |
| Fix version | No Fix versions |
| Affected versions | No Affected versions |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
With unit testing, I came across the idea of retaining the output of the last successful/unsuccessful test.
Often when I've done some heavy refactoring, the unit tests that were previously passing will fail, But I have no idea how, or why, even whilst debugging.
What ends up happening is that I need to swap branches back to the previous commit, possibly stashing my changes if they arn't commit ready.
Run the tests, debug and store the log files generated by the test, then swap back to the failing test cases run, debug, compare.
What would be undoubtedly awesome UX would be if the last test results for unsuccessful, and successful were cached, and viewable in the test editor.
It can save people in my shoes a LOT of time, and change the way they do test logging for the better.