How to set up a Headless Selenium Testing environment for CentOS 6.3.
Follow these steps to set up a CentOS 6.3 host to run headless Selenium tests with Firefox.
#!/bin/bash | |
# include config | |
# config example below: | |
# | |
# | |
# Example deploy_config.sh | |
# | |
# dev_env() { |
// License: MIT - https://opensource.org/licenses/MIT | |
// Author: Michele Locati <[email protected]> | |
// Source: https://gist.github.com/mlocati/7210513 | |
function perc2color(perc) { | |
var r, g, b = 0; | |
if(perc < 50) { | |
r = 255; | |
g = Math.round(5.1 * perc); | |
} | |
else { |
<IfModule mod_rewrite.c> | |
RewriteEngine On | |
### Call the correct front controller. This is dependent on an environment variable being set | |
### in the virtual host configuration. SetEnv seems not to work, so here's an example with SetEnvIfNoCase: | |
### <Directory /path/to/application/web> | |
### SetEnvIfNoCase REQUEST_URI .* SYMFONY_ENV=dev | |
### </Directory> | |
### This will force the following rules to call the dev front controller. |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
Our Virtual Machines are provisioned using Vagrant from a Linux base box to run using VirutalBox. If the Hard Disk space runs out and you cannot remove files to free-up space, you can resize the Hard Disk using some VirtualBox and Linux commands.
The following steps assume you've got a set-up like mine, where:
http://stackoverflow.com/questions/24380159/corebluetooth-and-wifi-interference
http://lists.apple.com/archives/bluetooth-dev/2013/Aug/msg00023.html
This is a well known issue, and it has a solution that is confirmed to work for the Mac side.
sudo defaults write /Library/Preferences/com.apple.airport.bt.plist bluetoothCoexMgmt Hybrid
After you run this script, the issue will go away and BT connections will remain stable.
<!-- | |
kindly provided by 'Knapster' | |
Ref: http://forum.kodi.tv/showthread.php?tid=139145&pid=1285390#pid1285390 | |
--> | |
<keymap> | |
<global> | |
<remote> | |
<channelplus>Notification(Keypress, channelplus, 1)</channelplus> | |
<channelminus>Notification(Keypress, channelminus, 1)</channelminus> |