test framework error: Unable to load type TechTalk.SpecRun.Framework.Filtering.TagFilter required for deserialization

hussainsam commented 4 years ago

SpecFlow Version:

[ ] 3.1
[ ] 3.0
[x] 2.4
[ ] 2.3
[ ] 2.2
[ ] 2.1
[ ] 2.0
[ ] 1.9

Used Test Runner

[x] SpecFlow+Runner
[ ] MSTest
[ ] NUnit
[ ] Xunit

Version number: 1.8.5

Project Format of the SpecFlow project

[x] Classic project format using packages.config
[ ] Classic project format using <PackageReference> tags
[ ] Sdk-style project format

.feature.cs files are generated using

[x] SpecFlow.Tools.MsBuild.Generation NuGet package
[ ] SpecFlowSingleFileGenerator custom tool

Visual Studio Version

[ ] VS 2019
[x] VS 2017
[ ] VS 2015

`Enable SpecFlowSingleFileGenerator Custom Tool` option in Visual Studio extension settings

[ ] Enabled
[x] Disabled

Are the latest Visual Studio updates installed?

[x] Yes
[ ] No, I use Visual Studio version <Major>.<Minor>.<Patch>

.NET Framework:

[x] >= .NET 4.5
[ ] before .NET 4.5
[ ] .NET Core 2.0
[ ] .NET Core 2.1
[ ] .NET Core 2.2
[ ] .NET Core 3.0

Test Execution Method:

[ ] Visual Studio Test Explorer
[x] TFS/VSTS/Azure DevOps – Task – Visual Studio Test
[ ] Command line – PLEASE SPECIFY THE FULL COMMAND LINE

<SpecFlow> Section in app.config or content of specflow.json

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler,log4net" />

  <section name="specFlow" type="TechTalk.SpecFlow.Configuration.ConfigurationSectionHandler, TechTalk.SpecFlow" /></configSections>
<appSettings>
xxx
</appsettings>

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="TechTalk.SpecFlow" publicKeyToken="0778194805d6db41" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.4.0.0" newVersion="2.4.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="TechTalk.SpecRun" publicKeyToken="d0fc5cc18b3b389b" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.8.0.0" newVersion="1.8.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-10.0.0.0" newVersion="10.0.0.0" />
      </dependentAssembly>   
    </assemblyBinding>
  </runtime>
<specFlow>
    <!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config -->
  <!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- use unit test provider SpecRun+NUnit or SpecRun+MsTest for being able to execute the tests with SpecRun and another provider --><!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- use unit test provider SpecRun+NUnit or SpecRun+MsTest for being able to execute the tests with SpecRun and another provider --><!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- use unit test provider SpecRun+NUnit or SpecRun+MsTest for being able to execute the tests with SpecRun and another provider --><!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- use unit test provider SpecRun+NUnit or SpecRun+MsTest for being able to execute the tests with SpecRun and another provider --><unitTestProvider name="SpecRun" /><plugins>
      <add name="SpecRun" />
    </plugins></specFlow></configuration>

Repro Project

Issue Description

Local Scenario : I have 2 projects in a solution. After linking the required run settings file and build/rebuild the solution, test runner will not recognize the test cases defined in srs profile. If I rebuild just one project within the solution, test runner identifies the test cases and populates the scenarios in test explorer.

TFS Scenario: I attempted numerous ways to make the test cases recognized while CI build but unfortunately I couldnt do so. Here's my CI build tasks comprises of

Get Sources [pointing to my repo]
Visual Studio Build [pointing to solution file]
Visual Studio Test [pointing to run settings file] Here's the steps I tried so for Attempt 1 : Since in my local version, the test cases are recognized only after build single csproj file and not .sln, I added another task in the CI build : MSBuild task [pointing to csproj] with arguments /t Rebuild or /t Clean;Build The build was successfull but the test cases are still not idenfied. Attempt 2 : I went to the Agent system where the CI builds run, and tried clearing the temp data and rebuild but same issue. Attempt 3 : I tried running the same project in Agent system, linking the run settings file and rebuilding the project manually, Specrun is able to identify the test cases but its not happening when the build is running on CI. Please help, I will not be able to upgrade to Specflow 3 yet as the framework is so big, migration would consume lot more effort for now.

Steps to Reproduce

Here's my package details

hussainsam commented 4 years ago

Here's my package details
<packages>
  <package id="log4net" version="2.0.5" targetFramework="net45" />
  <package id="Newtonsoft.Json" version="10.0.3" targetFramework="net45" />
  <package id="SpecFlow" version="2.4.1" targetFramework="net45" />
  <package id="SpecFlow.Tools.MsBuild.Generation" version="2.4.1" targetFramework="net45" />
  <package id="SpecRun.Runner" version="1.8.5" targetFramework="net45" />
  <package id="SpecRun.SpecFlow" version="1.3.0" targetFramework="net45" />
  <package id="SpecRun.SpecFlow.2-4-0" version="1.8.5" targetFramework="net45" />
  <package id="System.ValueTuple" version="4.3.0" targetFramework="net45" />
</packages>

SabotageAndi commented 4 years ago

@hussainsam What is the filter in the srProfile- Files?

hussainsam commented 4 years ago

@SabotageAndi Below is the Filter, the same tag has in the Feature file.

<TestAssemblyPath> AppFeatureTest.dll</TestAssemblyPath>
  <Filter>@sanity_workflow</Filter>
I also tried with
<Targets> 
      <Filter>@sanity_workflow</Filter>
   </Target> 
</Targets>

SabotageAndi commented 4 years ago

@hussainsam Please post the whole srProfile or make no errors in copy & pasting parts of it. TestAssemblyPath and Filter can be on the same level.

for the filter you are missing a Target tag before.

I have no idea if your error is now because of an illegal srProfile or not.

SabotageAndi commented 3 years ago

Closed because of inactivity

github-actions[bot] commented 3 years ago

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.

SpecFlowOSS / SpecFlow