QA/BrowserID/BrowserID Basic Install - Revision history

Darkspirit: Replaced ftp and http with https where it didn't make things worse.

2018-08-12T01:22:09Z

Replaced ftp and http with https where it didn't make things worse.

Jbonacci: /* Installing gmp/gmp-devel on Linux */

2013-11-01T02:08:34Z

Installing gmp/gmp-devel on Linux

← Older revision		Revision as of 02:08, 1 November 2013
Line 110:		Line 110:

	== Installing gmp/gmp-devel on Linux ==		== Installing gmp/gmp-devel on Linux ==
	* NOTE: It should be possible to install the latest libgmp package, which can be found here: ~~ftp~~://~~ftp.~~gmplib.org/~~pub/~~		* NOTE: It should be possible to install the latest libgmp package, which can be found here: http://gmplib.org/#DOWNLOAD
	* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Linux, also. The recommendation was to use an older gmp package with the very latest node/npm bundle.		* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Linux, also. The recommendation was to use an older gmp package with the very latest node/npm bundle.

Jbonacci: /* Installing gmp on Mac */

2013-04-26T19:42:55Z

Installing gmp on Mac

← Older revision		Revision as of 19:42, 26 April 2013
Line 86:		Line 86:
	== Installing gmp on Mac ==		== Installing gmp on Mac ==
	* NOTE: It should be possible to install the latest libgmp package, which can be found here: ftp://ftp.gmplib.org/pub/ (Using a node Mac package is NOT recommended.)		* NOTE: It should be possible to install the latest libgmp package, which can be found here: ftp://ftp.gmplib.org/pub/ (Using a node Mac package is NOT recommended.)
	* (OLD INFORMATION) There ~~are~~ compatibility issues with using gmp and npm on Mac. The recommendation was to use an older gmp package with the very latest node/npm bundle.		* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Mac. The recommendation was to use an older gmp package with the very latest node/npm bundle.

	* Go through all four installation steps to ensure a decent gmp install		* Go through all four installation steps to ensure a decent gmp install

Jbonacci: /* Installing gmp/gmp-devel on Linux */

2013-04-26T19:41:57Z

Installing gmp/gmp-devel on Linux

← Older revision		Revision as of 19:41, 26 April 2013
Line 110:		Line 110:

	== Installing gmp/gmp-devel on Linux ==		== Installing gmp/gmp-devel on Linux ==
	NOTE: It should be possible to install the latest libgmp package, which can be found here: ftp://ftp.gmplib.org/pub/		* NOTE: It should be possible to install the latest libgmp package, which can be found here: ftp://ftp.gmplib.org/pub/
	* There ~~are~~ compatibility issues with using gmp and npm on Linux, also.		* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Linux, also. The recommendation was to use an older gmp package with the very latest node/npm bundle.
	* The recommendation is to use an older gmp package with the very latest node/npm bundle ~~(v0.6.5).~~
	* This combination for example, has presented some problems:
	** node v.0.6.3 install that includes npm 1.1.~~0-alpha-2~~

	* Install an older version (stable version) of gmp-devel, for example: gmp-4.3.1-7
	* Example site:
	~~ftp://ftp.gnu.org/gnu/gmp/gmp-4.3.1.tar.gz~~
	* Go through all four installation steps to ensure a decent gmp install		* Go through all four installation steps to ensure a decent gmp install
	./configure		./configure

Jbonacci: /* Installing gmp on Mac */

2013-04-26T19:40:29Z

Installing gmp on Mac

← Older revision		Revision as of 19:40, 26 April 2013
Line 85:		Line 85:

	== Installing gmp on Mac ==		== Installing gmp on Mac ==
	* NOTE: It should be possible to install the latest libgmp package, which can be found here: ftp://ftp.gmplib.org/pub/		* NOTE: It should be possible to install the latest libgmp package, which can be found here: ftp://ftp.gmplib.org/pub/ (Using a node Mac package is NOT recommended.)
	* There are compatibility issues with using gmp and npm on Mac.		* (OLD INFORMATION) There are compatibility issues with using gmp and npm on Mac. The recommendation was to use an older gmp package with the very latest node/npm bundle.
	* The recommendation is to use an older gmp package with the very latest node/npm bundle ~~(v0.6.5).~~
	* This combination for example, has presented some problems:
	** node v.0.6.3 install that includes npm 1.1.0-alpha-2
	* Using a node Mac package is NOT recommended.

	* Install an older version (stable version) of gmp-devel, for example: gmp-4.3.1.tar.gz
	** (do NOT use gmp-5.0.2)
	* Example site:
	~~ftp://ftp.gnu.org/gnu/gmp/gmp-4.3.1.tar~~.gz

	* Go through all four installation steps to ensure a decent gmp install		* Go through all four installation steps to ensure a decent gmp install

