Microsoft Playwright for .NET NUnit, cant launch tests in headed mode

Question

Im starting to use Playwright to automate my tests for a Blazor WebAssembly application, i created a new NUnit Test project and following the docs on playwright.dev i installed:

dotnet add package Microsoft.Playwright.NUnit

doing so i can inherit the PageTest class and directly use a Page object already configured for me without needing to instantiate the browser and the context

now i need to see what happens during my tests so i wanted to enable headed mode, normally i would launch the browser with this options like this:

await playwright.Firefox.LaunchAsync(new BrowserTypeLaunchOptions
{
    Headless = false,
    SlowMo = 50,
});

but i cant do that here, the official docs suggest to use this commands on the console

set HEADED=1

dotnet test

but nothing happens, the tests are run headless mode regardless.

Shoejep · Accepted Answer · 2022-07-05 13:00:20Z

3

If you set the environment variable PWDEBUG before your tests run, they will run in headed mode.

e.g. by doing something like this in a one time set up.

Environment.SetEnvironmentVariable("PWDEBUG", "console");

More information about Run in Debug Mode

answered Jul 5, 2022 at 13:00

Shoejep

4,8795 gold badges26 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

seangwright · Accepted Answer · 2023-07-19 16:22:57Z

3

The SlowMo and Headless options can be configured with a .runsettings file which you can specify when executing dotnet test

https://github.com/microsoft/playwright-dotnet/issues/2598

Create a headed-e2e.runsettings file:

<!-- headed-e2e.runsettings -->
<RunSettings>
    <!-- NUnit adapter -->
    <NUnit>
        <!-- ... -->
    </NUnit>
    <!-- General run configuration -->
    <RunConfiguration>
        <EnvironmentVariables>
            <!-- For debugging selectors, it's recommend to set the following environment variable -->
            <!-- <DEBUG>pw:api</DEBUG> -->
        </EnvironmentVariables>
    </RunConfiguration>
    <!-- Playwright -->
    <Playwright>
        <BrowserName>chromium</BrowserName>
        <ExpectTimeout>5000</ExpectTimeout>
        <LaunchOptions>
            <Headless>false</Headless>
            <SlowMo>1000</SlowMo>
            <Channel>chrome</Channel>
        </LaunchOptions>
    </Playwright>
</RunSettings>

Then specify that file when executing your tests:

dotnet test -s headed-e2e.runsettings

You could have other .runsettings files for other test use cases.

Note that the .runsettings file can be used for more than just Playwright

answered Jul 19, 2023 at 16:22

seangwright

18.3k7 gold badges47 silver badges57 bronze badges

1 Comment

MBielski Over a year ago

This is actually what worked for me.

Nalin · Accepted Answer · 2022-04-06 11:21:11Z

2

Use this

await using var browser = await playwright.Firefox.LaunchAsync(new BrowserTypeLaunchOptions { Headless = false, SlowMo = 50 });
var context = await browser.NewContextAsync();
var page = await context.NewPageAsync();
await page.GotoAsync("The site you want to go");

It should work

answered Apr 6, 2022 at 11:21

Nalin

773 silver badges13 bronze badges

1 Comment

Honza P. Over a year ago

This was the programatic way for me, config way did not work in my case.

Svetoslav Ts. · Accepted Answer · 2022-06-28 11:00:51Z

2

For the headless mode I first set the following in the terminal "$env:HEADED=1", so that it will open a browser. Keep in mind you have to set it to "0" if you want to run it in headless mode again. From what I understood, after inheriting from PageTest, due to lack of config file, such things (headless/slowMo) should be set runtime from the terminal.

answered Jun 28, 2022 at 11:00

Svetoslav Ts.

212 bronze badges

1 Comment

Adrián Alvarez Over a year ago

You should remember to blank the HEADED environment variable afterwards. This is done with $env:HEADED="" And you can see its value with echo $env:HEADED All of this should be done within a Powershell window.

Shahar · Accepted Answer · 2023-01-01 12:38:33Z

1

The playwright libary also provided test Runners frameworks like: mstest, NUnit, and Xunit. With the testing runner framework - NUnit, you can use customizing Browser/launch options by using the run settings file - .runsettings. See the docs: https://playwright.dev/dotnet/docs/test-runners See it under - "customizing Browser/launch options under Nunit/mstest"

Also about .runsettings file https://learn.microsoft.com/en-us/visualstudio/test/configure-unit-tests-by-using-a-dot-runsettings-file?view=vs-2022 for that to work with Nunit you need NUnit3TestAdapter. So your .csproj file contains:

<ItemGroup>
  <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.3.2" />
  <PackageReference Include="Microsoft.Playwright.NUnit" Version="1.28.0" />
  <PackageReference Include="Microsoft.Playwright.TestAdapter" Version="1.28.0" />
  <PackageReference Include="NUnit3TestAdapter" Version="4.3.1" />
</ItemGroup>

edited Jan 1, 2023 at 12:38

answered Jan 1, 2023 at 12:27

Shahar

112 bronze badges

1 Comment

Jan Over a year ago

NUnit3TestAdapter is a dependency within Microsoft.Playwright.NUnit as is Microsoft.Playwright.TestAdapter. So you don't need to add these two packages explicitly

Collectives™ on Stack Overflow

Microsoft Playwright for .NET NUnit, cant launch tests in headed mode

5 Answers 5

Comments

1 Comment

1 Comment

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

1 Comment

1 Comment

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related