How to use test_wait_with_force method in Playwright Python

There is no outer_html out of the box. But it's not hard to implement it:

locator.evaluate("el => el.outerHTML") 

This should get you started, because you don't really need to do fancy image trickery.

All reddit posts have data-testid=post-container selectors which let you get the top level post. All comments have a .Comment class you can use, so you can enumerate all the comments on any given reddit post and capture them separately if that's what you want.

Some major caveats of this code:

• It does not respect comment nesting - I only took a brief glance at Reddit's page source but they don't seem to have easy ways of getting comment chains.

• Reddit could change their selector names/CSS classes any time, and they do have some inconsistencies in how they seem to name things anyway.

• You specify you want to capture AskReddit threads, which can be quite large, so you could easily end up with, say, 1000+ comment screenshots on popular threads, or even 10K+ screenshots if you just let it run with abandon. I set a limit of 10, modify code as needed.

• I wrote this as a demonstration, I have no idea how it will perform on giant posts or such, but hopefully it shows you how to actually pull the information you want. If you need to do more work, you will likely have to inspect Reddit page layouts with your browser's developer tools.

#!/usr/bin/env python3

import asyncio
from playwright.async_api import async_playwright, Browser

MAX_COMMENT_LIMIT = 10


async def capture(browser: Browser,  url: str) -> None:
    page = await browser.new_page()

    await page.goto(url)
    posts = page.locator("data-testid=post-container")

    # reddit loads differently sometimes, so you need to
    # find the first post on the page
    await posts.first.screenshot(path="post.png")

    # this does not respect comment-nesting
    comments = page.locator(".Comment")
    count = await comments.count()
    print(f"Found {count} comments")
      
    for i in range(count):
        await comments.nth(i).screenshot(path=f"comment-{i}.png")

        if i+1 == MAX_COMMENT_LIMIT:
            print(f"Screened {MAX_COMMENT_LIMIT} images, stopping.")
            break


async def main() -> None:
    reddit_url = "https://www.reddit.com/r/cpp/comments/w9xkmf/c_for_scientific_programming/"
    async with async_playwright() as p:
        browser = await p.chromium.launch()
        await capture(browser, reddit_url)
        await browser.close()

asyncio.run(main())

The thread I picked generated some images like this...

Top-level post text

A comment

For the 1st form:

def get_playwright():
    with sync_playwright() as playwright:
        yield playwright

print(get_playwright())  # <generator object get_playwright at 0x108aac580>

That is expected because get_playwright is a generator, which returns a generator iterator, which you have to call next(...) on to get each yielded value from the iterator.

Consider a simpler, non-playwright example:

In [14]: def generate_nums():
    ...:     for num in range(10):
    ...:         yield num
    ...: 

In [15]: nums = generate_nums()

In [16]: nums
Out[16]: <generator object generate_nums at 0x11115e6d0>

In [17]: next(nums)
Out[17]: 0

In [18]: next(nums)
Out[18]: 1

In [19]: next(nums)
Out[19]: 2

For more examples, see Understanding generators in Python.

Since your get_playwright returns an iterator, you need to call next() once to get the actual object:

from playwright.sync_api import sync_playwright


def get_playwright():
    with sync_playwright() as playwright:
        yield playwright

playwright_generator = get_playwright()
print(playwright_generator)  # <generator object get_playwright at 0x104031580>

playwright = next(playwright_generator)
print(playwright)  # <playwright._impl._playwright.Playwright object at 0x1041aabb0>

For the 2nd form:

@pytest.fixture()
def get_playwright():
    with sync_playwright() as playwright:
        yield playwright

def test(get_playwright):
    print(get_playwright)

It should be the same case, but it's just that pytest automatically calls next() on the fixture value if it's a generator. I could not find documentation for this behavior from the pytest docs, but it was mentioned by one of the pytest author's/maintainer's in a different answer:

Here's roughly the execution here

• pytest notices your fixture is used for the test function
• pytest calls the fixture function
  • since it is a generator, it returns immediately without executing code
• pytest notices it is a generator, calls next(...) on it
  • this causes the code to execute until the yield and then "pausing". you can think of it kind of as a co-routine ...
• pytest then executes your test function

...which is probably why the value passed to your test function is already the next-ed value, the playwright object.

Each test must be independent from the rest. As you said, your test_delete_user can not depend on your test_create_user.

What I do? For my test test_create_user:

• Load website
• Create user
• Use expect statement to verify it worked
• In case you don't want to leave trash in the DB, then you can have another DB query for deleting that new user, but if this query does not work, the test should not fail.

For my test test_edit_user:

• Load website
• I always edit same user
• Use expect statement to verify it worked

For my test test_delete_user:

• Precondition: I have a query to DB to insert an user, then my test starts.
• Load website
• Delete user
• Use expect statement to verify it worked

I do it like this because each test is independent, lets imagine the function for deleting an user is working but your function for create user is not working, if your test were like this:

• Load website
• Create user
• Delete user
• Use expect statement to verify it worked

You will get a falsy error saying that your test_delete_user is not working, but actually it is.

I had the same issue as well. I ran this command, then restarted my command line and it started working.

playwright install-deps

I hope this helps.

How about checking if the element is clickable: https://playwright.dev/docs/api/class-locator#locator-click

use trial option and if it returns true continue execution

  await page.click(First_Row_Download, , {trial:true})

You can use below (Reference).

await page.locator('td > small:below(:text("{pan_ids[number]}")').text_content()

Or, You can also use the Adjacent sibling combinator

await page.locator(':text("{pan_ids[number]}") + td > small').text_content()

you can use the channel msedge

robotframework example

New Browser chromium headless=false channel=msedge

New Context viewport={'width': 1920, 'height': 1080}

New Page https://marketsquare.github.io/robotframework-browser/Browser.html

I have come up with a solution in Node js puppeteer and I think it work the same way in python. As far as why the button isn't being pressed, I have no idea. But, what does work is entering an address and then clicking the first address suggestion.

Here is my code:

const puppeteer = require('puppeteer');
async function start(){
    const browser = await puppeteer.launch()
    const page = await browser.newPage()
    await page.goto("https://www.ubereats.com/ca")
    await page.type("#location-typeahead-home-input", "Address")
    await page.waitForSelector('#location-typeahead-home-item-0');
    await page.click("#location-typeahead-home-item-0")
    await page.waitForNavigation()

    console.log(page.url())
    await browser.close()
}

start()