Pylenium.io
GitHub ↗️
  • Welcome to Pylenium
  • Getting Started
    • 1. Virtual Environments
    • 2. Setup pytest
    • 3. Project Structure with pytest
    • 4. Writing Tests with Pylenium
  • Guides
    • πŸ“ŠVisualize Test Results with Allure
    • πŸ“Logging
    • 🟨Run Tests in Containers
    • πŸ”€Run Tests in Parallel
    • πŸ§ͺShould / Expected Conditions
    • 🌐Script with Standalone Pylenium
  • CLI
    • πŸ’»Pylenium CLI
    • πŸ“ŠAllure CLI
  • Configuration
    • πŸ“„pylenium.json
    • πŸš—Driver
    • πŸ–₯️Viewport
  • Fixtures
    • ↗️api
    • πŸͺ“axe
    • πŸ₯Έfake
    • βœ…py
    • β˜‘οΈpyc
    • ❌pys
  • Driver Commands
    • Overview
    • πŸ—ΊοΈNavigation
      • go
      • quit
      • reload
      • visit
    • πŸ”Find Elements
      • contains
      • find
      • findx
      • get
      • getx
    • ⏱️Driver.should()
    • 🌐Browser
      • execute_script
      • execute_async_script
      • maximize_window
      • screenshot
      • scroll_to
      • title
      • url
      • window_handles
      • window_size
      • viewport
    • πŸͺCookies
      • delete_all_cookies
      • delete_cookie
      • get_all_cookies
      • get_cookie
      • set_cookie
    • πŸ”„Switch To
      • default_content
      • frame
      • frame_by_element
      • parent_frame
      • window
      • new_window
      • new_tab
    • πŸ“ŠWeb Performance
      • Performance API
      • CDP Performance
    • fake
    • wait
    • webdriver
  • Element Commands
    • πŸ”Find Elements
    • ⏱️Element.should()
    • πŸ‘Actions
      • check
      • clear
      • click
      • deselect
      • double_click
      • drag_to
      • drag_to_element
      • focus
      • hover
      • right_click
      • scroll_into_view
      • select_by_index
      • select_by_text
      • select_by_value
      • submit
      • type
      • uncheck
      • upload
    • πŸ”’Element Data
      • css_value
      • get_attribute
      • get_property
      • tag_name
      • text
      • is_checked
      • is_displayed
      • is_enabled
      • is_selected
    • πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦Family
      • children
      • parent
      • siblings
    • open_shadow_dom
    • screenshot
    • webelement
  • Elements Commands
    • ⏱️Elements.should()
    • first
    • length
    • last
    • is_empty
  • Contribute
    • Clone and Setup the Project
Powered by GitBook
On this page
  • allure install
  • allure check
  • allure serve
  • Example
  1. CLI

Allure CLI

Pylenium has commands for working with allure reporting

PreviousPylenium CLINextConfiguration

Last updated 11 months ago

These are "convenience" commands if you are new to allure, but you can use these Pylenium commands or use the allure CLI directly (recommended)

allure install

Install the allure CLI on the current machine.

Terminal
pylenium allure install

Pylenium detects your operating system and tries to install allure with the appropriate installation commands. However, it's recommended that you use their official installation docs instead.

allure check

Check that there is valid allure CLI installed on the current machine.

Terminal
pylenium allure check
  • If successful, a message is displayed with the current version of allure

  • Otherwise, allure is not installed or not added to the PATH correctly

This is equivalent to the following allure command ⬇️

Terminal
allure --version

allure serve

Starts the allure server, generates the report, and serves it as a new browser tab.

Terminal
pylenium allure serve --folder [FOLDER]

This is equivalent to the following allure command ⬇️

Terminal
allure serve [FOLDER]

Example

Run your tests with pytest and specify that the output be saved to the allure-report folder

Terminal
pytest --alluredir=allure-report

With the test run finished we can serve the report and see the results

Terminal
pylenium allure serve --folder allure-report
πŸ“Š
https://docs.qameta.io/allure-report/#_installing_a_commandline