409
edits
Auto-tools/Automation Development: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Automation Development (view source)
Revision as of 20:14, 15 August 2011
, 15 August 2011→Projects
| Line 18: | Line 18: | ||
== Projects == | == Projects == | ||
=== | {| cellspacing="1" cellpadding="1" border="1" summary="Projects that the team is actively engaged in" style="width: 1163px; height: 170px;" | ||
|+ Automation Projects | |||
|- | |||
| Mozmill Tests | |||
| [https://www.pivotaltracker.com/projects/289215 www.pivotaltracker.com/projects/289215] | |||
|- | |||
| Mozmill Automation | |||
| [https://www.pivotaltracker.com/projects/298905 www.pivotaltracker.com/projects/298905] | |||
|- | |||
| Mozmill Shared Modules | |||
| [https://www.pivotaltracker.com/projects/344657 www.pivotaltracker.com/projects/344657] | |||
|- | |||
| Open WebApps | |||
| [https://www.pivotaltracker.com/projects/350145 www.pivotaltracker.com/projects/350145] | |||
|} | |||
== | == Automated Test Frameworks == | ||
=== Selenium === | |||
=== | === Mozmill (Firefox) Test Framework === | ||
Basically you need to have python 2.6 running, on linux this is fairly simple, on mac it may require some work. | ==== About Mozmill ==== | ||
The eternal struggle on a mac is upgrading / installing linux based applications (fink, mac ports, have grown up to solve this problem) | |||
We like Homebrew, as the installs are non-destructive to the operating system, and localized to specific users. Without further a do, here are some instructions to get python 2.6 running. | Mozmill is a Software Automation Test Framework that has been designed to test the Firefox Browser. The test suites are written in a domain independent language (javascript), which then uses python in the backend to communicate with a local socket in the browser. There are several pieces required to run Mozmill tests. The simplest / easiest way to get up and writing / running mozmill tests is to install mozmill crowd. This extension allows you to run mozmill tests, and get familiar with writing test cases. After this initial you will be looking for something more complex, try installing Mozmill, and the corresponding test suite so you can run tests from the command line. *If you are able to get this up and running, Congratulations.. this is how tests are run in our continuous integration environment* | ||
==== How to Install ==== | |||
Install Mozmill Crowd and get familiar with running automated tests [https://addons.mozilla.org/firefox/addon/mozmill-crowd/ Mozmill Crowd] | |||
===== Advanced Install ===== | |||
Basically you need to have python 2.6 running, on linux this is fairly simple, on mac it may require some work. The eternal struggle on a mac is upgrading / installing linux based applications (fink, mac ports, have grown up to solve this problem) We like Homebrew, as the installs are non-destructive to the operating system, and localized to specific users. Without further a do, here are some instructions to get python 2.6 running. | |||
Mac: | Mac: | ||
Install Brew - [https://github.com/mxcl/homebrew Brew] | Install Brew - [https://github.com/mxcl/homebrew Brew] | ||
Update Python 2.6 Formula | |||
brew create git://gist.github.com/743034 | |||
name it python26 | |||
brew install python26 | |||
(Do not run brew install python, as it will install python 2.7.1) | |||
Linux: | |||
Linux: | |||
Install Pip with the following command sudo easy_install pip | Install Pip with the following command sudo easy_install pip | ||
sudo pip install mercurial | |||
sudo pip install virtualenvwrapper | |||
update your ~/.bash_profile | |||
export WORKON_HOME=$HOME/.virtualenvs | |||
export PIP_VIRTUALENV_BASE=$WORKON_HOME | |||
source /usr/local/bin/virtualenvwrapper.sh | |||
To create a new virtualenv you would do mkvirtualenv projecta –no-site-packages. “projecta” would be the name of the project you are using | |||
To create a new virtualenv you would do mkvirtualenv projecta –no-site-packages. “projecta” would be the name of the project you are using | |||
workon projecta | workon projecta | ||
install libraries needed in the relevant virtualenv so that you don’t pollute your environment. | |||
If something goes wrong you can delete the virtualenv without breaking your machine | |||
The basic install process is well documented on : [https://developer.mozilla.org/en/Mozmill Mozilla Developer] | |||
Install the Mozmill Tests Get the tests out of the repository - [https://developer.mozilla.org/en/Mozmill_Tests Mozmill Tests] | |||
=== Team Presence (Documentation) === | |||
=== Infrastructure Investigation === | |||
=== Selenium Grid 2 === | |||
=== Endurance Tests === | |||
===Endurance Tests=== | |||
== [[/QA/Automation_Services/New_Members|New Members]] == | == [[/QA/Automation_Services/New_Members|New Members]] == | ||
All new members to the team can find all the details about getting setup. Details on what accounts, what mailing lists, etc can be found on the [[/QA/Automation_Services/New_Members|Here]]. | All new members to the team can find all the details about getting setup. Details on what accounts, what mailing lists, etc can be found on the [[/QA/Automation_Services/New_Members|Here]]. | ||