Fix build

Author: rogerdahl

README.md

@@ -110,7 +110,7 @@ When unit tests are being run as part of CI or as a normal guard against regress
 
 The normal procedure for writing a sample based unit test is to just write the test as if the sample already exists, then running the test with `--sample-ask` and viewing and approving the resulting sample, which is then automatically written to a file. The sample file name is displayed, making it easy to find the file in order to add it to tracking so that it can be committed along with the test module.
 
-When working on large changes that cause many samples to become outdated, reviewing and approving samples can be deferred until the new code approaches stability. This is done by running the tests with `--sample-write`, which automatically writes or updates samples to match the current results. Then, view and approve the tests with `--sample-review` before committing.  
+When working on large changes that cause many samples to become outdated, reviewing and approving samples can be deferred until the new code approaches stability. This is done by running the tests with `--sample-update`, which automatically writes or updates samples to match the current results. Then, view and approve the tests with `--sample-review` before committing.  
 
 Typically, it is not desirable to track generated files in Git. However, although the sample files are generated, they are an integral part of the units tests, and should be tracked just like the unit tests themselves.
 

conftest.py

@@ -81,12 +81,12 @@ def pytest_addoption(parser):
     help='Prompt to update or write new test sample files on failures'
   )
   parser.addoption(
-    '--sample-write', action='store_true',
+    '--sample-update', action='store_true',
     help='Automatically update or write sample files on failures'
   )
   parser.addoption(
     '--sample-review', action='store_true',
-    help='Review samples (use after --sample-write)'
+    help='Review samples (use after --sample-update)'
   )
   parser.addoption(
     '--sample-tidy', action='store_true',

gmn/src/d1_gmn/tests/test_templates.py

@@ -23,6 +23,7 @@
 
 from __future__ import absolute_import
 
+import freezegun
 import responses
 
 import d1_gmn.tests.gmn_test_case
@@ -37,6 +38,7 @@
 
 
 @d1_test.d1_test_case.reproducible_random_decorator('TestTemplates')
+@freezegun.freeze_time('1961-11-22')
 class TestTemplates(d1_gmn.tests.gmn_test_case.GMNTestCase):
   @responses.activate
   def test_1000(self):

test_utilities/src/d1_test/sample.py

@@ -101,7 +101,7 @@ def assert_equals(
     format(filename, '-' * 10, diff_str)
   )
 
-  if pytest.config.getoption('--sample-write'):
+  if pytest.config.getoption('--sample-update'):
     save(got_str, filename)
     return
 

test_utilities/src/d1_test/test_docs/test_templates_home_html_doc.sample

@@ -87,7 +87,7 @@
       </tr>
       <tr>
         <td>Operations, last hour:</td>
-        <td>632</td>
+        <td>3,236</td>
       </tr>
       <tr>
         <td>Subjects:</td>
@@ -99,7 +99,7 @@
       </tr>
       <tr>
         <td>Server time:</td>
-        <td>Dec. 7, 2017, 4:19 p.m.</td>
+        <td>Nov. 22, 1961, midnight</td>
       </tr>
       <tr>
         <td>Storage used / remaining:</td>