dataverse-client-python icon indicating copy to clipboard operation
dataverse-client-python copied to clipboard

Published 20 hours ago • verified publisher icon IQSS

Set up Travis for Continuous integration

Open astrofrog opened this issue 10 years ago • 2 comments

It would be nice to set up Travis CI for continuous integration. The only problem with this is that an API key is required to run the tests - however, Travis has a mechanism for storing environment variables securely, so we could use that. But then the downside is that every time the test server is wiped, the API key would need to change. To resolve this, I think it would be necessary to have another test server that exists solely for the purpose of running the tests and which is never wiped?

I can provide advice on setting up Travis, if needed.

astrofrog avatar Apr 29 '15 10:04 astrofrog

Related: #10.

pdurbin avatar Apr 29 '15 10:04 pdurbin

But then the downside is that every time the test server is wiped, the API key would need to change.

I would suggest creating (and deleting) a user for every test run. That's what I do at https://github.com/IQSS/dataverse/blob/master/src/test/java/edu/harvard/iq/dataverse/api/SearchIT.java

See also this comment I just made: https://github.com/IQSS/dataverse-client-python/issues/10#issuecomment-99127268

pdurbin avatar May 05 '15 16:05 pdurbin