Add TimePicker functional tests

[pottedmeat]

Type: feature

The following has been addressed in the PR:

• There is a related issue
• All code matches the style guide
• Unit or Functional tests are included in the PR

Description:

Wraps example tests with identifiers. Adds functional tests.

Resolves #162

[codecov]

Codecov Report

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

@@           Coverage Diff           @@
##           master     #368   +/-   ##
=======================================
  Coverage   97.79%   97.79%           
=======================================
  Files          25       25           
  Lines        1947     1947           
  Branches      494      494           
=======================================
  Hits         1904     1904           
  Misses         20       20           
  Partials       23       23

---

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 dc1076e...654460b. Read the comment docs.

[bitpshr]

One subjective question about skip messages. Also, it was a little hard to read the diff since the indentation changed on the example page, but the code changes and added test look solid.

[bitpshr]

Should we be more descriptive with the messages we pass when skipping tests? Do we know the level at which this test fails? Intern? Leadfoot? A driver? This is largely rhetorical, just trying to think of ways to make the skips less ugly.

This may be as good as we can do for now.

[pottedmeat]

When I'm able to easily find a reason in one of the other skips, I use it. Otherwise, trying to figure out the underlying cause is what had been holding up the tests, so I haven't been bothering anymore. I think the plan was to just skip with abandon then document and fix later.