Visual Studio integration - Right click running

[Pedro G. Dias]

I believe this is a specrun issue, however, if it isn't please don't
shoot me :)

PROJECT-RIGHT-CLICK
When I right-click a PROJECT file in solution explorer, and select
"Run SpecFlow Scenarios", everything works as expected.

FOLDER-RIGHT-CLICK
Inside the project file, our features are in sub-folders, "Backend",
"FrontEnd".
If I right-click on one of these folders, and choose "Run SpecFlow
Scenarios", I see that SpecRun does some output, but no tests are
ever run. Copying SpecRun command and pasting into a CMD window
reveals the followning:

[Configuration error: Invalid filter expression syntax]

The command specrun is using begins with:
[C:\PSMob\Trunk\packages\SpecRun.0.12.0.69\tools\SpecRun.exe run
"Nrk.Programspiller.Specifications.dll" "/baseFolder:C:\PSMob\Trunk
\Backend.Specifications\Nrk.Programspiller.Specifications\bin\Debug" "/
filter:testpath:Feature:Backend+-+Categories+(US297) |
testpath:Feature:Backend+-+Channels+(US298) | ..(more filters here)]

FEATURE-RIGHT-CLICK
Same as folder-right-click. When I right-click a feature file and
choose to run specflow scenarios, the SpecRun output displays only the
following:

[C:\PSMob\Trunk\packages\SpecRun.0.12.0.69\tools\SpecRun.exe run
"Nrk.Programspiller.Specifications.dll" "/baseFolder:C:\PSMob\Trunk
\Backend.Specifications\Nrk.Programspiller.Specifications\bin\Debug" "/
filter:testpath:Feature:Backend+-+EPG+(US3324)" /
toolIntegration:vs2010]

Again, when I repeat this instruction in a CMD window, I See an error
message:

[Configuration error: Invalid filter expression syntax]

Is this something that I can influence in any manner?

[Gáspár Nagy]

Oh. This must be a bug indeed. Most probably there is a problem with
escaping the scenario titles when building the filter expression. Do
you have maybe a |, ! or & character in any of your scenario titles?
Removing that could be a temporary workaround until it is fixed.

Br,
Gaspar

On Dec 2, 8:15 am, "Pedro G. Dias" <pedro.digitald...@gmail.com>
wrote:

[Pedro Dias]

Could it be that we are using #language: no-nB in our features?

The files must be saved in unicode in order to run, however, it is strange that running the tests when we right-click on the entire project file, all the features run fine.

It is only when we do it from a folder, or directly on a feature file that nothing happens.

--
Pedro Dias
/www.digitaldias.com

[Pedro Dias]

I am enclosing one of the feature files that are not running on right-click.
The project name is: Nrk.Programspiller.Specifications
There is a folder inside the  project named: "Backend"
And I found one english scenario (from start) that you can understand: Channel List.Feature
I am enclosing this file, as well as the output from specrun:

C:\PSMob\Trunk\packages\SpecRun.0.12.0.69\tools\SpecRun.exe run "Nrk.Programspiller.Specifications.dll" "/baseFolder:C:\PSMob\Trunk\Backend.Specifications\Nrk.Programspiller.Specifications\bin\Debug" "/filter:testpath:Feature:Backend+-+Channels+(US298)" /toolIntegration:vs2010

Regards,


Pedro

--
Pedro Dias
/www.digitaldias.com

[Gáspár Nagy]

The project-level run does not build a filter it just runs the tests
unfiltered, that's why it works.

I'll check it in detail. It can happen that the parenthesis "(" and
")" in the feature title causes the trouble, because it does not seem
to be masked in the filter expression.

Br,
Gaspar

On Dec 2, 9:47 am, Pedro Dias <pe...@digitaldias.com> wrote:
> I am enclosing one of the feature files that are not running on
> right-click.
> The project name is: Nrk.Programspiller.Specifications
> There is a folder inside the  project named: "Backend"
> And I found one english scenario (from start) that you can understand:
> Channel List.Feature
> I am enclosing this file, as well as the output from specrun:
>
> C:\PSMob\Trunk\packages\SpecRun.0.12.0.69\tools\SpecRun.exe run
> "Nrk.Programspiller.Specifications.dll"
> "/baseFolder:C:\PSMob\Trunk\Backend.Specifications\Nrk.Programspiller.Specifications\bin\Debug"
> "/filter:testpath:Feature:Backend+-+Channels+(US298)"
> /toolIntegration:vs2010
>
> Regards,
>
> Pedro
>
>
>
>
>
>
>
>
>
> On Fri, Dec 2, 2011 at 9:38 AM, Pedro Dias <pe...@digitaldias.com> wrote:
> > Could it be that we are using #language: no-nB in our features?
> > The files must be saved in unicode in order to run, however, it is strange
> > that running the tests when we right-click on the entire project file, all
> > the features run fine.
> > It is only when we do it from a folder, or directly on a feature file that
> > nothing happens.
>

>  Channel List.feature
> 1KViewDownload

[Pedro G. Dias]

It is the parenthesis. Removing them is a temporary fix for us.

On 2 Des, 10:19, Gáspár Nagy <gaspar.n...@gmail.com> wrote:
> The project-level run does not build a filter it just runs the tests
> unfiltered, that's why it works.
>
> I'll check it in detail. It can happen that the parenthesis "(" and
> ")" in the feature title causes the trouble, because it does not seem
> to be masked in the filter expression.
>
> Br,
> Gaspar
>
> On Dec 2, 9:47 am, Pedro Dias <pe...@digitaldias.com> wrote:
>
>
>
>
>
>
>
> > I am enclosing one of the feature files that are not running on
> > right-click.
> > The project name is: Nrk.Programspiller.Specifications
> > There is a folder inside the  project named: "Backend"
> > And I found one english scenario (from start) that you can understand:
> > Channel List.Feature
> > I am enclosing this file, as well as the output from specrun:
>
> > C:\PSMob\Trunk\packages\SpecRun.0.12.0.69\tools\SpecRun.exe run
> > "Nrk.Programspiller.Specifications.dll"

> > "/baseFolder:C:\PSMob\Trunk\Backend.Specifications\Nrk.Programspiller.Speci fications\bin\Debug"