You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to generate focused reports by using the property serenity.exclude.unrelated.requirements.of.type in my serenity.properties file, see: serenity.exclude.unrelated.requirements.of.type= capabilities, features, stories
I'm using maven and jbehave and therefore jbehave metafilter instead the serenity tags function to execute my tests, e.g.: clean verify serenity:aggregate -Dmetafilter="+test"
Still I get the following results:
Seems that the property has absolutely no effect but I would assume that it should not show capabilities, features and stories in the report anymore.
Used versions:
<serenity.version>1.2.3-rc.4</serenity.version>
<serenity.maven.version>1.2.2</serenity.maven.version>
<serenity.jbehave.version>1.21.0</serenity.jbehave.version>
Anything wrong with that? Do I miss something or is this a bug?
The text was updated successfully, but these errors were encountered:
Is there any way that this function will work with jbehave meta filters in the future? This feature, in my opinion, is quite important for bigger test sets and I would realy love to use it.
I'm trying to generate focused reports by using the property
serenity.exclude.unrelated.requirements.of.type
in my serenity.properties file, see:serenity.exclude.unrelated.requirements.of.type= capabilities, features, stories
I'm using maven and jbehave and therefore jbehave metafilter instead the serenity tags function to execute my tests, e.g.:
clean verify serenity:aggregate -Dmetafilter="+test"
Still I get the following results:
Seems that the property has absolutely no effect but I would assume that it should not show capabilities, features and stories in the report anymore.
Used versions:
<serenity.version>1.2.3-rc.4</serenity.version>
<serenity.maven.version>1.2.2</serenity.maven.version>
<serenity.jbehave.version>1.21.0</serenity.jbehave.version>
Anything wrong with that? Do I miss something or is this a bug?
The text was updated successfully, but these errors were encountered: