Discuss testing and deployment

[bartjkdp]

Added by @ericherman

[bartjkdp]

We discussed the following during the weekly development meeting:

Testing We are not running the end-to-end tests in GitHub Actions. We would like to run the tests in CI as well, so we get more confidence merging changes. We have Cypress tests, that we can integrate.

Deployment We would like to have a clear separation between merging pull requests and deploying them to the production environment of Amsterdam.

• For the frontend we already have separation. Pull requests are merged into the develop branch and released by merging to master.
• For the backend we do not have separation. Pull requests are merged into the master branch and released directly to production.

Proposed solutions:

• Introduce a develop branch for backend as well.
• Do not automatically release when merging to master, but create a manual job for that.

[bartjkdp]

We discussed the following during the weekly development meeting:

Testing

• @bartjkdp will do some experiments of running the existing Cypress end-to-end tests from the frontend repository in GitHub Actions and report back next week.

Deployment

• Deployment for VNG and Amsterdam backend is working just fine. Amsterdam frontend is experiencing some problems with keeping all the configuration in sync. The current way of working is prone to errors. Probably integrating Amsterdam/signals-frontend#1024 with the pipeline would help a lot. @jpoppe is currently working on this. It would be nice if he can share the details next week.

[bartjkdp]

End-to-end testing will be followed up in Signalen/frontend#64 and deployment of Amsterdam frontend in https://github.com/Amsterdam/signals-frontend/pull/1047.