CHEFS Operational Tools

 Size and Diversity:

FIDER - Common Hosted Form Service Feedback
Whether we’re fixing issues or developing new features, we frequently consult FIDER to gauge which are the most requested. This helps us prioritize our work. FIDER is also where we add comments to indicate when issues have been resolved and to provide status updates.

DEPENDABOT
Helps us maintain CHEFS security via exploits for third party packages we're using

CODEQL
Scans the code and helps us find ways to improve the security of CHEFS

ACTIONS
Helps us reduce the time taken for any CHEFS improvement from development to production through CI/CD.

ACS
Further helps us find ways to improve the security of CHEFS by checking known Openshift cluster vulnerabilities

OWASP
Looks for HTTP server security configurations that are needed

CODE CLIMATE
Helps us find areas of the code that need test coverage. Increasing test coverage shows that we're actively maintaining CHEFS. More test coverage also helps us reduce the likelihood of bugs when future changes are made.

JEST
Tests reduce likelihood of future bugs with new changes

CYPRESS TESTS
These are end to end tests, simulating how a user would interact with the system starting at the front end, through the back end, and back to the front end. this helps us prove consistency of the product and helps reduce the likelihood of bugs with new changes.

KIBANA
Real time monitoring of http status codes and database problems to notify the team when issues arise, how often an issue occurs, so that we can more easily pinpoint where a problem is happening and when.

SYSDIG
Real time monitoring of resource usage for our infrastructure, in case we run out of storage space, or memory,  we will be notified.

• Documentation in Backstage
  Support for users that want to know how CHEFS works such as the team roles, a submissions workflow, how to export