Skip to main content

Setting up multiple test projects in Azure Pipeline




  • Balazs Epresi


    This is currently not supported. The build task only accepts 1 input (1 feature folder, 1 test assembly, 1 feature data).
    However, as a workaround, you could add for each project a build task. This should work, because the Build task (during it's run) will merge the previous build task results into one.

    I don't know how many projects you have currently, hopefully not a lot of work to create the tasks. If you wish, you can open a feature request here: 

  • william diaz

    Thank you for the reply, I imagine there will be many test projects, Having to modify the Pipeline each time a new test project is created is a bit of an overhead. Ideally some sort of pattern matching within a folder structure would be ideal. In the meantime I will test your multiple build steps suggestion and report back. Thanks again.


    Multiple steps is working. so far. Just have to test the "Unused Step Definitions" field. I though I had one showing up before but now is 0. not sure if it is being overwritten by latest built step.

    Confirmed, the "Unused Step Definitions" field under the analytics tab is not working as expected. My first test project has 1 unused step, while the second does not. I have two build steps for LivingDocs and the las step seems to be overwriting this field and showing up as "0"

Please sign in to leave a comment.

Powered by Zendesk