How to use test_hover method in Playwright Python

Playwright does not play well with relative paths, use os.getcwd() instead. Also, note that you don't need to ensure that directories exist, playwright creates them automatically if they don't.

from playwright.sync_api import sync_playwright
import os

user_dir = 'tmp/playwright'
user_dir = os.path.join(os.getcwd(), user_dir)

with sync_playwright() as p:
    browser = p.chromium.launch_persistent_context(user_dir, headless=False)
    page = browser.new_page()
    page.goto('https://playwright.dev/python', wait_until='domcontentloaded')

Try this:

if (page.is_visible(XPATH)):
    page.click(XPATH)

Or you can make the code cleaner like this:

try:
    page.click(XPATH)
except:
    pass

PLAYWRITH_BROWSERS_PATH=0

Please make sure your above configuration was correct. There are some spelling mistakes in the settings. Its like PLAYWRIGHT_BROWSERS_PATH = 0

In your local.settings.json it should be

{

"IsEncrypted": false,

    "Values": {
    
        "AzureWebJobsStorage": "",
        
        "FUNCTIONS_WORKER_RUNTIME": "python",
        
        "PLAYWRIGHT_BROWSERS_PATH": "0"
    
    }

}

And In your requirement.txt file it should be

azure-functions
playwright==1.18.0

here we can see the playwright running in local as well as azure after deployment Local:

Azure:

https://github.com/microsoft/playwright-python/issues/1622 :

Sounds like we need to upgrade to Greenlet v2 for that.

You can use one of those options :

const element = await page.$$("text='element'");
if (element) {
    // ...
}

or

const element = await page.$$("text='element'");
if (element.length) {
    // ...
}

or

await expect(page.locator(".MyClass")).toHaveCount(0)

Based on @ggorlen's suggestion, I spotted that the select_option triggered a request, which I was able to trigger on, and validate, thus:

        with page.expect_response(lambda response: response.url) as response_info:
            assert loc[0] in response_info.value.url, f"wrong location {response_info.value.url}, expecting {loc}"

From this page: https://playwright.dev/python/docs/network#variations

But note that there seemed to be a bug on that page as token in in the lambda function isn't relevant. The code checks that the query relates to the address of interest.

user and myInput are IDs on the input element itself and not on one of the parent elements. This means, that using a selector like this works in your scenario:

    page.type('input[name="email"]#user', "xxxxx")
    page.type('input[name="password"]#myInput', "xxxxxxxxxxxx")

The reason why it hangs is that it can't find the element. I would recommend to follow the Playwright debugging tools section to either use DEBUG=pw:api or the PWDEBUG=1 to get debug logs why its hanging - in your case it would tell you that the selector cannot be found.

In your special case, each page has their own link. It is your base link and the page number with an hyphen (-) in between.

You can see this behaviour when clicking on the second page, compare your base-link with the link you have now: https://forum.donanimhaber.com/turkcell-25-000-dk-12-000-sms-70-gb-internet-12-ay-320-tl-ana-konu--151777938-2

(notice the -2 at the end)

One way to do it, would be to change your url in a for-loop, iterating up to 24 and scrape all of those pages individually.

You can use the API request feature:

browser = playwright.chromium.launch()
context = browser.new_context(base_url="https://api.github.com")
api_request_context = context.request
page = context.new_page()

response = api_request_context.post(
  "/user/repos",
  headers={
      "Accept": "application/vnd.github.v3+json",
      "Authorization": f"token {API_TOKEN}",
  },
  data={"name": REPO},
)