Started implementing the Test and TestCase classes
Add TestParser

The TestParser class knows how to parse the output produced by the
ooniprobe tests. The idea is to seperate the parsing logic from the Test
class.
Add parsable output to tests

Ihis makes it easy for TestParser to keep track of the test results,
without having to parse the .yamloo reports.
Add test subclasses

One small subclass per test, to simplify the process of creating and running
tests.
Rewrite the TestCase class
Introduce PingTest subclass

First, rough draft of this Test subclass. It overrides the standard
parseResults method.
Change subclasses to use super

Test subclasses now use super instead of calling Test
Rewrite TestCase class

The TestCase class is now a subclass of list. A generator function now
takes care of randomizing the order in which the tests are run.
Add parsable output
Add DNSTest subclass
Add parsable output
Add Traceroute subclass
Add parsable output

This will most likely be changed, once I can think of a better approach.
Rewrite module to use the new Test-classes

The lower level details of specifying and running ooniprobe tests are
hidden by a layer of abstraction. Tests are now run by creating an
instance of the corresponding Test subclass, and invoking it's run
method.
Merge branch 'dev'

Conflicts:
	analyser.py