Skip to content

Commit 73520c6

Browse files
committed
Update ReadMe files
1 parent e98f5f8 commit 73520c6

File tree

6 files changed

+26
-23
lines changed

6 files changed

+26
-23
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ SeleniumBase simplifies Web-UI automation by extending Python's unittest framewo
1313
### [**Get Started**](#seleniumbase_installation), or Learn More:
1414

1515
**No more repetitive WebDriver code:**<br />
16-
SeleniumBase automatically handles common WebDriver actions such as spinning up web browsers, waiting for page objects to load, saving screenshots during test failures, and more. (<i>[Read about the command line interface](https://github.com/seleniumbase/SeleniumBase/blob/master/help_docs/command_line.md).</i>)
16+
SeleniumBase automatically handles common WebDriver actions such as spinning up web browsers, waiting for page objects to load, saving screenshots during test failures, using a proxy server, and more. (<i>[Read about customizing test runs](https://github.com/seleniumbase/SeleniumBase/blob/master/help_docs/customizing_test_runs.md).</i>)
1717

1818
**Simple Python syntax makes coding easy:**<br />
1919

@@ -90,22 +90,22 @@ cd SeleniumBase
9090

9191
If you're installing SeleniumBase from a cloned copy on your machine, use:
9292
```
93-
pip install -U -r requirements.txt
93+
pip install -r requirements.txt
9494
9595
python setup.py develop
9696
```
9797

9898
If you're installing SeleniumBase from the [Python Package Index](https://pypi.python.org/pypi/seleniumbase), use:
9999
```bash
100-
pip install -U seleniumbase
100+
pip install seleniumbase
101101
```
102102

103103
If you're installing SeleniumBase directly from GitHub, use:
104104
```bash
105-
pip install -U -e git+https://github.com/seleniumbase/SeleniumBase.git@master#egg=seleniumbase
105+
pip install -e git+https://github.com/seleniumbase/SeleniumBase.git@master#egg=seleniumbase
106106
```
107107

108-
(If you encounter permission errors during installation while not using a virtual environment, you may need to add ``--user`` to your ``pip`` command.)
108+
(If you encounter permission errors during installation while not using a virtual environment, you may need to add ``--user`` to your pip command. If you already have an older version of SeleniumBase installed, you may want to add ``--upgrade`` or ``-U`` to your pip command.)
109109

110110

111111
<a id="seleniumbase_basic_usage"></a>

examples/ReadMe.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Running SeleniumBase Scripts
22

3-
(NOTE: If you didn't install SeleniumBase properly, these scripts won't work. Installation steps include "``pip install seleniumbase``" and/or "``python setup.py develop``" from the top-level directory.)
3+
(NOTE: If you didn't install SeleniumBase properly, these scripts won't work. Installation steps include ``pip install seleniumbase`` OR ``pip install -r requirements.txt`` + ``python setup.py develop``" from the top-level directory.)
44

55
To makes things easier, here's a simple GUI program that allows you to kick off a few example scripts by pressing a button:
66

@@ -10,7 +10,7 @@ python gui_test_runner.py
1010

1111
(NOTE: With the exception of [my_first_test.py](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/my_first_test.py), which should pass, many other tests in this folder fail on purpose to demonstrate features such as screenshots on failure, exception logging, and test reports.)
1212

13-
(NOTE: You can interchange ``nosetests`` with ``pytest`` in most of these examples.)
13+
(NOTE: You can interchange ``pytest`` with ``nosetests`` in most of these examples.)
1414

1515
<img src="https://cdn2.hubspot.net/hubfs/100006/images/The_GUI_Runner.png" title="GUI Test Runner" height="400">
1616

@@ -35,12 +35,12 @@ pytest my_first_test.py --browser=chrome --demo_mode
3535

3636
Run the example test suite in Chrome and generate an html report: (nosetests-only)
3737
```bash
38-
nosetests my_test_suite.py --browser=chrome --report
38+
nosetests my_test_suite.py --browser=chrome --report --show_report
3939
```
4040

4141
Run the example test suite in Firefox and generate an html report: (nosetests-only)
4242
```bash
43-
nosetests my_test_suite.py --browser=firefox --report
43+
nosetests my_test_suite.py --browser=firefox --report --show_report
4444
```
4545

4646
Run a test with configuration specifed by a config file:
@@ -50,17 +50,19 @@ nosetests my_first_test.py --config=example_config.cfg
5050

5151
Run a test demonstrating the use of Python decorators available:
5252
```bash
53-
nosetests rate_limiting_test.py
53+
pytest rate_limiting_test.py
5454
```
5555

5656
Run a failing test with pdb mode enabled: (If a test failure occurs, test enters pdb mode)
5757
```bash
58-
nosetests test_fail.py --browser=chrome --pdb --pdb-failures
58+
pytest test_fail.py --browser=chrome --pdb --pdb-failures
5959
```
6060

6161
Run a failing test (and then look into the ``latest_logs`` folder afterwards:
6262
```bash
6363
pytest test_fail.py --browser=chrome
6464
```
6565

66+
For more advanced run commands, such as using a proxy server, see [../help_docs/customizing_test_runs.md](https://github.com/seleniumbase/SeleniumBase/blob/master/help_docs/customizing_test_runs.md)
67+
6668
(NOTE: If you see any ``*.pyc`` files appear as you run tests, that's perfectly normal. Compiled bytecode is a natural result of running Python code.)

help_docs/command_line.md renamed to help_docs/customizing_test_runs.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
### The Command Line Interface
1+
### Customizing test runs from the command line
22

33
In addition to [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py), which allows you to customize the test framework, SeleniumBase gives you the flexibility to customize & control test runs from the command line:
44

@@ -21,7 +21,7 @@ pytest my_first_test.py
2121

2222
pytest my_first_test.py --demo_mode --browser=chrome
2323

24-
nosetests my_first_test.py --browser=firefox
24+
pytest my_first_test.py --browser=firefox
2525

2626
pytest basic_script.py -s --pdb --pdb-failures
2727

@@ -49,15 +49,15 @@ pytest my_test_suite.py --browser=chrome
4949
If any test is moving too fast for your eyes to see what's going on, you can run it in **Demo Mode** by adding ``--demo_mode`` on the command line, which pauses the browser briefly between actions, and highlights page elements being acted on:
5050

5151
```bash
52-
nosetests my_first_test.py --browser=chrome --demo_mode
52+
pytest my_first_test.py --browser=chrome --demo_mode
5353
```
5454

5555
You can override the default wait time by either updating [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py) or by using ``--demo_sleep={NUM}`` when using Demo Mode. (NOTE: If you use ``--demo_sleep={NUM}`` without using ``--demo_mode``, nothing will happen.)
5656

5757
If you ever make any changes to your local copy of ``settings.py``, you may need to run ``python setup.py install`` for those changes to take effect.
5858

5959
```bash
60-
nosetests my_first_test.py --browser=chrome --demo_mode --demo_sleep=1.2
60+
pytest my_first_test.py --browser=chrome --demo_mode --demo_sleep=1.2
6161
```
6262

6363
**You can also use the following in your scripts to slow down the tests:**
@@ -73,7 +73,7 @@ You may also want to have your test sleep in other situations where you need to
7373
**If you need to debug things on the fly (in case of errors), use this:**
7474

7575
```bash
76-
nosetests my_first_test.py --browser=chrome --pdb --pdb-failures -s
76+
pytest my_first_test.py --browser=chrome --pdb --pdb-failures -s
7777
```
7878

7979
The above code (with --pdb) will leave your browser window open in case there's a failure, which is possible if the web pages from the example change the data that's displayed on the page. (ipdb commands: 'c', 's', 'n' => continue, step, next). You may need the ``-s`` in order to see all console output.

integrations/google_cloud/ReadMe.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111

1212
![](http://cdn2.hubspot.net/hubfs/100006/images/gcp_cloud_launcher_jenkins_3.png "Finding Jenkins")
1313

14-
* Under "Cloud Launcher", Click on "Jenkins"
14+
* Under "Cloud Launcher", Click on "Jenkins Certified by Bitnami"
1515
* Click on "Launch on Compute Engine"
1616
* Give the instance a name
1717
* Give the instance a zone
@@ -76,7 +76,7 @@ sudo pip install -r requirements.txt --upgrade
7676
#### Step 12. Install SeleniumBase (Make sure you already installed the requirements above)
7777

7878
```bash
79-
sudo python server_setup.py develop
79+
sudo python setup.py develop
8080
```
8181

8282
#### Step 13. Run an [example test](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/my_first_test.py) in Chrome to verify installation (Takes ~10 seconds)

integrations/katalon/ReadMe.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
## This page has been moved to: [../selenium_ide/ReadMe.md](https://github.com/seleniumbase/SeleniumBase/blob/master/integrations/selenium_ide/ReadMe.md)

integrations/selenium_ide/ReadMe.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
## Converting Selenium IDE recordings into SeleniumBase test scripts
1+
## Converting Katalon-based Selenium IDE recordings into SeleniumBase test scripts
22

3-
[Selenium IDE](http://docs.seleniumhq.org/projects/ide/) is a tool that allows you to record and playback actions performed inside a web browser. It's available as a [downloadable Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/selenium-ide/). Selenium IDE comes with an option to export recordings as various WebDriver test scripts, one of which is ``Python2/unittest/WebDriver``. Unfortunately, these natively-exported scripts tend to be very messy and don't 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.
3+
[Katelon Recorder / Selenium IDE](https://www.katalon.com/resources-center/blog/katalon-automation-recorder/) (<i>the successor to the [old Selenium IDE](http://docs.seleniumhq.org/projects/ide/)</i>) 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/). Katelon 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.
44

5-
#### Step 1: Make a recording with Selenium IDE
5+
#### Step 1: Make a recording with Katelon Recorder
66

7-
![](https://cdn2.hubspot.net/hubfs/100006/selenium_ide_example_b.png "Selenium IDE example")
7+
![](https://cdn2.hubspot.net/hubfs/100006/images/katalon_recorder_2.png "Katelon Recorder example")
88

99
#### Step 2: Export your recording as a Python 2 Webdriver script
1010

11-
* ``File`` => ``Export Test Case As`` => ``Python 2 / unittest / WebDriver``
11+
* ``{} Export`` => ``Python 2 (WebDriver + unittest)`` => ``Save As File``
1212

1313
#### Step 3: Drop your exported file into the ``selenium_ide`` folder
1414

0 commit comments

Comments
 (0)