The mission is simple

Bring the best of Selenium, Cypress and Python into one package.

This means:

• Automatic waiting and synchronization
• Quick setup to start writing tests
• Easy to use and clean syntax for amazing readability and maintainability
• Automatic driver installation so you don't need to manage drivers
• Leverage the awesome Python language
• and more!

Test Example

Although Pylenium is a thin wrapper of Selenium, let's use this simple scenario to show the difference between using Selenium and Pylenium:

1. Visit the QA at the Point website: https://qap.dev
2. Hover the About link to reveal a menu
3. Click the Leadership link in that menu
4. Assert Carlos Kidman is on the Leadership page

def test_carlos_is_on_leadership(py):
    py.visit('https://qap.dev')
    py.get('a[href="/about"]').hover()
    py.get('a[href="/leadership"][class^="Header-nav"]').click()
    assert py.contains('Carlos Kidman')

from selenium import webdriver
from selenium.webdriver.common.action_chains import ActionChains
from selenium.webdriver.common.by import By
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.support.wait import WebDriverWait

# define your setup and teardown fixture
@pytest.fixture
def driver():
    driver = webdriver.Chrome()
    yield driver
    driver.quit()


def test_carlos_is_on_leadership_page_with_selenium(driver):
    wait = WebDriverWait(driver, timeout=10)
    driver.get('https://qap.dev')

    # hover About link
    about_link = driver.find_element(By.CSS_SELECTOR, "a[href='/about']")
    actions = ActionChains(driver)
    actions.move_to_element(about_link).perform()

    # click Leadership link in About menu
    wait.until(EC.visibility_of_element_located((By.CSS_SELECTOR, "a[href='/leadership'][class^='Header-nav']"))).click()

    # check if 'Carlos Kidman' is on the page
    assert wait.until(lambda _: driver.find_element(By.XPATH, "//*[contains(text(), 'Carlos Kidman')]"))

Purpose

I teach courses and do trainings for both Selenium and Cypress, but Selenium, out of the box, feels clunky. When you start at a new place, you almost always need to "setup" the framework from scratch all over again. Instead of getting right to creating meaningful tests, you end up spending most of your time building a custom framework, maintaining it, and having to teach others to use it.

Also, many people blame Selenium for bad or flaky tests. This usually tells me that they have yet to experience someone that truly knows how to make Selenium amazing! This also tells me that they are not aware of the usual root causes that make Test Automation fail:

• Poor programming skills, test design and practices
• Flaky applications
• Complex frameworks

What if we tried to get the best from both worlds and combine it with an amazing language?

Selenium has done an amazing job of providing W3C bindings to many languages and makes scaling a breeze.

Cypress has done an amazing job of making the testing experience more enjoyable - especially for beginners.

Pylenium looks to bring more Cypress-like bindings and techniques to Selenium (like automatic waits) and still leverage Selenium's power along with the ease-of-use and power of Python.

Quick Start

The Official Pylenium Docs are the best place to start, but you can quickly get going with the following steps:

1. Install pyleniumio

pip install pyleniumio

---or---

pipenv install pyleniumio

2. Write a test

Create a directory called tests and then a test file called test_google.py

Define a new test called test_google_search

def test_google_search(py)

Pylenium uses pytest as the Test Framework. You only need to pass in pyto the function!

Now we can use Pylenium Commands to interact with the browser.

def test_google_search(py):
    py.visit('https://google.com')
    py.get("[name='q']").type('puppies')
    py.get("[name='btnK']").submit()
    assert py.should().contain_title('puppies')

3. Run the Test

This will depend on your IDE, but you can always run tests from the CLI:

python -m pytest tests/test_google.py

You're all set! You should see the browser open and complete the commands we had in the test :)