blizzz

#!/bin/env bash

# requires nvm installed from AUR (i.e. only tested on Arch), and also jq
# run from the project directory like: runWithNodeAndNpm.sh make dev-setup
#  the package.json is taken from the current working directory

NODE_MAJOR_VERSION=$(cat package.json | jq .engines.node | grep -oE '[0-9]*' | head -1)
NPM_MAJOR_VERSION=$(cat package.json | jq .engines.npm | grep -oE '[0-9]*' | head -1)
source /usr/share/nvm/init-nvm.sh
nvm install ${NODE_MAJOR_VERSION} && \

svbergerem

import requests
urlFrom = 'https://cloud.domainfrom.tld'
authFrom = ('username', 'password')

urlTo = 'https://nextcloud.domainto.tld'
authTo = ('username', 'password')

headers={'OCS-APIRequest': 'true', 'Content-Type': 'application/json'}

klamping

Easy UI Regression Testing with Wraith and TravisCI

Introduction

In the past four years, I've learned the hard way about how painful it can be to try and update a codebase used by a large number of applications. Changes that seem innocent can break a specific use case that wasn't anticipated. Do enough manual regression testing and you will catch the bugs, but it's' costly and time consuming process. When things are costly and time consuming, they usually stop being done.

This is why I focus a lot of my efforts towards build process automation. Computers are fantastic about doing boring, repetitive work and never complaining. If you can get them to do the boring chores for you, you spend more time doing the fun, challenging work.

UI Regression testing is one of those spots where I'm looking for automation scripts to take over. Not only because playing "spot the difference" between your builds is boring, but also because [we're horrible at it](http://en.wikipedia.org/wiki/Chan

zziuni

# source : http://code.google.com/p/natvpn/source/browse/trunk/stun_server_list
# A list of available STUN server.

stun.l.google.com:19302
stun1.l.google.com:19302
stun2.l.google.com:19302
stun3.l.google.com:19302
stun4.l.google.com:19302
stun01.sipphone.com
stun.ekiga.net