[meta] Implement continuous integration for Panopoly

Yeah, it's going to do pretty much the same things but instead of Selenium, it will be some Simpletest and Behat tests (which may at some point use Selenium underneath). I'm going to try and focus on Behat (via the Drupal extension) when possible, so that the tests are human readable.

@Andrew_Mallis: That is a great idea!

@populist mentioned the Canadian Government project at BADCamp, but I still haven't a chance to look into it. I just Google'd up a reference to it (Web Experience Toolkit) but I'm not sure still what exactly it is or where it touches Drupal/Panopoly:

http://wet-boew.github.io/wet-boew/index-en.html

But I'll dig in, when I find a chance. :-)

@isolesen: I haven't created any "real" Behat tests yet, I've been mostly experimenting with connecting all the peices together. However, I'm giving a presentation on Behat at my local Drupal meetup on Thusday (http://www.meetup.com/Drupal414/events/146920562/) and I'm thinking about trying to organize a Panopoly Behat test sprint with the same group in early December, but I have to run the idea by them first and see if there is enough interest. :-)

It would amazing if you would contribute some tests! Sometime next week, I'll start committing the infrastructure to run them to Panopoly and we can start creating some real tests. :-)

Just a note for myself or anyone who was curious about the Canadian government distribution...

I finally found the Panopoly-based distribution created by the Canadian government entirely by accident (they were posting about an issue with Drupal.org in the issue queue) and I wanted to post the link so I wouldn't lose it:

https://drupal.org/project/wetkit

The first step to this is setting up the boilerplate for Behat tests in Panopoly: #2145447: Add initial Behat tests to Panopoly

@lsolesen: Thanks for the links! I've been working on an approach for this in an other project, but I take a look at those articles before I commit anything to see if there's anything worth borrowing from them. :-)

To everyone: Sorry, I haven't committed this yet! I meant to last week but things got busy. :-) I'll try and do it this week for sure.

I made this into "meta issue" - we can create sub-issues for the individual tasks as they come up.

The next step is compiling a list of Panopoly's features that we want to make sure we don't break! I've added a new issue which links to Google Doc we can collaborate on: #2146747: Make a list of "core features" to Panopoly that we don't want to break

Added a seperate issue for the Jenkins part of this: #2146755: Setup Jenkins to build Panopoly, install and run the tests for each commit

(Removed note about myself offering servers for this since we might be able to do it with Pantheon and servers from SystemSeed that already have Jenkins/Selenium going - we'll work that out in this issue: #2146755: Setup Jenkins to build Panopoly, install and run the tests for each commit)

Adding issue for the Behat tests of Panopoly widgets.

Added the travis-ci issue.

Implemented! I'll let the remaining issues speak for themselves.