microsoft / playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
https://playwright.dev
Apache License 2.0
66.4k stars 3.63k forks source link

[Feature] Is there any plan to implement Playwright and Azure Test Plan integration so we can associate our automated tests to our Azure Test Cases? #28983

Closed qk5 closed 9 months ago

qk5 commented 9 months ago

According to the official Azure DevOps documentation at the URL: https://learn.microsoft.com/en-us/azure/devops/test/associate-automated-test-with-test-case?view=azure-devops,

We can only associate the following automated tests with Azure Test Plan, and Visual Studio Enterprise must be used for this purpose:

I did find the following extension that facilitates this integration, but it is specifically designed for Playwright node.js: https://github.com/alexneo2003/playwright-azure-reporter

While this extension works well based on my personal testing, it only supports Playwright node.js and not Playwright Java, which is the preferred programming language in my company.

So, here are the questions:

  1. Since Visual Studio Code is the preferred choice for Playwright automation development, is it possible to implement this integration without going through Visual Studio Enterprise and instead use Visual Studio Code?

  2. If so, can we have this feature for all supported Playwright programming languages (node.js, Python, and Java)?

mxschmitt commented 9 months ago

This sounds like a feature request to a specific language binding rather than to the Node.js version of Playwright. I recommend filing a separate issue in the language binding repository you are interested in (e.g. microsoft/playwright-java). For the non-Node.js language bindings we don't have our own test-runner, this gives us limitations but also offers opportunities, that existing users of e.g. NUnit/MSTest/junit have implemented similar things.

Playwright only offers an extension for VSCode as of today. This is because we learned, that most of our users are in Node.js and we have only there the required APIs/integrations (via our own test-runner).

Closing as per above.