As a special use admin I would like to be confident that the system is performing as expected with a variety of applications.

[ericsorenson]

Instead of creating a unique object for each test case, only define the differences from a single object.

DRY up factories in server tests so that the system can better handle future changes to the permit applications.

Definition of Done

• [x] Code unit / e2e tested and comply with QWASP
• [x] No new security vulnerabilities
• [x] Flexion code review
• [x] Documentation / readme.md / CircleCI updated
• [x] Docker updated
• [x] Compare finished design with mockup
• [x] Usability tested

Tasks

• [x] review codebase and make a list of issues based on what we find
• [x] use models, views, controllers
• [x] reduce code duplication in server tests (Eric)
• [x] add app code to a src directory
• [x] Remove paths to binaries in package.json (Jesse)
• [x] Use request-promise (Jesse)
• [x] Break email templates into their own files (Seth)
• [x] Create routers for each path /auth, /permits/applications/special-uses/noncommercial, /permits/applications/special-uses/temp-outfitter (Jesse)

[ericsorenson]

• [x] Convert server comments to JSDoc format

[ericsorenson]

• [x] Create “special-use” directory for permit applications