Skip to main content

wildcards for testexecution json file is not working.

Comments

6 comments

  • Andreas Willich

    Could you post the complete command line call?

    It is the fourth line in the screenshot.

    0
  • The command line task he not relevant to SpecFlow and it was just for my reference.  Below is the task which I am using.

    - task: SpecFlowPlus@0
        displayName: Create SpecFlow Feature Documentation
        condition: always()
        inputs:
            generatorSource: 'TestAssembly'  #Required. Options: FeatureFolder, TestAssembly, FeatureData
              testAssemblyFilePath:' $(Build.ArtifactStagingDirectory)/FeatureTests/bin/Debug/netcoreapp3.1/Rabobank.nBIF.RSME.FeatureTests.dll'
            projectName: 'nBIF POC SpecFlow'
            testExecutionJson: '$(Build.ArtifactStagingDirectory)/FeatureTests/bin/Debug/**/TestExecution_*.json'
            projectLanguage: 'en'

    0
  • Please assist on what I am missing here :) I tried multiple approaches for fixing the path, but no luck. Below is how the TestExecution_*.json files are being published in the pipeline.

     

    0
  • Andreas Willich

    Hmm. Interesting. 

    The only quick idea is, that there is a problem with case-sensitive paths. You are running on a Linux agent which is case-sensitive for files/folders/paths. Windows is not case-sensitive for these things.

    0
  • Should I need to try this in windows agent pool? kindly advice.

    0
  • It seems to be the same issue when I run it on windows agent pool.

    0

Please sign in to leave a comment.

Powered by Zendesk