Update ReadMe files

Author: mdmintz

README.md

@@ -1,4 +1,4 @@
-![](https://cdn2.hubspot.net/hubfs/100006/images/SB_Logo8g.png "SeleniumBase")
+<img src="https://cdn2.hubspot.net/hubfs/100006/images/SeleniumBase_Home.png" title="SeleniumBase" height="50">
 
 **WebDriver automation simplified by extending Python's unittest framework.**
 
@@ -145,14 +145,14 @@ Here are some other useful nosetest arguments for appending to your run commands
 --with-id  # If -v is also used, will number the tests for easy counting.
 ```
 
-The ``--with-testing_base`` plugin gives you full logging on test failures, which saves screenshots, page source, and basic test info into the logs folder:
+During test failures you'll get detailed log files, which include screenshots, page source, and basic test info, which will get added to the logs folder at ``latest_logs/``. (Unless you have ARCHIVE_EXISTING_LOGS set to True in [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py), log files with be cleaned up at the start of the next test run. If the archive feature is enabled, those logs will get saved to the ``archived_logs/`` folder.) The ``my_test_suite.py`` collection contains tests that fail on purpose so that you can see how logging works.
 
 ```bash
 cd examples/
 
-pytest my_first_test.py --with-testing_base --browser=chrome
+pytest my_test_suite.py --browser=chrome
 
-pytest my_first_test.py --with-testing_base --browser=firefox
+pytest my_test_suite.py --browser=firefox
 ```
 
 If you want to run tests headlessly, use ``--headless``, which you'll need to do if your system lacks a GUI interface. Even if your system does have a GUI interface, it may still support headless browser automation.
@@ -188,12 +188,12 @@ pytest my_test_suite.py --junitxml=report.xml
 
 #### **Nosetest Reports:**
 
-The ``--report`` option gives you a fancy report after your test suite completes. (Requires ``--with-testing_base`` to also be set when ``--report`` is used because it's part of that plugin.)
+The ``--report`` option gives you a fancy report after your test suite completes.
 
 ```bash
-nosetests my_test_suite.py --with-testing_base --report
+nosetests my_test_suite.py --report
 ```
-![](https://cdn2.hubspot.net/hubfs/100006/images/Test_Report_2.png "Example Nosetest Report")
+<img src="https://cdn2.hubspot.net/hubfs/100006/images/Test_Report_2.png" title="Example Nosetest Report" height="450">
 
 (NOTE: You can add ``--show_report`` to immediately display Nosetest reports after the test suite completes. Only use ``--show_report`` when running tests locally because it pauses the test run.)
 
@@ -206,7 +206,7 @@ If you wish to use a proxy server for your browser tests (Chrome and Firefox onl
 pytest proxy_test.py --proxy=IP_ADDRESS:PORT
 ```
 
-To make things easier, you can add your frequently-used proxies to PROXY_LIST in [seleniumbase/config/proxy_list.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/proxy_list.py), and then use ``--proxy=KEY_FROM_PROXY_LIST`` to use the IP_ADDRESS:PORT of that key.
+To make things easier, you can add your frequently-used proxies to PROXY_LIST in [proxy_list.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/proxy_list.py), and then use ``--proxy=KEY_FROM_PROXY_LIST`` to use the IP_ADDRESS:PORT of that key.
 
 ```bash
 pytest proxy_test.py --proxy=proxy1
@@ -236,7 +236,7 @@ pip install MySQL-python==1.2.5
 
 Here's an example of running tests with additional features enabled:
 ```bash
-nosetests [YOUR_TEST_FILE].py --browser=chrome --with-testing_base --with-db_reporting --with-s3_logging -s
+nosetests [YOUR_TEST_FILE].py --browser=chrome --with-db_reporting --with-s3_logging -s
 ```
 (NOTE: If you haven't configured your MySQL or S3 connections in [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py), don't use ``--with-db_reporting`` or ``--with-s3_logging``.)
 
@@ -256,7 +256,7 @@ If you tell nosetests to run an entire file, it will run every method in that py
 nosetests [YOUR_TEST_FILE].py:[SOME_CLASS_NAME].test_[SOME_TEST_NAME] --config=[MY_CONFIG_FILE].cfg
 ```
 
-Let's try an example of a test that fails. Copy the following into a file called fail_test.py:
+Let's try an example of a test that fails:
 ```python
 """ test_fail.py """
 from seleniumbase import BaseCase
@@ -265,12 +265,13 @@ class MyTestClass(BaseCase):
 
     def test_find_army_of_robots_on_xkcd_desert_island(self):
         self.open("http://xkcd.com/731/")
-        self.assert_element("div#ARMY_OF_ROBOTS", timeout=3)  # This should fail
+        self.assert_element("div#ARMY_OF_ROBOTS", timeout=1)  # This should fail
 ```
-Now run it:
+
+You can run it from the ``examples`` folder like this:
 
 ```bash
-nosetests test_fail.py --browser=chrome --with-testing_base
+nosetests test_fail.py
 ```
 
 You'll notice that a logs folder, "latest_logs", was created to hold information about the failing test, and screenshots. Take a look at what you get. Remember, this data can be saved in your MySQL DB and in S3 if you include the necessary plugins in your run command (and if you set up the neccessary connections properly). For future test runs, past test results will get stored in the archived_logs folder if you have ARCHIVE_EXISTING_LOGS set to True in [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py).

examples/ReadMe.md

@@ -12,9 +12,9 @@ python gui_test_runner.py
 
 (NOTE: You can interchange ``nosetests`` with ``pytest`` in most of these examples.)
 
-![](https://cdn2.hubspot.net/hubfs/100006/images/GUI_Test_Runner_7.png "GUI Test Runner")
+<img src="https://cdn2.hubspot.net/hubfs/100006/images/The_GUI_Runner.png" title="GUI Test Runner" height="400">
 
-If you run scripts with logging enabled, (using ``--with-testing_base``), you’ll see two folders appear: “latest_logs” and “archived_logs”. The “latest_logs” folder will contain log files from the most recent test run, but logs will only be created if the test run is failing. Afterwards, logs from the “latest_logs” folder will get pushed to the “archived_logs” folder if you have have the ``ARCHIVE_EXISTING_LOGS`` feature enabled in [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py).
+When you run tests, you’ll see two folders appear: “latest_logs” and “archived_logs”. The “latest_logs” folder will contain log files from the most recent test run, but logs will only be created if the test run is failing. Afterwards, logs from the “latest_logs” folder will get pushed to the “archived_logs” folder if you have have the ``ARCHIVE_EXISTING_LOGS`` feature enabled in [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py).
 
 **For running scripts the usual way, here are some of the example run commands:**
 
@@ -35,12 +35,12 @@ pytest my_first_test.py --browser=chrome --demo_mode
 
 Run the example test suite in Chrome and generate an html report: (nosetests-only)
 ```bash
-nosetests my_test_suite.py --browser=chrome --with-testing_base --report
+nosetests my_test_suite.py --browser=chrome --report
 ```
 
 Run the example test suite in Firefox and generate an html report: (nosetests-only)
 ```bash
-nosetests my_test_suite.py --browser=firefox --with-testing_base --report
+nosetests my_test_suite.py --browser=firefox --report
 ```
 
 Run a test with configuration specifed by a config file:
@@ -58,9 +58,9 @@ Run a failing test with pdb mode enabled: (If a test failure occurs, test enters
 nosetests test_fail.py --browser=chrome --pdb --pdb-failures
 ```
 
-Run a failing test with logging:
+Run a failing test (and then look into the ``latest_logs`` folder afterwards:
 ```bash
-pytest test_fail.py --browser=chrome --with-testing_base
+pytest test_fail.py --browser=chrome
 ```
 
 (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

@@ -22,7 +22,7 @@ nosetests my_first_test.py --browser=firefox
 
 pytest my_first_test.py --demo_mode --browser=chrome
 
-nosetests my_test_suite.py --with-testing_base -s
+nosetests my_test_suite.py -s
 ```
 
 You can interchange **nosetests** with **pytest**. Chrome is the default browser if not specified. The ``-s`` option may produce additional output to make debugging easier.
@@ -31,24 +31,24 @@ You can interchange **nosetests** with **pytest**. Chrome is the default browser
 
 **Example tests using Logging**:
 ```bash
-pytest my_test_suite.py --with-testing_base --browser=chrome
+pytest my_test_suite.py --browser=chrome
 ```
-(NOTE: The ``--with-testing_base`` plugin gives you full logging on test failures, which saves screenshots, page source, and basic test info into the logs folder.)
+(NOTE: You'll automatically get full logging on test failures, which include screenshots, page source, and basic test info in the logs folder, which is ``latest_logs/`` initially, and those logs will be saved in ``archived_logs/`` if you have ARCHIVE_EXISTING_LOGS set to True in [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py))
 
 **Demo Mode:**
 
 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:
 
 ```bash
-nosetests my_first_test.py --with-selenium --browser=chrome --demo_mode
+nosetests my_first_test.py --browser=chrome --demo_mode
 ```
 
 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.)
 
 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.
 
 ```bash
-nosetests my_first_test.py --with-selenium --browser=chrome --demo_mode --demo_sleep=1.2
+nosetests my_first_test.py --browser=chrome --demo_mode --demo_sleep=1.2
 ```
 
 **You can also use the following in your scripts to slow down the tests:**
@@ -64,7 +64,7 @@ You may also want to have your test sleep in other situations where you need to
 **If you need to debug things on the fly (in case of errors), use this:**
 
 ```bash
-nosetests my_first_test.py --browser=chrome --with-selenium --pdb --pdb-failures -s
+nosetests my_first_test.py --browser=chrome --pdb --pdb-failures -s
 ```
 
 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.
@@ -83,16 +83,16 @@ The above code (with --pdb) will leave your browser window open in case there's
 Using ``--html=report.html`` gives you a fancy report of the name specified after your test suite completes.
 
 ```bash
-pytest my_test_suite.py --with-selenium --html=report.html
+pytest my_test_suite.py --html=report.html
 ```
 ![](https://cdn2.hubspot.net/hubfs/100006/images/PytestReport.png "Example Pytest Report")
 
 #### **Nosetest Reports:**
 
-The ``--report`` option gives you a fancy report after your test suite completes. (Requires ``--with-testing_base`` to also be set when ``--report`` is used because it's part of that plugin.)
+The ``--report`` option gives you a fancy report after your test suite completes.
 
 ```bash
-nosetests my_test_suite.py --with-selenium --with-testing_base --report
+nosetests my_test_suite.py --report
 ```
 ![](http://cdn2.hubspot.net/hubfs/100006/images/Test_Report_2.png "Example Nosetest Report")