test: add smoke test for app sample

[JustinBeckwith]

There are currently no tests available for the samples. This cleans up a few things and adds a simple test. In addition removes @google-cloud/repo-tools and it's configuration as it wasn't being used.

[codecov]

Codecov Report

Merging #663 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #663   +/-   ##
======================================
  Coverage    88.9%   88.9%           
======================================
  Files          15      15           
  Lines         946     946           
  Branches       83      83           
======================================
  Hits          841     841           
  Misses         87      87           
  Partials       18      18

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b079085...0855363. Read the comment docs.

[bcoe]

this LGTM, and is better than nothing -- is there any way for us to detect that logs have been emitted to stackdriver?

[bcoe]

just a difference in style, I'd usually just pick a port and use it consistently for integration tests (I'd rather know that I'm not shutting down cleanly via failure to bind).

[JustinBeckwith]

In retrospect, that's probably going to be fine too. Initially I was worried about the same tests running in parallel, but it doesn't matter since they're almost always in docker containers that should abstract it from us.

[JustinBeckwith]

@DominicKramer from @bcoe question:

is there any way for us to detect that logs have been emitted to stackdriver?

[ofrobots]

is there any way for us to detect that logs have been emitted to stackdriver?

@bcoe can you elaborate.. as far as I can see there are no logs being emitted to a Stackdriver log stream. I only see console.logs.

[bcoe]

@ofrobots I think I'm misunderstanding the default behavior of require('@google-cloud/debug-agent').start();, mainly I was wondering if there was a way in test to assert that it had instrumented the logging in the application -- not a blocker for me.