Usage of @Issue annotation and where clause

[AnthonyTonda]

I would like to know if you are planning to handle this:

@issue(“#format test”)
def “method using where clause #format test” {
Given…
Then…
Where
#format
xml
json
}

We will have two tests with the format xml then json
We will have also the sentence having the token #format being replace by xml then by json
Will you apply also for the annotation @issue having also the token #format ?

thanks in advance for your reply
Tonda

[Vampire]

For what would that be useful?
You could probably even write an own global Spockextension that does it, all the @Issue extension does is setting Tags, besides serving as documentation itself which could be used by some reporting extension or similar.
But the intention of the @Issue annotation is to write there the issue that is tested with the test, like the link to the GitHub issue, or alternatively just the issue number.
I don't see how there the data variables would be any helpful in 99% of the cases.

[AnthonyTonda]

Let’s agree that we have different point of view of using the annotation @issue
For a Story we have multiple Issues or Tests
A test can be parameterized. I want to be link to distinct issue/test

[AnthonyTonda]

"The built-in extension just sets Spock tags derived from the @issue values."

is it possible to set the @issue value from the where block ?

[Vampire]

No

[AnthonyTonda]

Can you explain, please. Why it is no ?

[Vampire]

Because it is an annotation.
Annotation values need to be compile-time constants.