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