Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C# Playwright #809

Closed
ferBonnin opened this issue Mar 17, 2022 · 9 comments
Closed

C# Playwright #809

ferBonnin opened this issue Mar 17, 2022 · 9 comments

Comments

@ferBonnin
Copy link
Contributor

Is your feature request related to a problem? Please describe.

My team is currently using the C# + Selenium option from https://github.com/microsoft/axe-pipelines-samples to run Accessibility Insights in our ADO build pipeline but would like to convert all our UIA to using C# + Playwright now that Microsoft has an official .NET port for Playwright (https://github.com/microsoft/playwright-dotnet).

Describe the desired outcome

Can an equivalent C# version of the npm @axe-core/playright package be created?

Additional context

Creating feature request on behalf of user

@ghost ghost added the status: new This issue is new and requires triage by DRI. label Mar 17, 2022
@ghost ghost assigned lisli1 Mar 17, 2022
@lisli1 lisli1 added the status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. label Mar 17, 2022
@ghost ghost assigned asksep Mar 17, 2022
@ghost
Copy link

ghost commented Mar 17, 2022

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

@ghost ghost removed the status: new This issue is new and requires triage by DRI. label Mar 17, 2022
@asksep asksep added the status: needs investigation This issue requires investigation (PM, Design, or SWE) by the Accessibility Insights team. label Apr 11, 2022
@ghost
Copy link

ghost commented Apr 11, 2022

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

@ghost ghost removed the status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. label Apr 11, 2022
@lisli1 lisli1 removed their assignment Apr 11, 2022
@jeffreyrivor
Copy link

Hi, I'm the original asker that sent this via email. Let me describe our current UI automation setup to add more context.

We are testing an ASP.NET Core app following the docs for Integration tests with customized WebApplicationFactory; this results in an HttpClient that allows sending requests and receiving responses in object form (without having an actual Kestrel server open an actual port on the localhost). Using the Selenium.WebDriver NuGet package and the Fetch domain of the Chrome DevTools Protocol, we drive a Chromium-based browser, intercept relevant requests and route them through this HttpClient to generate the response to return to the browser. This essentially results in a functional equivalent of navigating a browser to a page in the app, but without needing to deploy the service anywhere. With that setup, we simply use Selenium.Axe (a third-party C# wrapper of axe-core) to run accessibility scans through Selenium.WebDriver.

We have a desire to move from using Selenium.WebDriver library to using Microsoft.Playwright (the official .NET language port), primarily because the underlying support of the Chrome DevTools Protocol in Selenium.WebDriver is tightly coupled to the library and is out-of-date (v96) with current Chromium stable; see SeleniumHQ/selenium#10583 for details. We are only using Selenium.WebDriver due to the lack of an axe-core .NET language port that works with Microsoft.Playwright. With Chromium stable going to version 100+ now, the Selenium.WebDriver library no longer works with latest stable because it only allows a gap of up to 4 major versions between the web driver and itself (the newest version in the latest 4.1.0 package is the v96 protocol).

@dbjorge
Copy link
Contributor

dbjorge commented Aug 15, 2022

Just an update on this: our team is currently working with Deque and with the author of https://github.com/IsaacWalker/PlaywrightAxeDotnet to migrate that library to be the basis of a new, officially Deque-supported C# Playwright integration library. Once we've completed that work and gotten the library published, we'll be adding a new sample based on it here (tracked by this issue), as well as official https://playwright.dev documentation similar to the sample (tracked by microsoft/playwright#14112)

@Gso-1
Copy link

Gso-1 commented Jun 8, 2023

Hola Los Puedo Agregar Y suscribir y darles toda mi asesoría pero tenemos que llegar a un acuerdo de proceso de acuerdo de negocios para que sea el mas optimo para todos

@Gso-1
Copy link

Gso-1 commented Jun 9, 2023

¿Su solicitud de función está relacionada con un problema? Sírvase describir.

Mi equipo está usando actualmente la opción C# + Selenium de https://github.com/microsoft/axe-pipelines-samples para ejecutar Accessibility Insights en nuestra canalización de compilación de ADO, pero me gustaría convertir toda nuestra UIA para usar C# + Playwright ahora que Microsoft tiene un puerto .NET oficial para Playwright (https://github.com/microsoft/playwright-dotnet).

Describir el resultado deseado

¿Se puede crear una versión equivalente en C# del paquete npm @axe-core/playright?

Contexto adicional

Creación de una solicitud de característica en nombre del us

¿Su solicitud de función está relacionada con un problema? Sírvase describir.

Mi equipo está usando actualmente la opción C# + Selenium de https://github.com/microsoft/axe-pipelines-samples para ejecutar Accessibility Insights en nuestra canalización de compilación de ADO, pero me gustaría convertir toda nuestra UIA para usar C# + Playwright ahora que Microsoft tiene un puerto .NET oficial para Playwright (https://github.com/microsoft/playwright-dotnet).

Describir el resultado deseado

¿Se puede crear una versión equivalente en C# del paquete npm @axe-core/playright?

Contexto adicional

Creación de una solicitud de característica en nombre del usuario

Hola yo le podría agendar una realización de asesoría informática pero para ello necesitaría que lleguemos a un acuerdo comercial

@Gso-1
Copy link

Gso-1 commented Jun 9, 2023

Y lo podría suscribir en mi aplicación web pero para ello necesito que se contacte a mi correo corporativo gasparsalinasoyaneder@educarparaavanzar.onmicrosoft.com

@Gso-1
Copy link

Gso-1 commented Jun 9, 2023

Además la suscripción tiene un costo de 45000 CLP

@DaveTryon DaveTryon moved this from Needs Triage to Old backlog in Accessibility Insights Jun 28, 2023
@DaveTryon DaveTryon closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2023
@DaveTryon DaveTryon removed the status: needs investigation This issue requires investigation (PM, Design, or SWE) by the Accessibility Insights team. label Jul 27, 2023
@DaveTryon
Copy link
Contributor

Unfortunately, this is out of scope given our current priorities.

Thanks for using Accessibility Insights!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants