-
Sub-task
-
Resolution: Fixed
-
Low
-
None
-
None
Analyse how a test named like:
def "my test name"
is converted to a method like:
$spock_feature_1_0
It's being done during AST transformation I guess.
Check how it's possible to either:
- reverse engineer this behaviour i.e. get a back-ward mapping $spock_feature_1_0 -> def "my test name" or
- reproduce this behaviour, i.e. instrument methods in such order/way that Clover could 'calculate' the same method name
[CLOV-1360] Analyse how tests are converted by Spock
Workflow | Original: New Clover Workflow [ 897473 ] | New: New Clover Workflow - Restricted [ 1474018 ] |
Workflow | Original: Clover Workflow [ 896365 ] | New: New Clover Workflow [ 897473 ] |
Workflow | Original: reviewflow [ 553955 ] | New: Clover Workflow [ 896365 ] |
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 ] |
Attachment | New: class_annotation.png [ 104455 ] | |
Attachment | New: method_annotations.png [ 104456 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |