Skip to content

Instantly share code, notes, and snippets.

View chumster's full-sized avatar

Stephen Chumley chumster

View GitHub Profile
@chumster
chumster / gist:5093671
Created March 5, 2013 19:55
SoapUI - Groovy Cheatsheet
// Generate Random GUID
def guidVal = "${java.util.UUID.randomUUID()}"
// Get current date and time in milliseconds
now = Calendar.instance
log.info 'now is a ' + now.class.name
date = now.time
log.info 'date is a ' + date.class.name + ' with value ' + date
millis = date.time
log.info 'millis is a ' + millis.class.name + ' with value ' + millis
@chumster
chumster / gist:6142516
Created August 2, 2013 19:09
selenium-server-standalone on ubuntu
apt-get update
apt-get install sudo
Fonts and Headless X11 magic is here
sudo apt-get -y install xvfb\
x11-xkb-utils\
xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic\
xserver-xorg-core
@chumster
chumster / gist:8946300
Created February 11, 2014 23:09
Google's approach to testing
Google’s approach is more than a little counterintuitive: We have fewer dedicated testers in our entire company than many of our competitors have on a single product team. Google Test is no million-man army. We are small and elite Special Forces that have to depend on superior tactics and advanced weaponry to stand a fighting chance at success. As with military Special Forces, it is this scarcity of resources that forms the base of our secret sauce. The absence of plenty forces us to get good at prioritizing, or as Larry Page puts it: “Scarcity brings clarity.” From features to test techniques, we’ve learned to create high impact, low-drag activities in our pursuit of quality. Scarcity also makes testing resources highly valued, and thus, well regarded, keeping smart people actively and energetically involved in the discipline. The first piece of advice I give people when they ask for the keys to our success: Don’t hire too many testers.
How does Google get by with such small ranks of test folks? If I had to