azure-sdk-for-net
azure-sdk-for-net copied to clipboard
Azure
Onboard Azure.Developer.MicrosoftPlaywrightTesting sdk
Packages impacted by this PR
Azure.Developer.MicrosoftPlaywrightTesting Azure.Developer.MicrosoftPlaywrightTesting.NUnit
Description
- Onboard 2 packages
- Azure.Developer.MicrosoftPlaywrightTesting: Client library used to integrate Playwright OSS with Microsoft Playwright Testing service
- Azure.Developer.MicrosoftPlaywrightTesting.NUnit: Utility library to setup the above package in a NUnit environment.
What does the package do
- Playwright OSS client connects to the service-hosted browsers using the API provided by Playwright OSS. The package provides an abstraction over this interaction
- Test results are published from the machine running the tests to the service.
To integrate the service with a Playwright project, users will need to install a package along with Playwright OSS package. The package is tightly coupled with Playwright OSS package and also is responsible for entra id authentication.
Since we have 2 SDKs being published, both being pre-release versions, the NUnit SDK taking a dependency on the base SDK, how do we work around the below check?
https://github.com/Azure/azure-sdk-for-net/blob/80b5a9cf9eaaf1a889250e9d927d9f8ced5bff3b/eng/Directory.Build.Common.targets#L306
Since we have 2 SDKs being published, both being pre-release versions, the NUnit SDK taking a dependency on the base SDK, how do we work around the below check?
https://github.com/Azure/azure-sdk-for-net/blob/80b5a9cf9eaaf1a889250e9d927d9f8ced5bff3b/eng/Directory.Build.Common.targets#L306
You don't and should not need to. That check says "You can't have a GA package that has beta/preview dependencies." You've stated that you're intending to release two previews, which would not violate that validation.
![azure-pipelines[bot] avatar](https://avatars.githubusercontent.com/in/9426?v=4 "Published by a pub.dev verified publisher"){kind=small}
