Add integration tests on `testing` + `staging` instances.
The testing
and staging
environment use a database that contains real data and does not have any access to repositories on GitLab or GitHub. It is not used for integration tests but this should be used for this purpose.
I propose to create integration tests and so:
-
Create a repository owned by a new user on gitlab.g.o
and it will be possible to push new commits to this repository, as well as refreshing the POT files. We need at least one repository, but more, with different POT generation methods would be better. -
Create integration tests scenarios in order to test the processes, including refreshing POT files, uploading files to DL and committing/pushing references to the repository. -
Flush the database on a regular basis (ie: twice a day) and refresh the repository to its initial state. Display a countdown on Damned Lies to prevent unwanted behaviour or misunderstanding.