Logging block labels in real-time

[Brian Stewart]

Hi, all! Is it possible to turn on real-time logging (not post-run reports) that display the block labels? Here is an example of what I'm trying to do:

def 'test block-level logging'() {
    given: 'some setup'
    def x = 5
   
    when: 'action is taken'
    x++

    then: 'result matches expected'
    x == 6
}

I would like this spec to produce logging output something like this (with or without the "given"/"when"/"then"):

given: some setup
when: action is taken
then: result matches expected

I looked at some extensions, but only saw hooks for before-spec and before-feature, not before-block.

Any pointers would be appreciated!

[David Lumpkin]

I've looked for this too but never found a good way to do it

[Raghu Kiran]

BDD test case writing is cool, This shoud reflect in reporting too. 

AbstractRunListener does not have beforeBlock and afterBlock contracts in Interface... 

Is there a way we can raise an enhancement request for this to be included to spock? Logging is where the teams and folks look at after automation runs and having good log that says what failed at which Block certainly helps. 

[Brian Stewart]

I just stumbled across a simple way to do this, and thought I'd update here. Just add the logging statement where the block description would be. A wrapper function around `log.info()` would make it even cleaner. 

def 'test block-level logging'() {


    given: log.info 'some setup'
    def x = 5
    ...
}

Brian

[Robert Evans]

You can make the method name a more dynamic which turns the problem on its head a little but ultimately gives you what you want which is presumably to see the values of your variables and make your programs easier to debug.

def "when I add #addValue to x=#x the result is #expected"() {
    when:
    def result = x + addValue

    then: // (possibly expect: I cannot remember.)
    assert result == expected

    where:
    | x | addValue | expected  |
    | 5 | 1        | 6         |
}

For more than 1 row in the where: portion use the @Unroll annotation above the method name to let spock know to treat each row of input as a single independent test - otherwise it'll assume your assertions are all a part of a single larger test and you won't get the right output.

HTH 

Rob