search

jole78 / TeamCity.SpecFlow.Reporting

Automates, via PowerShell, the process of executing SpecFlow features via specflow.exe to produce a html report that can be shown in TeamCity.
MIT License
19 stars 1 forks source link

PowerShell 3.0 requirement #1

Open jole78 opened 10 years ago

jole78 commented 10 years ago

See if we can remove it...don't know why there's that requirement?

djyako commented 10 years ago

First, kudos on getting this implemented. I had this working for me as well when using psexec and this set up "http://www.hamishgraham.net/post/TeamCity-SpecFlow-Integration.aspx". However when switched to windows 7 machines from 2003 server I ran into alot of system/machine level permissions. Also the psexec hanging issues. So then I switched to powershell and implemented the same process via the invoke-command. All in all, I have plugged in your solution into my project and here is minor concern...

It did take me a good minute to figure out the issues with your powershell. The issues was with me not having the right version of powershell installed :)

Maybe a better error/validation message would help...

Invoke-TeamCitySpecFlowReport : System.Management.Automation.ParameterBindingEx [14:55:13][Step 39/39] ception: A parameter cannot be found that matches parameter name 'File'. [14:55:13][Step 39/39] at System.Management.Automation.CmdletParameterBinderController.VerifyArgume [14:55:13][Step 39/39] ntsProcessed(ParameterBindingException originalBindingException) [14:55:13][Step 39/39] at System.Management.Automation.CmdletParameterBinderController.BindCommandL [14:55:13][Step 39/39] ineParametersNoValidation(Collection1 arguments) [14:55:13][Step 39/39] at System.Management.Automation.CmdletParameterBinderController.BindCommandL [14:55:13][Step 39/39] ineParameters(Collection1 arguments) [14:55:13][Step 39/39] at System.Management.Automation.CommandProcessor.BindCommandLineParameters(C [14:55:13][Step 39/39] ommandParameterInternal[] parameters) [14:55:13][Step 39/39] at System.Management.Automation.CommandProcessor.Prepare(CommandParameterInt [14:55:13][Step 39/39] ernal[] parameters) [14:55:13][Step 39/39] at System.Management.Automation.CommandProcessorBase.DoPrepare(CommandParame [14:55:13][Step 39/39] terInternal[] parameters) [14:55:13][Step 39/39] at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean inc [14:55:13][Step 39/39] omingStream) [14:55:13][Step 39/39] at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecut [14:55:13][Step 39/39] eEnumerate(Object input, Hashtable errorResults, Boolean enumerate) [14:55:13][Step 39/39] At line:1 char:30 [14:55:13][Step 39/39] + Invoke-TeamCitySpecFlowReport <<<< "ThisOne" [14:55:13][Step 39/39] + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep [14:55:13][Step 39/39] tion [14:55:13][Step 39/39] + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio [14:55:13][Step 39/39] n,Invoke-TeamCitySpecFlowReport

jole78 commented 10 years ago

@djyako thx! Really there shouldn't be a PS3 requirement...at least I didn't plan on it. Will try to look into it. Besides I do except PR so if have an idea...