implementing a test proxy

can be used as a contextmanager to communicate results about tests run
to teamcity
using teamcity test proxy for integration tests
Merge pull request #62 from pybuilder/feature/teamcity-messages

Feature/teamcity messages
refactor : extract slice
allow reporting unittests to ci server

This required extending the builtin test runner so that its result is
aware of the tests that were run and which of those failed.
using correct proxy mock
need a travis run on 2.6 with -X
fix issue on python2.6

it is too difficult to override the constructor while maintaining 2.6
compatibility.
It seems TestResult on 2.6 does not want a stream (__init__ takes
exactly one argument, which can only be self). Worked around it by
initializing the result when the first test runs.
Revert "fix issue on python2.6"

This reverts commit 5ea41d222aa86602672a1f7afac1e1ec55f1ed54.
need to do this for 2.6 - 2.7+ compatibility
let's try this again
this should finally fix it

please?
Merge pull request #63 from pybuilder/feature/teamcity-messages

CI server messages for unittest plugin
v0.10.7
avoid confusing the ci server when parallel

the service messages were sent in parallel, thus causing the ci server
to be confused with the nesting of the tests. The service messages are
now sent sequentially after finishing to run the tests.
v0.10.8
disable pacman rotation which is annoying
v0.10.9
strip single quotes for service messages
disable service messages while running coverage

fixes #64