Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Continous Testing and Delivery #49

Open
gubuntu opened this issue Jul 6, 2017 · 2 comments
Open

Implement Continous Testing and Delivery #49

gubuntu opened this issue Jul 6, 2017 · 2 comments

Comments

@gubuntu
Copy link
Contributor

gubuntu commented Jul 6, 2017

From @lucernae on March 7, 2017 12:17

Implement systematic TDD for Pull Request (or might be possible with Travis - docker)

  • Learn git webhook
  • Need a test server
  • Need to spin up celery based testing, (including broker and worker), might need ansible
  • Container order and spin up rule
  • Testing scripts.

Copied from original issue: kartoza/geosafe#57

@gubuntu
Copy link
Contributor Author

gubuntu commented Jul 6, 2017

From @Gustry on March 7, 2017 13:1

Can't we use the geonode architecture ?
Because we need to do that for the QGIS Server backend ? As it will be integrated in the geonode repo, we will need to setup and write tests for their architecure.

@lucernae
Copy link
Collaborator

lucernae commented Jul 6, 2017

This repo already uses Travis to check that standard deployment command working, to know that at least the deployment command didn't failed.
We didn't run package unittest here because it is redundant with each unittest in submodules.
On a different node, I'm still struggling to create TDD for geosafe repo, because it depends on this docker-geosafe repo to setup the dependencies (geonode version, settings, etc), but the unittest should run on geosafe repo.

@gubuntu gubuntu removed the ready label May 8, 2018
@gubuntu gubuntu added this to the Mozambique milestone May 8, 2018
@gubuntu gubuntu removed this from the Mozambique milestone Sep 3, 2018
@gubuntu gubuntu removed the analyzing label Jul 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants