Skip to main content

Specflow+Living Doc Azure Devops Integration failed and not working

Comments

10 comments

  • Nurulhuda Shaik

    any help please ? Please note i have latest version of specflow

    0
  • Jordan Western

    hi Nurulhuda Shaik,

    Your pipeline does not appear to have any test task?

    TestExecution.json is generated after test execution, as it would on your local machine.

    Please see our docs here.

    Yes you should see the results in the doc once the generation is a success

    0
  • Nurulhuda Shaik

    Jordan Western - Thanks for response. Can i add specflow+Living doc step to release pipeline instead of build pipeline ? And since have VS Test as step in task, do i need to also add .netcore Test task too ? 

    Sometime I do want to trigger automated test manually through release pipeline. 

    0
  • Jordan Western

    Hi Nurulhuda Shaik,

    Yes you can add the SpecFlow+LivingDoc build step to your release pipeline.

    I don't believe you need an additional test task, VS Test task should be fine.

    Let me know of any concerns

    0
  • Nurulhuda Shaik

    Jordan Western - I tried adding step to release pipeline still but still not able to resolve the issue. After looking at artifacts in azuredevops, i don't see TestExecution.json copied over to ADO (Error: Cannot find the specified test-execution-json). Can you please advise ?

    Test Execution JSON paths:

    $(System.DefaultWorkingDirectory)/_[solutionname] - Main - Master/drop/bin/Release/netcoreapp3.1/TestExecution.JSON

    Binding Assemblies:

    $(System.DefaultWorkingDirectory)/_[solutionname] - Main - Master/drop/bin/Release/netcoreapp3.1/LivingDoc.SpecFlowPlugin.dll

    Some more info:

    I have this in Specflow.JSON file

    {
    "bindingCulture": {
    "language": "en-us"
    },
    "language": {
    "feature": "en-us"
    },
    "plugins": [],

    "livingDocGenerator": {
    "enabled": true,
    "filePath": "TestExecution.JSON"
    }

    }

     

     

    0
  • Nurulhuda Shaik

    Can you please reopen the request. I see it is marked as Completed ?

    0
  • Jordan Western

    Hi Nurulhuda Shaik,

    This 'copy files to' task, is this in your build pipeline?

    You will only see the TestExecution.json after the test execution, so if this copy task is in your build pipeline then you won't see it because you have yet to execute any tests at this stage.

    All you should need to do in your release pipeline is add the 'LivingDoc build step' to your release pipeline after your test execution.

    If you are already doing this, please send me the logs from the test execution.

    0
  • Nurulhuda Shaik

    Jordan Western - I sent you an email with required release pipeline screenshots and logs. I hope you received it and able to advise.

    Also to you above question, yes 'copy files to' task is in build pipeline. I added living doc to release pipeline and this task got failed as shown in email screenshot and logs.

    0
  • Jordan Western

    Hi Nurulhuda Shaik,

    Thanks for the logs, I have replied to the email given that you don't want to show these publicly. 

    Lets continue the conversation for there now.

    0
  • Jordan Western

    Please remove this from your LivingDoc task and try again -

    0

Please sign in to leave a comment.

Powered by Zendesk