How to use FrameWaitForNavigationOptions class of Microsoft.Playwright package

Found the issue: I was running Visual Studio without admin privileges. Once I chose, "Run as administrator", the local MS Edge launched and the test succeeded. Apparently, Playwright needs elevated rights to launch the Channel local browsers vs. its own binaries, at least on some setups.

I wish, though, that Playwright could launch the stock browsers without having to have elevated privs.

You can use the selecting selectors based on layout for this.

await page.Locator("span:below(:text(\" Status :\"))").TextContentAsync()

Your page might be recreating the DOM. To overcome that you can use the locator feature from playwright.

var locator = page.Locator("inputSelector");
await locator.ClickAsync();

The error came from me not correctly understanding Docker stages. Here a fixed Dockerfile, where I installed Playwright in the base stage:

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
RUN apt-get update
RUN apt-get -y install curl gnupg
RUN curl -sL https://deb.nodesource.com/setup_16.x  | bash -
RUN apt-get -y install nodejs
RUN npx playwright install
RUN apt-get update && apt-get install -y --no-install-recommends \
    fonts-liberation\
    libasound2\
    libatk-bridge2.0-0\
    libatk1.0-0\
    libatspi2.0-0\
    libcairo2\
    libcups2\
    libdbus-1-3\
    libdrm2\
    libgbm1\
    libglib2.0-0\
    libgtk-3-0\
    libnspr4\
    libnss3\
    libpango-1.0-0\
    libx11-6\
    libxcb1\
    libxcomposite1\
    libxdamage1\
    libxext6\
    libxfixes3\
    libxrandr2
WORKDIR /app

FROM mcr.microsoft.com/dotnet/sdk:6.0-focal  AS build
WORKDIR /src
COPY ["Dashboard/Dashboard.csproj", "Dashboard/"]
RUN dotnet restore "Dashboard/Dashboard.csproj"
COPY . .
WORKDIR "/src/Dashboard"
RUN dotnet build "Dashboard.csproj" -c Release -o /app/build
FROM build AS publish
RUN dotnet publish "Dashboard.csproj" -c Release -o /app/publish

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "Dashboard.dll"]

What I've done is add a runsettings file to visual studio called, for example, test.runsettings with the following content:

<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
  <RunConfiguration>
    <EnvironmentVariables>
        <HEADED>1</HEADED>
    </EnvironmentVariables>
  </RunConfiguration>
</RunSettings>

Then, as long as VS chooses that runsettings file (see Test > Configure Run Settings in the menu) you should start getting HEADED mode

The right CSS selector for that is DIV.v-image__image.v-image__image--contain

const browser = await playwright.chromium.launch({ headless: false });
let page = await browser.newPage();
await page.setContent(`
<div class="v-image__image v-image__image--contain" 
style='background-image: url("https://example.com/myimage.jpg"); 
background-position: right center;'></div>
`);

const el = await page.$("DIV.v-image__image.v-image__image--contain");
const styleProperty = await el.getProperty("style");
const style = await styleProperty.jsonValue();
console.log(style.backgroundImage);
await browser.close();

Playwright for .NET discourages using xunit see here. Also the playwright.config file does only work for Node.js.

I'd recommend to set the DEBUG=pw:api env var to get more logs. Most likely your site is not reachable or hangs.

I'm not sure if the TestServer is really a 'server' listening on a port or just in memory access to server without the tcp/ip part. If so, you don't have how to make playrigth use the same specific http client made for the in-memory server, because the httpclient and TestServer are using fake objects instead of real network one to provide fast tests

According to their documentation it should be possible. I see you are using StorageState maybe try StorageStatePath instead. Their example:

var context = await browser.NewContextAsync(new()
{
    StorageStatePath = "userCookies.json"
});

https://playwright.dev/dotnet/docs/auth

It's not clear from their documentation, and I never used this library before and could be wrong, but I believe StorageState expects the stringified JSON and not a file path. While StorageStatePath expects a file path / file name to the JSON and will read the file for you.

https://www.javadoc.io/static/com.microsoft.playwright/playwright/1.12.1/com/microsoft/playwright/Browser.NewContextOptions.html#storageState