Jbonacci: /* Installing gmp/gmp-devel on Linux */

2013-04-10T21:04:48Z

Installing gmp/gmp-devel on Linux

← Older revision		Revision as of 21:04, 10 April 2013
Line 119:		Line 119:

	== Installing gmp/gmp-devel on Linux ==		== Installing gmp/gmp-devel on Linux ==
			NOTE: It should be possible to install the latest libgmp package, which can be found here: ftp://ftp.gmplib.org/pub/
	* There are compatibility issues with using gmp and npm on Linux, also.		* There are compatibility issues with using gmp and npm on Linux, also.
	* The recommendation is to use an older gmp package with the very latest node/npm bundle (v0.6.5).		* The recommendation is to use an older gmp package with the very latest node/npm bundle (v0.6.5).

Jbonacci: /* Required Packages */

2013-04-08T17:37:18Z

Required Packages

← Older revision		Revision as of 17:37, 8 April 2013
Line 26:		Line 26:
	* mysql for testing		* mysql for testing

	~~Note~~: Mac OS should already have the first four, so you should only need to install node, npm, git, etc. before installing Persona/BrowserID.		* Mac Notes:
			** Mac OS should already have the first four, so you should only need to install node, npm, git, etc. before installing Persona/BrowserID.
			** With the latest versions of Mac OS and XCode, the command line tools are not downloaded/installed by default. You must explicitly download them through Xcode > Preferences > Downloads.

	~~Note 2~~: With the latest CentOS 6 used for the Linux portion of this document, the following packages were already installed: gcc, g++, make, openssl, git		* Linux Notes:
	So, if your version/flavor of Linux does not have these installed by default, proceed with installations typical for your Linux.		** With the latest CentOS 6 used for the Linux portion of this document, the following packages were already installed: gcc, g++, make, openssl, git
			** So, if your version/flavor of Linux does not have these installed by default, proceed with installations typical for your Linux.

	== Installing Node.js and NPM ==		== Installing Node.js and NPM ==

Jbonacci: /* Running the Automation Tests */

2013-04-04T17:59:08Z

Running the Automation Tests

Jbonacci: /* Running the Automation Tests */

2013-04-04T17:57:41Z

Running the Automation Tests

← Older revision		Revision as of 17:57, 4 April 2013
Line 427:		Line 427:
	** In one terminal, run the server		** In one terminal, run the server
	java -jar selenium-server-standalone-2.31.0.jar		java -jar selenium-server-standalone-2.31.0.jar
			** An example using the chrome driver support
			exec java -Dwebdriver.chrome.driver=/<PATH TO DRIVER>/chromedriver -jar /<PATH TO JAR>/selenium-server-standalone-2.301.0.jar
	** Open another terminal to run the automated tests		** Open another terminal to run the automated tests
	cd browserid/automation-tests/scripts		cd browserid/automation-tests/scripts
Line 445:		Line 447:
	See the following site for more information on downloading drivers to support other browsers:		See the following site for more information on downloading drivers to support other browsers:
	http://docs.seleniumhq.org/download/		http://docs.seleniumhq.org/download/
			NOTE: As of Selenium webdriver 2.31, Safari and Opera should have built-in support. The webdrivers for IE and Google Chrome are still required.

	./scripts/run-all.js --list-tests		./scripts/run-all.js --list-tests
Line 452:		Line 455:
	will allow you to change which environment you test: dev, stage, prod (the default is dev)		will allow you to change which environment you test: dev, stage, prod (the default is dev)

	* Examples		* Examples against local host
	One test, one browser, locally:		One test, one browser, locally:
	./scripts/run-all.js --local --platform=firefox --tests change-password-test		./scripts/run-all.js --local --platform=firefox --tests change-password-test
