[Feature]: Implement hasAttribute(String)

[jcgueriaud1]

🚀 Feature Request

I want to check if a locator has an attribute.
I think that's what toHaveAttribute(name) is doing in typescript.

I tried to:
assertThat(getInputLocator()).not().hasAttribute("min", ""); // that will forbid empty min but not a filled value
or
assertThat(getInputLocator()).not().hasAttribute("min", Pattern.compile(".*"));

And the result is:

• unexpected value "undefined"

With a new API hasAttribute(String attributeName), I would be able to do:
assertThat(getInputLocator()).not().hasAttribute("min");

That will test if there is an attribute min.

Example

import com.microsoft.playwright.assertions.PlaywrightAssertions;
import java.util.regex.Pattern;

Locator el = page.locator("#my-el");

// Assert the attribute is NOT present:
PlaywrightAssertions.assertThat(el)
    .not()
    .hasAttribute("min", Pattern.compile(".*"));

Motivation

The only workaround I found is to get the attribute and asserts it's null. But it's not the good practice.

Having that will help to check to the absence of a attribute.

[lnhrdt]

We would appreciate this addition too.

It looks like this feature was previously implemented in #1041 but was reverted in #1071.

Yury Semikhatsky (@yury-s) I know those PRs happened about 3 years ago, but can you recall if it was an intentional change to remove hasAttribute(name)?

[jcgueriaud1]

In fact this assertThat(getInputLocator()).not().hasAttribute("min", Pattern.compile(".*")); is working.
I was doing my test the wrong way.

[yury-s]

This was implemented in Node.js in microsoft/playwright#27418 but not ported to the languages. The workaround above should work.