Update links from mdmintz to seleniumbase

This commit is contained in:
Michael Mintz 2016-07-17 16:34:57 -04:00
parent 71cc64384b
commit 8e546f61bd
9 changed files with 15 additions and 15 deletions

View File

@ -8,11 +8,11 @@ To makes things easier, here's a simple GUI program that allows you to kick off
python gui_test_runner.py
```
(NOTE: With the exception of [my_first_test.py](https://github.com/mdmintz/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.)
(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.)
![](http://cdn2.hubspot.net/hubfs/100006/images/GUI_Test_Runner_3.png "GUI Test Runner")
If you run scripts with logging enabled, (using ``--with-testing_base``), youll 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/mdmintz/SeleniumBase/blob/master/seleniumbase/config/settings.py). Make sure to run ``python setup.py install`` for your changes to take effect if you make any changes to that file.
If you run scripts with logging enabled, (using ``--with-testing_base``), youll 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). Make sure to run ``python setup.py install`` for your changes to take effect if you make any changes to that file.
**For running scripts the usual way, here are some of the example run commands:**
(Note: You can replace ``nosetests`` with ``py.test`` for most of these.)

View File

@ -1,6 +1,6 @@
### SeleniumBase method summary
Here's a summary of SeleniumBase method definitions, which are defined in [base_case.py](https://github.com/mdmintz/SeleniumBase/blob/master/seleniumbase/fixtures/base_case.py)
Here's a summary of SeleniumBase method definitions, which are defined in [base_case.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/fixtures/base_case.py)
In order to maintain backwards compatibility with scripts using earlier verions of SeleniumBase, some methods that had their names shortened can also be called by their original method name. *(Ex: wait_for_element_visible was later shortened to wait_for_element and then to find_element, but the longer method names remained to keep older scripts from failing.)*

View File

@ -21,7 +21,7 @@ If you want a visual tool to help make your MySQL life easier, [try MySQL Workbe
#### Prepare your MySQL DB
You can use the [testcaserepository.sql](https://github.com/mdmintz/SeleniumBase/blob/master/seleniumbase/core/testcaserepository.sql) file to create the necessary tables for storing test data.
You can use the [testcaserepository.sql](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/core/testcaserepository.sql) file to create the necessary tables for storing test data.
If you were able to successfully install MySQL, you can now install the remaining MySQL requirements:
```bash
@ -30,7 +30,7 @@ pip install -r server_requirements.txt
#### Configure your MySQL DB for SeleniumBase
You'll want to update your [settings.py](https://github.com/mdmintz/SeleniumBase/blob/master/seleniumbase/config/settings.py) file with your MySQL DB credentials so that tests can write to the database when they run.
You'll want to update your [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py) file with your MySQL DB credentials so that tests can write to the database when they run.
#### Allow tests to write to your MySQL database

View File

@ -21,7 +21,7 @@
```bash
cd /
sudo git clone https://github.com/mdmintz/SeleniumBase.git
sudo git clone https://github.com/seleniumbase/SeleniumBase.git
```
#### 5. Enter the "linux" folder
@ -99,7 +99,7 @@ nosetests examples/my_first_test.py --with-selenium --headless --browser=firefox
#### 17. Setup your new Jenkins job
* Under "Source Code Management", select "Git".
* For the "Repository URL", put: ``https://github.com/mdmintz/SeleniumBase.git``. (You'll eventually be using your own clone of the repository here.)
* For the "Repository URL", put: ``https://github.com/seleniumbase/SeleniumBase.git``. (You'll eventually be using your own clone of the repository here.)
* Under "Build", click the "Add build step" dropdown and then select "Execute shell".
* For the "Command", put:
```bash
@ -150,11 +150,11 @@ If you have a web application that you want to test, you'll be able to create Se
#### 25. Create the necessary tables in your MySQL schema
* Run a SQL script in your MySQL schema using [testcaserepository.sql](https://raw.githubusercontent.com/mdmintz/SeleniumBase/master/seleniumbase/core/testcaserepository.sql)
* Run a SQL script in your MySQL schema using [testcaserepository.sql](https://raw.githubusercontent.com/seleniumbase/SeleniumBase/master/seleniumbase/core/testcaserepository.sql)
#### 26. Have your local clone of SeleniumBase connect to your MySQL DB
* Update the MySQL connection details in your [settings.py](https://github.com/mdmintz/SeleniumBase/blob/master/seleniumbase/config/settings.py) file to use the credentials that you saved in Step 21.
* Update the MySQL connection details in your [settings.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/config/settings.py) file to use the credentials that you saved in Step 21.
* Run the following command again from the top-level SeleniumBase folder to make sure that SeleniumBase uses the updated credentials:
```bash