Line 460:		Line 463:
	All tests, one browser, locally, against stage:		All tests, one browser, locally, against stage:
	./scripts/run-all.js --local --env stage --platform=firefox-beta		./scripts/run-all.js --local --env stage --platform=firefox-beta

			* Examples against sauce labs
			One test, one browser:
			./scripts/run-all.js --platform=osx_firefox_19 --tests change-password-test
			./scripts/run-all.js --platform=linux_opera_12 --tests change-password-test
			All tests, one browser:
			./scripts/run-all.js --platform=win7_chrome
			All tests, all browsers:
			./scripts/run-all.js --platform=all

	* Notes:		* Notes:
	** If you have multiple versions of Firefox installed on your system, you can tweak the local-platform.js file and add each version as an entry (see the comment in the file for an example)		** If you have multiple versions of Firefox installed on your system, you can tweak the local-platform.js file and add each version as an entry (see the comment in the file for an example)
	** The tests will create a significant amount of information that can be seen in the STDOUT/STDERR of the stand-alone server. Therefore, it might be helpful to redirect both to a log file.		** The current list of supported platforms for Sauce labs can always be found here: browserid/automation-tests/config/sauce-platforms.js file
			** The local host tests will create a significant amount of information that can be seen in the STDOUT/STDERR of the stand-alone server. Therefore, it might be helpful to redirect both to a log file.
			** Sauce Labs failures will generate an error link similar to the following: https://saucelabs.com/jobs/<Some Test ID>. Clicking on the link will give some detail to the failure(s) generated from the preceding automation test run.
			** The --output xunit flag can also be used to generate a live link for the sauce labs run

	* For more information, see the following links:		* For more information, see the following links:

Jbonacci: /* Running the Automation Tests */

2013-04-02T19:11:13Z

Running the Automation Tests

← Older revision		Revision as of 19:11, 2 April 2013
Line 429:		Line 429:
	** Open another terminal to run the automated tests		** Open another terminal to run the automated tests
	cd browserid/automation-tests/scripts		cd browserid/automation-tests/scripts
	./run-all.js --help		./scripts/run-all.js --help
	will give you the current list of all automation commands		will give you the current list of all automation commands
	~~./run-all.js --list-platforms~~
	~~will give you the current list of all supported platforms~~
	~~(this list can be manually updated to match the supported OS/browser combinations you want to test)~~

	Edit the following file to change/update this list:		./scripts/run-all.js --local --list-platforms
	browserid/automation-tests/config/~~sauce~~-~~platforms~~.js		will give you the current list of all supported platforms on the local host
			(this is a generic list that assumes all/any browser(s) can be run on the local host)
			Edit the following file to change/update this list, including adding support for all FireFox channels:
			browserid/automation-tests/config/local-platform.js

			./scripts/run-all.js --list-platforms
			will give you the current list of all supported platforms for running against sauce labs
			(this list should not be updated)

	By default, the automation tests only run against the FireFox browser (any current version on any current OS) without the use of a special browser driver.		By default, the automation tests only run against the FireFox browser (any current version on any current OS) without the use of a special browser driver.
	See the following site for more information on downloading drivers to support other browsers:		See the following site for more information on downloading drivers to support other browsers:
	http://docs.seleniumhq.org/download/		http://docs.seleniumhq.org/download/

	./run-all.js --list-tests		./scripts/run-all.js --list-tests
	will give you the current list of all automated tests than can be run singly or together		will give you the current list of all automated tests than can be run singly or together

	./run-all.js --env <other options here>		./scripts/run-all.js --env <other options here>
	will allow you to change which environment you test: dev, stage, prod (the default is dev)		will allow you to change which environment you test: dev, stage, prod (the default is dev)

	* Examples		* Examples
	One test, one browser, locally:		One test, one browser, locally:
	./run-all.js --local --platform=~~osx_firefox_19~~ --tests change-password-test		./scripts/run-all.js --local --platform=firefox --tests change-password-test
	./~~run-all.js --local --platform=linux_firefox_19 --tests change-password-test~~		./scripts/run-all.js --local --platform=linux --tests change-password-test
	./run-all.js --local --platform=~~linux_firefox_19~~ --tests change-password-test
	All tests, one browser, locally:		All tests, one browser, locally:
	./run-all.js --local --platform=~~osx_firefox_19~~		./scripts/run-all.js --local --platform=firefox-aurora
	All tests, one browser, locally, against stage:		All tests, one browser, locally, against stage:
	./run-all.js --local --env stage --platform=~~osx_firefox_19~~		./scripts/run-all.js --local --env stage --platform=firefox-beta

	* Notes:		* Notes:
	** If you have multiple versions of Firefox installed on your system, you can tweak the ~~sauce~~-~~platforms~~.js file and ~~redirect firefox.app to point to~~ the ~~version to be tested.~~		** If you have multiple versions of Firefox installed on your system, you can tweak the local-platform.js file and add each version as an entry (see the comment in the file for an example)
	** The tests will create a significant amount of information that can be seen in the STDOUT/STDERR of the stand-alone server. Therefore, it might be helpful to redirect both to a log file.		** The tests will create a significant amount of information that can be seen in the STDOUT/STDERR of the stand-alone server. Therefore, it might be helpful to redirect both to a log file.

