-
-
Notifications
You must be signed in to change notification settings - Fork 729
Continuous Integration
Continuous Integration testing (CI) ensures that all automated tests are run each time somebody pushes code to the GitHub repository. Currently, we support two different CI systems.
- Travis CI
- Buildkite
Travis offers a free testing infrastructure for free software projects. All forks of the Open Food Network can use Travis CI. The .travis configuration file contains all commands to execute on a Travis server to run the tests.
https://travis-ci.org/openfoodfoundation/openfoodnetwork
Buildkite provides a nice user interface to manage your own CI servers. The Australian team uses it to run tests and deploy to staging and production servers. But you have to pay for an account. See Deployment with Buildkite for more information.
Development environment setup
- Pipeline development process
- Bug severity
- Feature template (epic)
- Internationalisation (i18n)
- Dependency updates
Development
- Developer Guidelines
- The process of review, test, merge and deploy
- Making a great commit
- Making a great pull request
- Code Conventions
- Database migrations
- Testing and Rspec Tips
- Automated Testing Gotchas
- Rubocop
- Angular and OFN
- Feature toggles
- Stimulus and Turbo
Testing
- Testing process
- OFN Testing Documentation (Handbooks)
- Continuous Integration
- Parallelized test suite with knapsack
- Karma
Releasing
Specific features
Data and APIs
Instance-specific configuration
External services
Design