I’ve been thinking a little about automated testing and if it could be improved a bit.
It would be great to capture an overview of how OFN is tested and what automation and continuous integration there is on a wiki page. I started https://github.com/openfoodfoundation/openfoodnetwork/wiki/Testing to capture a link to Jenkins. Also are the ideas on Continuous Integration · openfoodfoundation/openfoodnetwork Wiki · GitHub all related to Jenkins?
I’m not sure how to get test failure email notifications from Jenkins.
How come Jenkins is used rather than Travis? As Travis is pretty easy to work with, and also a boon for just enabling a forked project, could we try to get it passing for OFN?
Would like to get test coverage for ofn_deployment. Am working on this using Travis.
There are definite potential problems when localising to a different place than Aus. I noticed a few controller tests are hardcoded to check for strings that arent available or have a different spelling with en-GB, hence fail. Do you think its desirable to be able to pass the full test suite under a different locale?
Also would like to understand better what Jenkins does in terms of deploying to staging. Is it automatic based on tests passing?
And thinking further ahead, it would be neat to discuss what might be developed for other installs to have 1 push deploy to staging/production. Not sure what that means w.r.t. Jenkins, ansible, etc.
[posting this here so that responses can get turned into scope of work]