← Older revision		Revision as of 01:22, 12 August 2018
Line 39:		Line 39:

	* Node can be installed from here:		* Node can be installed from here:
	~~http~~://nodejs.org/dist/		https://nodejs.org/dist/
	Example: ~~http~~://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz		Example: https://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz
	unzip/untar the files		unzip/untar the files
	Follow the README.md file to build/install node v0.6.5 (as root):		Follow the README.md file to build/install node v0.6.5 (as root):
Line 58:		Line 58:
	== Installing Git on Mac ==		== Installing Git on Mac ==
	* The Mac Git application is available here		* The Mac Git application is available here
	~~http~~://code.google.com/p/git-osx-installer/downloads/list		https://code.google.com/p/git-osx-installer/downloads/list

	* Select the latest for your version of Mac OS		* Select the latest for your version of Mac OS
Line 85:		Line 85:

	== Installing gmp on Mac ==		== Installing gmp on Mac ==
	* NOTE: It should be possible to install the latest libgmp package, which can be found here: ~~ftp~~://~~ftp.~~gmplib.org/~~pub~~/ (Using a node Mac package is NOT recommended.)		* NOTE: It should be possible to install the latest libgmp package, which can be found here: https://gmplib.org/download/ (Using a node Mac package is NOT recommended.)
	* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Mac. The recommendation was to use an older gmp package with the very latest node/npm bundle.		* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Mac. The recommendation was to use an older gmp package with the very latest node/npm bundle.

Line 97:		Line 97:
	== Installing phantomjs on Mac ==		== Installing phantomjs on Mac ==
	Grab the latest phantomjs package from here:		Grab the latest phantomjs package from here:
	~~http~~://code.google.com/p/phantomjs/downloads/list		https://code.google.com/p/phantomjs/downloads/list
	Example:		Example:
	~~http~~://phantomjs.googlecode.com/files/phantomjs-1.5.0-macosx-static.zip		https://phantomjs.googlecode.com/files/phantomjs-1.5.0-macosx-static.zip

	Unzip the file		Unzip the file
Line 110:		Line 110:

	== Installing gmp/gmp-devel on Linux ==		== Installing gmp/gmp-devel on Linux ==
	* NOTE: It should be possible to install the latest libgmp package, which can be found here: ~~http~~://gmplib.org/#DOWNLOAD		* NOTE: It should be possible to install the latest libgmp package, which can be found here: https://gmplib.org/#DOWNLOAD
	* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Linux, also. The recommendation was to use an older gmp package with the very latest node/npm bundle.		* (OLD INFORMATION) There were compatibility issues with using gmp and npm on Linux, also. The recommendation was to use an older gmp package with the very latest node/npm bundle.

Line 129:		Line 129:
	* There is a binary package now for phantomjs that can be downloaded and used on Linux, including RHEL 6, CentOS 6, and Ubuntu 11		* There is a binary package now for phantomjs that can be downloaded and used on Linux, including RHEL 6, CentOS 6, and Ubuntu 11
	* See the following sites for more information:		* See the following sites for more information:
	** ~~http~~://code.google.com/p/phantomjs/wiki/Installation		** https://code.google.com/p/phantomjs/wiki/Installation
	** ~~http~~://code.google.com/p/phantomjs/downloads/list		** https://code.google.com/p/phantomjs/downloads/list

	Install the latest version of phantomjs		Install the latest version of phantomjs
	Example:		Example:
	wget ~~http~~://phantomjs.googlecode.com/files/phantomjs-1.5.0-linux-x86_64-dynamic.tar.gz		wget https://phantomjs.googlecode.com/files/phantomjs-1.5.0-linux-x86_64-dynamic.tar.gz

	gunzip and tar xvf the file		gunzip and tar xvf the file
