-
Suggestion
-
Resolution: Fixed
-
None
-
None
Try and make it clearer to the end user what is happening during test optimization.
When Clover is run in debug mode, it would be ideal if a user could infer from the logs exactly why each test is either being run, or not being run.
Specifically some feedback from customers:
For instance I'd like to see which classes clover recognizes as changed ?
I'd like to know if clover thinks that a file has changed (but maybe just can't match the corresponding test-file) or if the problems start, because clover isn't even detecting a change ?
- relates to
-
CLOV-399 Test re-ordering not working for *.class patternsets
-
- Closed
-
[CLOV-400] Improve logging around Test Optimization
Workflow | Original: JAC Suggestion Workflow [ 3342178 ] | New: JAC Suggestion Workflow 3 [ 3584639 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: New Clover Workflow [ 897405 ] | New: JAC Suggestion Workflow [ 3342178 ] |
Assignee | Original: Michael Studman [ mstudman ] | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: Clover Workflow [ 896259 ] | New: New Clover Workflow [ 897405 ] |
Workflow | Original: reviewflow [ 149854 ] | New: Clover Workflow [ 896259 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Implemented [ 10025 ] | New: Resolved [ 5 ] |
Status | Original: In Progress [ 3 ] | New: Implemented [ 10025 ] |
Fix Version/s | New: 2.4.3 [ 14477 ] | |
Fix Version/s | Original: 2.5 [ 14419 ] |
Fix Version/s | New: 2.5 [ 14419 ] | |
Fix Version/s | Original: post 2.4 [ 13646 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |