Latest on VS2022 Associate Test Case and AZDO
Good morning! Do ya'll have any recent developments on how to leverage the Associate Test Case feature in VS2022 to link to AZDO Test Cases? This is a fairly large limitation for us with the default SpecRunner and would really like to keep using it ILO of another runner. When I researched this last, I came up with, Jordan's ADOTestSync tool may be a workaround to the issue - is this still the case or have there been any further developments on this front? Thanks as always!
Agreed, being able to associate SpecFlow features to AZDO Test Cases would be huge.0
Hey John Rodriguez,
I have not seen anything else that achieves this other than the project I shared way back from my GitHub.
Carter Rohmiller the project I wrote can achieve this; it's not perfect but could be cloned and used with relative ease.
I would have made something a bit more user friendly out of the box, but with the bulk uploading of work items into ADO, MS were charging me a fortune so I had to stop.0
Thanks so much Jordan - this helps! With the latest Specrunner announcement we'll likely table this as a contingency and start work with nunit or mstest ILO.0
Just some background information about this:
We could have never fixed this with the SpecFlow+ Runner, because this part of Visual Studio can't be extended by a unit test runner. You would always have to use an external tool, like the one Jordan Western created.0
John Rodriguez you could easily extend the tool I wrote to work with those runners too, all you'd need to do is find the tests from the dll by their attributes specific to that runner. This way you can run the exe in your build pipeline and not have to worry about manual association.0
For clarification - In VS2022, SpecFlow project using NUnit - I can associate my scenario back to AZDO using Associate Test Case (manually) without issue; test case in AZDO goes to an automated state as expected.
I think I'm missing something based on your responses - beyond what I listed above, is there some other limitation using a SpecFlow project (w/Nunit) that you're referencing that would still require a tool like Jordan's?0
Please sign in to leave a comment.