While the specific setup for each TTS project varies widely, there are certain elements that should be present in all source code repositories. This document aims to detail those elements and suggest corresponding tools and resources.
Source code management
TTS projects use GitHub for source code management, with their repositories under a government-owned organization.
- GitHub Standard
Below is an aspirational list of configuration and files for a source code repository. Not all of these elements will apply to every project (e.g. visual regression tests don’t make sense for an API).
- Community profile
.gitignore(though also consider a global config)
- Programming language version specifications (e.g.,
- Dependency version descriptions (e.g.,
package.json) — don’t forget to pin them
- Build scripts
- Unit test setup for each programming language
- Linter setup (e.g.,
- cloud.gov/Cloud Foundry
- Deploy scripts
- Continuous Integration/Continuous Deployment
- Code coverage metrics
- Static analysis for code quality
- Static security analysis
- Accessibility scanning (e.g., Pa11y Default )
- Integration test setup (e.g., Selenium Suggestion )
- Visual regression setup (e.g., Backstop Suggestion )
Project Management Tool
Every project, no matter the size, should use a project management tool to keep track of ongoing tasks and to do items. The project management tool should be linked to somewhere in the project’s GitHub repository so that others can find it easily.
Continuous Integration/Continuous Deployment
Developers don’t always remember to run the test suite. That’s why we have Continuous Integration services to run the tests automatically after each commit. CI also helps ensure there’s nothing specific to the developer’s machine that makes the tests pass.
A Continuous Deployment service allows a development team to receive rapid feedback on new features or bug fixes. CD also helps ensure deployment and infrastructure issues are identified earlier in a release process, and are scoped to a smaller number of changes.
Pick a CI/CD service with a GitHub integration so that the build status can be seen for each pull request.
Code coverage metrics
Aim for more than 90% of your source code to be covered by tests; worry if coverage drops below 80%. For repositories with multiple programming languages/components (e.g., front and back ends), ensure that coverage reports are aggregated and reported on the entire project, in addition to reports on individual components.
Static analysis for code quality
A good code review process is essential to writing good code. But certain code problems are difficult for humans to spot. Duplication, for example: if new code is an exact duplicate of code from an existing file in a project, that might not be caught in a code review. Static analysis tools catch duplication, security concerns, and more. Also see Static Security Analysis.
- Code Climate Quality Suggestion
Applications require specific versions of programming languages, libraries, databases, services, and configuration to execute. A dependency management solution helps abstract that complexity and makes it easier for cross-functional teams to create consistent, reproducible, local development environments.
Developers needing to deploy their code beyond their local environment should use either:
a cloud.gov sandbox Standard
a TTS-managed AWS sandbox account Standard
or Federalist (for static web sites) Standard
The use of tools such as
ngrok, which make your locally running services visible to the internet,
are not allowed because they present a large security concern. Consult
#infrastructure on Slack for any questions.