Hi Edgardo,
currently the filtering logic is as follows:
- first it checks to see the filter matches the story meta
- then it does the same check for each scenario meta, inheriting from
the parent story meta.
What's happening here is that your filter '+author A' - an inclusive
rather than an is not matching the check on the story meta (which is
empty):
Meta[properties={}] excluded by filter '+author A'
Therefore it never goes on to execute the scenarios.
Arguably, we should be doing the story-level check on a merged meta that
included all the scenarios metas too.
Could you please create a jira issue for this and attach your example
project?
Cheers
On 13/05/2011 20:23, Edgardo Hames wrote:
> Hi Mauro,
>
> I created the attached project which uses a very simple story with 2
> scenarios. Each scenario has a different author. I would like to run
> the scenario written by author A using
>
> <metaFilters>
> <metaFilter>+author A</metaFilter>
> </metaFilters>
>
> but that doesn't run any scenarios. Filtering with -author A works
> fine. Attached project is self-contained and doesn't have any external
> depdendencies. See maven details below.
>
> Thanks,
> Edgardo
>
>
> $ mvn -version
> Apache Maven 2.2.1 (r801777; 2009-08-06 16:16:01-0300)
> Java version: 1.6.0
> Java home: C:\Program Files\IBM\WID7\jdk\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch:
> "x86" Family: "windows"
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
