Why there is a need for 2 (Playwright and NUnit) Adapters in dependencies

[nithinbandaru1]

Please do not submit this issue.

• I understand

Hi,

I am trying to work with Playwright and I am just exploring different things that are needed for working with Playwright.

1. I came across 2 adapter dependencies when I installed Microsoft.Playwright.NUnit package. Isn't NUnit adapter enough to work? NUnit adapter will be used for both test discovery and test execution. I am confused what is this additional adapter doing here. Does it modify default execution of NUnit Adapter or it completely overrides it somehow?
2. Does this need node JS runtime to run the tests. I came across this this architecture which says that this language dependencies are very just libraries which provide programming interface to in different languages and there will be WebSocket connection to the Playwright Server where the execution of browser steps happens? So, with this I see it now working without Node JS runtime. Also seeing port of Playwright in README confused me more?
3. Also wondering about if I can use different tools that I see in nodejs like test reports UI etc. One doubt is NUnit does not support test steps, and in UI I saw has test steps, So I wounder if there will be 2 test reports that will come one in .trx format specific to .NET and one in Playwright format. Playwright format report will be used for that UI (probably without steps I guess as there is no steps anyway in .NET)?
4. Keeping steps in mind I wounder if you guys have plans to support Reqroll (Formally SpecFlow) framework based NuGet package?

It would be great if this questions are answered to get started with Playwright with great clarity.

[mxschmitt]

It takes care of reading the values from the runsettings file / parameters.

[nithinbandaru1]

@mxschmitt Thanks for super fast reply. But I was not yet written my questions 😁. It would be really kind of you if you can address my questions.

[nithinbandaru1]

#2988
I guess Reqroll (Formally SpecFlow) framework based NuGet package would resolve my 4 point quite easily.

[mxschmitt]

1. Its not enough, since we have a custom logic to parse the runsettings file with the Playwright properties. This is what our TestAdapter takes care of. It does not modify default execution of NUnit or MSTest.
2. Internally yes, but this is an implementation detail. Internally we are communicating over stdin/stdout with it. With port we mean the .NET version of Playwright aka. a client.
3. There is no trx integration with Playwright test steps. Playwright for .NET is just a library. No additional integrations as of today. Tools like VSCode integration, UI Mode or HTML Reporter are Node.js only.
4. There are no plans for that as of today.