I work for a large organization in QA and we use Azure DevOps for testing enterprise level projects. I have ran into some issues with projects this large and when I try to find solutions, all I’ve found are years old posts from Microsoft telling someone to submit it to their suggestions and then nothing happens. Thought maybe someone here might know a simpler way of doing things? Or an alternative to DevOps? I haven’t used Jira in years, so I have no idea if it has these limitations.

The first issue we’re having is that we can’t track test execution tasks because you can’t query them. They’re not considered work objects. So I can’t create a dashboard view from info we can’t query. This means I get to manually click through test suites and visually identify the tests that are still out there needing to be ran, and who needs to run them. This is not feasible when you have 3k test executions in the first sprint of the project. You can query the test case, but that’s not the execution task. A report of the people who made the scripts is not useful to us.

The second issue is with shared parameters. We would like to be able to have a variable or parameter as our test URL that the testers will click on in the first step of the test script. We would like it to be variable because the URL will change when we move to different environments. I have figured out how to do that with parameters, but it requires you to click on every single test and convert it to shared parameters. With the number of test cases we have, this would not be possible. I was looking for a way to assign shared parameters to all test cases, or maybe every new test case that was created. Also looked into copying that step to all test cases, but it would require working each test individually as well.

Is Azure DevOps actually enterprise level, or should we be looking for something else for project tracking? I work in state government if that is a factor in choosing the best tracking method. We work with all divisions of the state.

Tried looking into Rest API, but it seemed like it would apply the parameter more like a configuration or tag, instead of adding the URL to the first test step and using it as a shared parameter.

Here’s kinda what we’re trying to accomplish:

Also tried using this edit feature to add parameters to multiple cases at once, but it just applies it like a tag or configuration or something, without making it a shared parameter (meaning we would still have to edit every test manually):
enter image description here
enter image description here