seleniumbase 4.24.11__py3-none-any.whl → 4.33.15__py3-none-any.whl

seleniumbase/drivers/ReadMe.md

@@ -1,27 +0,0 @@
-### <img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="32" /> SeleniumBase webdriver storage
-
-To run web automation, you'll need webdrivers for each browser you plan on using.  With SeleniumBase, drivers are downloaded automatically as needed into the SeleniumBase ``drivers`` folder.
-
-You can also download drivers manually with these commands:
-
-```bash
-seleniumbase get chromedriver
-seleniumbase get geckodriver
-seleniumbase get edgedriver
-```
-
-After running the commands above, web drivers will get downloaded into the ``seleniumbase/drivers/`` folder. SeleniumBase uses those drivers during tests. (The drivers don't come with SeleniumBase by default.)
-
-If the necessary driver is not found in this location while running tests, SeleniumBase will instead look for the driver on the System PATH. If the necessary driver is not on the System PATH either, SeleniumBase will automatically attempt to download the required driver.
-
-* You can also download specific versions of drivers. Examples:
-
-```bash
-sbase get chromedriver 107
-sbase get chromedriver 107.0.5304.62
-sbase get chromedriver latest
-sbase get chromedriver latest-1
-sbase get edgedriver 106.0.1370.42
-```
-
-(NOTE: ``sbase`` is a shortcut for ``seleniumbase``)

seleniumbase/extensions/ReadMe.md

@@ -1,12 +0,0 @@
-<!-- SeleniumBase Docs -->
-
-[<img src="https://seleniumbase.github.io/cdn/img/sb_text_f.png" title="SeleniumBase" align="center" width="360">](https://github.com/seleniumbase/SeleniumBase)
-
-<h2><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="32" /> SeleniumBase browser extension storage</h2>
-
-<b>The List:</b>
-
-* ad_block.zip => This extension blocks certain types of iframe ads from loading.
-* disable_csp.zip => This extension disables a website's Content-Security-Policy.
-* recorder.zip => Save browser actions to sessionStorage with good CSS selectors.
-* sbase_ext.zip => An extension that does nothing, but helps people learn things.

seleniumbase/masterqa/ReadMe.md

@@ -1,61 +0,0 @@
-<!-- SeleniumBase Docs -->
-
-![](https://seleniumbase.github.io/cdn/img/masterqa_logo.png "MasterQA")
-
-<h3><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="32" /> MasterQA combines automation with manual verification steps.</h3>
-
-![](https://seleniumbase.github.io/cdn/gif/masterqa6.gif "MasterQA")
-
-Here's code from [basic_masterqa_test_0.py](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/master_qa/basic_masterqa_test_0.py):
-
-```python
-from seleniumbase import MasterQA
-
-class MasterQATests(MasterQA):
-    def test_masterqa(self):
-        self.open("https://xkcd.com/1700/")
-        self.verify("Do you see a webcomic?")
-        self.open("https://seleniumbase.io/demo_page")
-        self.highlight('table')
-        self.verify("Do you see elements in a table?")
-        self.open("https://seleniumbase.io/devices/")
-        self.highlight("div.mockup-wrapper")
-        self.verify("Do you see 4 computer devices?")
-```
-
-After each automation checkpoint, a pop-up window will ask the user questions for each verification command.
-
-When the test run completes, as seen from [this longer example](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/master_qa/masterqa_test_1.py), you'll reach the results page that appears after answering all the verification questions. (Failed verifications generate links to screenshots and log files.)
-
-![](https://seleniumbase.github.io/cdn/img/mqa_hybrid.png "MasterQA")
-
-You may have noticed the ``Incomplete Test Runs`` row on the results page. If the value for that is not zero, it means that one of the automated steps failed. This could happen if you tell your script to perform an action on an element that doesn't exist. Now that we're mixing automation with manual QA, it's good to tell apart the failures from each. The results_table CSV file contains a spreadsheet with the details of each failure (if any) for both manual and automated steps.
-
-**How to run the example tests from scratch:**
-
-```bash
-git clone https://github.com/seleniumbase/SeleniumBase.git
-cd SeleniumBase
-pip install .
-cd examples/master_qa
-pytest basic_masterqa_test_0.py
-pytest masterqa_test_1.py
-```
-
-At the end of your test run, you'll receive a report with results, screenshots, and log files. Close the Results Page window when you're done.
-
-**Check out [masterqa_test_1.py](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/master_qa/masterqa_test_1.py) to learn how to write your own MasterQA tests:**
-
-You'll notice that tests are written the same way as regular [SeleniumBase](https://seleniumbase.com) tests, with the key difference being a different import: ``from seleniumbase import MasterQA`` rather than ``from seleniumbase import BaseCase``. Now your Python test class will import ``MasterQA`` instead of ``BaseCase``.
-
-To add a manual verification step, use ``self.verify()`` in the code after each part of your test that needs a manual verification step. If you want to include a custom question, add text inside that call (in quotes). Example:
-
-```python
-self.verify()
-
-self.verify("Can you find the moon?")
-```
-
---------
-
-MasterQA is powered by [SeleniumBase](https://seleniumbase.com), the most advanced open-source automation framework on the [Planet](https://en.wikipedia.org/wiki/Earth).

seleniumbase/resources/ReadMe.md

@@ -1,31 +0,0 @@
-<!-- SeleniumBase Docs -->
-
-## [<img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="32">](https://github.com/seleniumbase/SeleniumBase/) Resource Files
-
-SeleniumBase uses JavaScript libraries for bonus features such as the Website Tour Maker, Presentation Maker, Chart Maker, Demo Mode, HTML Inspector, and more. In general, SeleniumBase retrieves these resources via CDN link.
-
-**favicon.ico** - This file is used by [style_sheet.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/core/style_sheet.py) for the favicon icon. Currently, SeleniumBase uses the version at [https://raw.githubusercontent.com/seleniumbase/SeleniumBase/master/seleniumbase/resources/favicon.ico](https://raw.githubusercontent.com/seleniumbase/SeleniumBase/master/seleniumbase/resources/favicon.ico).
-
---------
-
-The remaining resources have been moved into [github.com/seleniumbase/resource-files](https://github.com/seleniumbase/resource-files) in order to reduce the size of SeleniumBase:
-
-**messenger/** - Files in this folder are used for creating JavaScript notifications during test runs in Demo Mode.
-
-**jquery_confirm/** - Files in this folder are used for creating JavaScript confirmation prompts during test runs when using MasterQA.
-
-**html_inspector/** - Files in this folder are used for the HTML Inspector, which validates website pages.
-
-**reveal/** - Files in this folder are used for the HTML Presentation Maker.
-
-**prettify/** - Files in this folder are used to assist the HTML Presentation Maker.
-
-**shepherd/** - Files in this folder are used for creating website tours using the Shepherd JavaScript library.
-
-**bootstrap_tour/** - Files in this folder are used for creating website tours using the Bootstrap Tour JavaScript library.
-
-**introjs/** - Files in this folder are used for creating website tours using the IntroJS JavaScript library.
-
-**driverjs/** - Files in this folder are used for creating website tours using the DriverJS JavaScript library.
-
-**hopscotch/** - Files in this folder are used for creating website tours using the Hopscotch JavaScript library.

seleniumbase/utilities/selenium_grid/ReadMe.md

@@ -1,84 +0,0 @@
-<!-- SeleniumBase Docs -->
-
-[<img src="https://seleniumbase.github.io/cdn/img/super_logo_sb.png" title="SeleniumBase" width="290">](https://github.com/seleniumbase/SeleniumBase/blob/master/README.md)
-
-<h2><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="28" /> The Selenium Grid Hub:</h2>
-
-The Selenium Grid Hub lets you distribute tests to run in parallel across multiple node machines. Each node machine can then run its own allocation of tests. This allows you to run a large suite of tests very quickly.
-
-<h3><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="28" /> Running the Selenium Grid Hub:</h3>
-
-The following commands will work once you've installed seleniumbase.
-
-<h4><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="28" /> Downloading the Selenium Server JAR file:</h4>
-
-```bash
-seleniumbase download server
-```
-
-* (Required for using your own Selenium Grid)
-
-<h4><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="28" /> Grid Hub server controls:</h4>
-
-```bash
-seleniumbase grid-hub {start|stop|restart} [OPTIONS]
-```
-
-<b>Options:</b>
-<ul>
-<li> -v / --verbose  (Increases verbosity of logging output.)</li>
-<li> --timeout=TIMEOUT  (Close idle browser after TIMEOUT sec.)</li>
-</ul>
-
-<h4><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="28" /> Grid node server controls:</h4>
-
-```bash
-seleniumbase grid-node {start|stop|restart} --hub=[HUB_IP] [OPTIONS]
-```
-
-<b>Options:</b>
-<ul>
-<li> -v / --verbose  (Increases verbosity of logging output.)</li>
-<li> --hub=[HUB_IP]  (Specifies the Grid Hub to connect to. Default: "127.0.0.1".)</li>
-</ul>
-
-When the Grid Hub Console is up and running, you'll be able to find it here: [http://127.0.0.1:4444/grid/console](http://127.0.0.1:4444/grid/console)
-
-Now you can run your tests on the Selenium Grid:
-
-```bash
-pytest test_demo_site.py --server=IP_ADDRESS --port=4444
-```
-
-You can also run your tests on someone else's Selenium Grid to avoid managing your own. Here are some Selenium Grids that you can use (and the run command format):
-
-* [BrowserStack](https://www.browserstack.com/automate#) Selenium Grid:
-
-```bash
-pytest test_demo_site.py --server=USERNAME:KEY@hub.browserstack.com --port=80
-```
-
-* [Sauce Labs](https://saucelabs.com/products/platform-configurator) Selenium Grid:
-
-```bash
-pytest test_demo_site.py --server=USERNAME:KEY@ondemand.us-east-1.saucelabs.com --port=443 --protocol=https
-```
-
-* [CrossBrowserTesting](https://help.crossbrowsertesting.com/selenium-testing/getting-started/python/) Selenium Grid:
-
-```bash
-pytest test_demo_site.py --server=USERNAME:KEY@hub.crossbrowsertesting.com --port=80
-```
-
-To use a server on the ``https`` protocol, add ``--protocol=https``:
-(<i>SeleniumBase 1.65.2 and newer uses ``https`` automatically for ``--port=443``.</i>)
-
-```bash
-pytest test_demo_site.py --protocol=https --server=IP_ADDRESS --port=PORT
-```
-
-(For setting browser desired capabilities while running Selenium remotely, see the <a href="https://seleniumbase.io/help_docs/desired_capabilities/">desired capabilities documentation</a> and the sample files located in <a href="https://github.com/seleniumbase/SeleniumBase/tree/master/examples/capabilities">SeleniumBase/examples/capabilities</a>)
-
-<h4><img src="https://seleniumbase.github.io/img/logo6.png" title="SeleniumBase" width="28" /> More info about the Selenium Grid Hub can be found here:</h4>
-
-* [https://www.selenium.dev/documentation/grid/](https://www.selenium.dev/documentation/grid/)

seleniumbase/utilities/selenium_ide/ReadMe.md

@@ -1,111 +0,0 @@
-<!-- SeleniumBase Docs -->
-
-### Converting Katalon recordings into SeleniumBase test scripts
-
-### (NOTE: **[SeleniumBase now has Recorder Mode](https://github.com/seleniumbase/SeleniumBase/blob/master/help_docs/recorder_mode.md)**, which is recommended over other record & playback tools.)
-
---------
-
-Katalon Recorder (Selenium IDE) is a tool that allows you to record and playback actions performed inside a web browser. It's available as a [downloadable Chrome extension](https://chrome.google.com/webstore/detail/katalon-recorder-selenium/ljdobmomdgdljniojadhoplhkpialdid) and a [downloadable Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/katalon-automation-record/). The Katalon Recorder comes with an option to export recordings as various WebDriver test scripts, one of which is ``Python 2 (WebDriver + unittest)``. Unfortunately, these natively-exported scripts can be very messy and don't always run reliably. The purpose of this converter is to clean up and improve the scripts so that they can be used in production-level environments.
-
-#### Step 1: Make a recording with the Katalon Recorder
-
-![](https://seleniumbase.io/cdn/img/katalon_recorder_2.png "Katalon Recorder example")
-
-#### Step 2: Export your recording as a Python 2 Webdriver script
-
-* ``{} Export`` => ``Python 2 (WebDriver + unittest)`` => ``Save As File``
-
-#### Step 3: Run ``seleniumbase convert`` on your exported Python file
-
-```bash
-seleniumbase convert MY_TEST.py
-```
-
-* You should see a [MY_TEST_SB.py] file appear in the folder. (``_SB`` is added to the file name so that the original file stays intact in case you still need it.) This new clean & reliable SeleniumBase test script is ready to be added into your test suite for running.
-
---------
-
---------
-
-The following is an example of a Katalon Recorder exported file (**WebDriver + unittest format**).
-It is **messy** and has **unnecessary lines of code** to do the task that was recorded:
-
-```python
-# -*- coding: utf-8 -*-
-from selenium import webdriver
-from selenium.webdriver.common.by import By
-from selenium.webdriver.common.keys import Keys
-from selenium.webdriver.support.ui import Select
-from selenium.common.exceptions import NoSuchElementException
-from selenium.common.exceptions import NoAlertPresentException
-import unittest, time, re
-
-class Swag(unittest.TestCase):
-    def setUp(self):
-        self.driver = webdriver.Firefox()
-        self.driver.implicitly_wait(30)
-        self.base_url = "https://www.google.com/"
-        self.verificationErrors = []
-        self.accept_next_alert = True
-
-    def test_swag(self):
-        driver = self.driver
-        driver.get("https://www.saucedemo.com/")
-        driver.find_element_by_id("user-name").click()
-        driver.find_element_by_id("user-name").clear()
-        driver.find_element_by_id("user-name").send_keys("standard_user")
-        driver.find_element_by_id("password").click()
-        driver.find_element_by_id("password").clear()
-        driver.find_element_by_id("password").send_keys("secret_sauce")
-        driver.find_element_by_id("login-button").click()
-
-    def is_element_present(self, how, what):
-        try: self.driver.find_element(by=how, value=what)
-        except NoSuchElementException as e: return False
-        return True
-
-    def is_alert_present(self):
-        try: self.driver.switch_to_alert()
-        except NoAlertPresentException as e: return False
-        return True
-
-    def close_alert_and_get_its_text(self):
-        try:
-            alert = self.driver.switch_to_alert()
-            alert_text = alert.text
-            if self.accept_next_alert:
-                alert.accept()
-            else:
-                alert.dismiss()
-            return alert_text
-        finally: self.accept_next_alert = True
-
-    def tearDown(self):
-        self.driver.quit()
-        self.assertEqual([], self.verificationErrors)
-
-if __name__ == "__main__":
-    unittest.main()
-```
-
-<div><b>This can be improved on...</b></div>
-
-<b>After running <code>seleniumbase convert [FILE.py]</code> on it, here is the new result:</b>
-
-```python
-# -*- coding: utf-8 -*-
-from seleniumbase import BaseCase
-
-
-class Swag(BaseCase):
-
-    def test_swag(self):
-        self.open('https://www.saucedemo.com/')
-        self.type('#user-name', 'standard_user')
-        self.type('#password', 'secret_sauce')
-        self.click('#login-button')
-```
-
-<b>This is much cleaner than the original version.
-It also uses the more reliable SeleniumBase methods.</b>