Line 178:		Line 178:
	** RHEL/Fedora/CentOS: sudo yum -y install svn gettext		** RHEL/Fedora/CentOS: sudo yum -y install svn gettext
	** Mac: use Ports, Homebrew, or install from here:		** Mac: use Ports, Homebrew, or install from here:
	~~ftp~~://ftp.gnu.org/pub/gnu/gettext/		https://ftp.gnu.org/pub/gnu/gettext/
	Make sure that the gettext/msgfmt bin directory is added to your path		Make sure that the gettext/msgfmt bin directory is added to your path
	* If XCode is installed, svn should already be available		* If XCode is installed, svn should already be available
Line 412:		Line 412:
	* Basic instructions		* Basic instructions
	** Download the standalone Selenium server from the following site		** Download the standalone Selenium server from the following site
	~~http~~://selenium.googlecode.com		https://selenium.googlecode.com
	Example: curl -O ~~http~~://selenium.googlecode.com/files/selenium-server-standalone-2.31.0.jar		Example: curl -O https://selenium.googlecode.com/files/selenium-server-standalone-2.31.0.jar
	** In one terminal, run the server		** In one terminal, run the server
	java -jar selenium-server-standalone-2.31.0.jar		java -jar selenium-server-standalone-2.31.0.jar
Line 437:		Line 437:
	on any current OS) without the use of a special browser driver.		on any current OS) without the use of a special browser driver.
	See the following site for more information on downloading drivers to support other browsers:		See the following site for more information on downloading drivers to support other browsers:
	~~http~~://docs.seleniumhq.org/download/		https://docs.seleniumhq.org/download/
	NOTE: As of Selenium webdriver 2.31, Safari and Opera should have built-in support.		NOTE: As of Selenium webdriver 2.31, Safari and Opera should have built-in support.
	The webdrivers for IE and Google Chrome are still required.		The webdrivers for IE and Google Chrome are still required.
Line 475:		Line 475:
	** Automation test information: https://github.com/mozilla/browserid/tree/dev/automation-tests		** Automation test information: https://github.com/mozilla/browserid/tree/dev/automation-tests
	** Automation tests: https://github.com/mozilla/browserid/tree/dev/automation-tests/tests		** Automation tests: https://github.com/mozilla/browserid/tree/dev/automation-tests/tests
	** Selenium components and information on browser drivers: ~~http~~://docs.seleniumhq.org/download/		** Selenium components and information on browser drivers: https://docs.seleniumhq.org/download/
	** Documentation: https://github.com/mozilla/browserid/wiki/Automated-Browser-Testing		** Documentation: https://github.com/mozilla/browserid/wiki/Automated-Browser-Testing
	** Persona Test Plan: https://wiki.mozilla.org/QA/BrowserID/TestPlan		** Persona Test Plan: https://wiki.mozilla.org/QA/BrowserID/TestPlan

← Older revision		Revision as of 17:59, 4 April 2013
Line 428:		Line 428:
	java -jar selenium-server-standalone-2.31.0.jar		java -jar selenium-server-standalone-2.31.0.jar
	** An example using the chrome driver support		** An example using the chrome driver support
	exec java -Dwebdriver.chrome.driver=/<PATH TO DRIVER>/chromedriver -jar /<PATH TO JAR>/selenium-server-standalone-2.301.0.jar		exec java -Dwebdriver.chrome.driver=/<PATH TO DRIVER>/chromedriver
			-jar /<PATH TO JAR>/selenium-server-standalone-2.301.0.jar
	** Open another terminal to run the automated tests		** Open another terminal to run the automated tests
	cd browserid/automation-tests/scripts		cd browserid/automation-tests/scripts
Line 444:		Line 445:
	(this list should not be updated)		(this list should not be updated)

	By default, the automation tests only run against the FireFox browser (any current version on any current OS) without the use of a special browser driver.		By default, the automation tests only run against the FireFox browser (any current version
			on any current OS) without the use of a special browser driver.
	See the following site for more information on downloading drivers to support other browsers:		See the following site for more information on downloading drivers to support other browsers:
	http://docs.seleniumhq.org/download/		http://docs.seleniumhq.org/download/
	NOTE: As of Selenium webdriver 2.31, Safari and Opera should have built-in support. The webdrivers for IE and Google Chrome are still required.		NOTE: As of Selenium webdriver 2.31, Safari and Opera should have built-in support.
			The webdrivers for IE and Google Chrome are still required.

	./scripts/run-all.js --list-tests		./scripts/run-all.js --list-tests