How to use test_auth_should_fail_with_wrong_credentials method in Playwright Python

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.

As mentioned in the comments, your tests should be independent and indeed this can be achieved with database fixtures. One way to achieve this and worked really well for me is by using testcontainers: https://github.com/testcontainers/testcontainers-python.

A fixture might look like this in pytest with, in my case, a Postgress database:

@pytest.fixture(scope="module", name="session_for_db_in_testcontainer")
def db_engine():
    """
    Creates testcontainer with Postgres db
    """
    pg_container = PostgresContainer('postgres:latest')
    pg_container.start()

    # Fireup the SQLModel engine with the uri of the container
    db_engine = create_engine(pg_container.get_connection_url())
    sqlmodel_metadata.create_all(db_engine)

    with Session(db_engine) as session_for_db_in_testcontainer:
        # add some rows to start, for test get requests and posting existing data
        add_data_to_test_db(database_input_path, session_for_db_in_testcontainer)
        yield session_for_db_in_testcontainer

    # Will be executed after the last test
    session_for_db_in_testcontainer.close()
    pg_container.stop()

Like this during the test run a (Postgres) DB is created it only runs during a session, module or function depending on the scope of the fixture. If you want, you can add test data to the db as well like in the example.

Not sure about Colab, but in a normal Jupyter notebook you do:

import nest_asyncio
nest_asyncio.apply()

Install with pip install nest-asyncio, and then you can run async stuff in a notebook.

Edit: You are also trying to run a GUI instance of Chrome, with that headless=False - change that to headless=True, Colab doens't run with a GUI.

There is several good practices for creating locators/selectors. Using playwright there is official documentation for each common and unique selector on how-to and what-is doing.

More information in https://playwright.dev/docs/selectors#text-selector

About your case, i would suggest always to use an parent selector for locating an element. When there is a button, try to find its unique parent.

• By id
• By unique class
• Something else unique.

Example:

<dv id=test>
 <button id=continue-test>Continue</button>
</div>

In this case you can use the unique id of the button and not the text. Selector css: #continue-test But if you, don't have an unique identifier for the button you can use the parent and go down to the button. Selector css: #test > button

Matching text using css is not possible, but with XPATH can look like this:

//button[text()="Continue"] 

This selector MATCHES the text using "equals".

Using playwright:

button:has-text("Continue")

Using has-text and quotes - matches the text using equals. If you are using another selector for example text=Continue, this will match all elements that CONTAINS the text "Continue"

All this is explained with example in the official documentation for playwright selectors. That does not mean to not use XPATH to achieve the goals.

CSS selectors are fast but kind of restricted to work with text.

Xpath is quite slower but much more powerful to work in text/parent/child elements etc.

I would suggest always to use an parent element with unique identifier and go down to reach your actual element, which will receive the interaction.

Playwright has a built in code generator which will make things easy for you.

Run this command and try it out

npx playwright codegen

Try this:

# Needed libs
from playwright.sync_api import Playwright, sync_playwright, expect

with sync_playwright() as p:
    #We define the browser, the context and the page
    browser = p.chromium.launch(headless=False)
    context = browser.new_context()
    page = context.new_page()
    # Go to URL for this example
    page.goto("https://demoqa.com/browser-windows")

    # With the current context we wait for a new page, and we do whatever we have to do inside for opening that new page (tab)
    with context.expect_page() as new_page_info:
        # Needed actions for opening the new tab, in my case clicling a button
        page.locator('#tabButton').click()  # Opens a new tab
    # Now we have the new page
    new_page = new_page_info.value
    # We do whatever we want with our new page, in my case it is only taking a text from an element and printing it out
    text_of_h1_from_new_page = new_page.locator('#sampleHeading').inner_text()
    print(text_of_h1_from_new_page)
    # Close the context and browser
    context.close()
    browser.close()

More info here: https://playwright.dev/python/docs/pages#handling-new-pages

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 should be able to get that button by text:

page.locator('"Log in"').click()

Try following css selector to identify the element and then click the item.

await page.click("[data-test-id='selectForBattleButton']");