View File

@ -1,3 +1,3 @@
## Running SeleniumBase on Debian GNU/Linux
The files in this folder are currently used with the [Google Cloud setup instructions for SeleniumBase](https://github.com/mdmintz/SeleniumBase/blob/master/integrations/google_cloud/ReadMe.md). You can also use these files standalone with any Debian GNU/Linux machine.
The files in this folder are currently used with the [Google Cloud setup instructions for SeleniumBase](https://github.com/seleniumbase/SeleniumBase/blob/master/integrations/google_cloud/ReadMe.md). You can also use these files standalone with any Debian GNU/Linux machine.

View File

@ -1,6 +1,6 @@
## Creating a SeleniumBase Test Launcher using NodeJS
Great news: It's really easy to create a customized web app for kicking off SeleniumBase jobs using NodeJS. This tutorial will walk you through all the steps that you need. (I'll assume that you've already installed SeleniumBase by following the instructions from the [top-level ReadMe](https://github.com/mdmintz/SeleniumBase/blob/master/README.md) file.)
Great news: It's really easy to create a customized web app for kicking off SeleniumBase jobs using NodeJS. This tutorial will walk you through all the steps that you need. (I'll assume that you've already installed SeleniumBase by following the instructions from the [top-level ReadMe](https://github.com/seleniumbase/SeleniumBase/blob/master/README.md) file.)
#### 1. Install NodeJS

View File

@ -1,6 +1,6 @@
## Notes on using the Selenium Grid Hub
The Selenium Grid Hub allows you to distribute tests to run in parallel across multiple machines. Each machine can then run its own allocation of tests in parallel. This allows you to run an entire test suite quickly, which may be important if you have a lot of tests to run. Machines can be personal computers, data centers, or virtual machines in the cloud. You can also create your own virtual machine by using a tool such as Docker (see the [Docker ReadMe](https://github.com/mdmintz/SeleniumBase/blob/master/integrations/docker/ReadMe.md)).
The Selenium Grid Hub allows you to distribute tests to run in parallel across multiple machines. Each machine can then run its own allocation of tests in parallel. This allows you to run an entire test suite quickly, which may be important if you have a lot of tests to run. Machines can be personal computers, data centers, or virtual machines in the cloud. You can also create your own virtual machine by using a tool such as Docker (see the [Docker ReadMe](https://github.com/seleniumbase/SeleniumBase/blob/master/integrations/docker/ReadMe.md)).
### Running the Selenium Grid Hub

View File

@ -2,7 +2,7 @@ title = '''<meta id="OGTitle" property="og:title" content="SeleniumBase">
<title>Test Report</title>
<link rel="SHORTCUT ICON"
href="%s" /> ''' % (
"https://raw.githubusercontent.com/mdmintz/SeleniumBase"
"https://raw.githubusercontent.com/seleniumbase/SeleniumBase"
"/master/seleniumbase/resources/favicon.ico")
style = title + '''<style type="text/css">

View File

@ -2,6 +2,6 @@
If you want to run SeleniumBase automation on local web pages while offline, that's possible if you copy the resource files here to a location where your local web server is able to access those files as long as you make the necessary updates to your local copy of SeleniumBase. You might not even need to use them depending on what you're doing.
**jquery-2.2.4.min.js** - This file is used by [base_case.py](https://github.com/mdmintz/SeleniumBase/blob/master/seleniumbase/fixtures/base_case.py) in activate_jquery(). The activate_jquery() method uses the version at [http://code.jquery.com/jquery-2.2.4.min.js](http://code.jquery.com/jquery-2.2.4.min.js). You only need this file if you're making jQuery calls in your automation (some base_case methods use jQuery).
**jquery-2.2.4.min.js** - This file is used by [base_case.py](https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/fixtures/base_case.py) in activate_jquery(). The activate_jquery() method uses the version at [http://code.jquery.com/jquery-2.2.4.min.js](http://code.jquery.com/jquery-2.2.4.min.js). You only need this file if you're making jQuery calls in your automation (some base_case methods use jQuery).
**favicon.ico** - This file is used by [style_sheet.py](https://github.com/mdmintz/SeleniumBase/blob/master/seleniumbase/core/style_sheet.py) for the favicon icon. All it does is make the report page a little more professional-looking. Currently, SeleniumBase uses the version at [https://raw.githubusercontent.com/mdmintz/SeleniumBase/master/seleniumbase/resources/favicon.ico](https://raw.githubusercontent.com/mdmintz/SeleniumBase/master/seleniumbase/resources/favicon.ico).
**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. All it does is make the report page a little more professional-looking. 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).