chore(build): enable AoT

README.md

@@ -17,11 +17,11 @@ Code.gov is an open source project, so we invite your contributions, be it in th
 
 The development of code.gov is guided by the requirements set forth in [Section 7.2 (Code Inventories and Discovery)](https://sourcecode.cio.gov/Implementation/#code-inventories-and-discovery), [Section 7.3 (Code.gov)](https://sourcecode.cio.gov/Implementation/#codegov), and  [Section 7.6 (Agency Policy)](https://sourcecode.cio.gov/Implementation/#agency-policy) of the Federal Source Code Policy. Namely:
 
-    * "Within 90 days of the publication date of this policy, the Administration will launch https://www.code.gov, an online collection of tools, best practices, and schemas to help agencies implement this policy.";
-
-    * "Within 90 days of the publication date of this policy, each agency’s CIO—in consultation with the agency’s CAO—shall develop an agency-wide policy that addresses the requirements of this [document.]";  and
-
-    * "Within 120 days of the publication date of this policy, each agency must update—and thereafter keep up to date—its inventory of agency information resources to include an enterprise code inventory that lists custom-developed code for or by the agency after the publication of this policy."
+> * "Within 90 days of the publication date of this policy, the Administration will launch https://www.code.gov, an online collection of tools, best practices, and schemas to help agencies implement this policy.";
+>
+> * "Within 90 days of the publication date of this policy, each agency’s CIO—in consultation with the agency’s CAO—shall develop an agency-wide policy that addresses the requirements of this [document.]";  and
+>
+> * "Within 120 days of the publication date of this policy, each agency must update—and thereafter keep up to date—its inventory of agency information resources to include an enterprise code inventory that lists custom-developed code for or by the agency after the publication of this policy."
 
 Over the next few weeks, we will begin the *discovery sprint* for code.gov. During that time, we will conduct user interviews and engage this community in discussions that will inform the user experience for code.gov.
 
@@ -53,9 +53,21 @@ You can then run the server using `npm start`.
 By default, the development server will listen on <http://localhost:2700/>. You can change the default port by setting the `PORT` environment variable before starting the server (for example, `PORT=3000 npm start`).
 
 ## Testing
-This app uses Karma + Jasmine to handle testing. Run `npm test` to execute
+### Unit tests
+This app uses Karma + Jasmine to handle unit testing. Run `npm test` to execute
 tests. To add tests, simply create a file with `.spec.ts` as the extension and
 your tests will be included.
+### End-to-end tests
+End-to-end testing is done with Protractor and tests are written in Jasmine with the Protractor API
+used to locate elements and interact with the page.
+Running e2e tests requires the following steps:
+* Run `npm start` to start the application.
+* In a second terminal window, run `npm run webdriver:start` to start the selenium server used to run the tests.
+This step must be done before the next step.
+* In a third terminal window, run `npm run e2e`. The Chrome browser will be launched to
+run the tests and the test results will be displayed in this window.
+
+End-to-end tests need to be written in a file with an `.e2e.ts` extension.
 
 ## Deployment
 This app uses the `github-deploy` package for handling deployment. To configure