nelse003 / exhaustive_search

Testing exhaustive search algorithms for crystallographic occupancy refinement and surrounding problems
0 stars 0 forks source link

Automate validation.py as an integration test #50

Open nelse003 opened 6 years ago

nelse003 commented 6 years ago

Aim: Run validation code* at least at every code change/ daily.

Validation code: Minimal:

Enhancements:

Consider closed if minimal condition met, then move enhancements to new issues.

Questions:

nelse003 commented 6 years ago

How:

Needed:

Dockerfile : Like that in XCE repo- to be in exhaustive_search repo

./run_tests

Bash script that just shows that docker is ok... Assuming placholder for further tests?

compile_test.py

Changes enbvironment variables and and imports all xce components. this is considered a "Build/ compile test"?

Travis CI needs:

Read: https://docs.travis-ci.com/user/getting-started/

.travis.yml (XCE version)

- install: docker build -t reskyner/xce Builds the version of docker

Not sure where this is pointing to, but should be getting the docker build? Thought his would be at rskyner/ccp4_docker

script: docker run reskyner/xce /bin/bash -c "/ccp4/bin/ccp4-python /XChemExplorer/compile_test.py"

This runs the compile_test.py script using docker image

nelse003 commented 6 years ago

https://medium.com/mobileforgood/coding-tips-patterns-for-continuous-integration-with-docker-on-travis-ci-9cedb8348a62 https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings

nelse003 commented 6 years ago

Need to:

Apply more tests: