Closed jpc1963 closed 4 years ago
No ideas on my side. We don't maintain the SpecFlow VS Extension for VS for Mac/MonoDevelop/XamarinStudio and in the callstacks I don't see anything related to SpecFlow.
What I know is, that Xamarin UITest has some ugly hacks for SpecFlow support that is version dependent. Perhaps they didn't update it yet for SpecFlow 3.
OK thanks I'll follow it up with Xamarin.
Closed because of inactivity
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
UI test fails with error: Exception has been thrown by the target of an invocation.
SpecFlow Version:
Used Test Runner
Version number: 3.1
Project Format of the SpecFlow project
packages.config
<PackageReference>
tags.feature.cs files are generated using
SpecFlow.Tools.MsBuild.Generation
NuGet packageSpecFlowSingleFileGenerator
custom toolVisual Studio Version
Enable SpecFlowSingleFileGenerator Custom Tool
option in Visual Studio extension settingsAre the latest Visual Studio updates installed?
<Major>.<Minor>.<Patch>
.NET Framework:
Test Execution Method:
<SpecFlow> Section in app.config or content of specflow.json
Repro Project
Issue Description
I develop UI tests for apps on iOS & Android devices & simulators. I write UI Tests using VS 2019 on a MAC and recently tried to update my nuget packages to the latest version: NUnit = 3.12 Xamarin.UITest = 3.03 Specflow = 3.0.225
On Visual studio for the MAC I have always used Straight8s Specflow Integration to edit my feature files. The latest version generates code for specflow 3 - hence the upgrading my nuget packages.
When I run a test I get the following error (which occurs when trying to start the app on a simulator): 1 - LaunchTestAsync: deviceId: bla.bla 1 - Launching simulator if not already running Test server version: 0.21.7 Error: Exception has been thrown by the target of an invocation.
See attachments for further error info. NOTE: I removed all Specflow elements from the project and turned it into a simple Nunit test. This runs OK on my simulators / emulators.
Xamarin.Test.Results.txt Simulator.Log.txt
Any ideas?
Steps to Reproduce