Tests are ugly and bad. We also need to structure them better, e.g.
[ ] test_base_ for functions that don't need data from the server (e.g. config...).
[ ] test_localcache_ to test the getOML* functions using a local cache dir (maybe this could also be test_base_).
[ ] test_mainserver_ to test stuff except functions that require write access on the main server.
[ ] test_paper_ to test the code that was published in papers to ensure that this still works.
[ ] test_testserver_ to test stuff that requires write access (basically the upload, delete and tag functions). Here, we could also add tests for the getOML* functions to see whether API changes on the test server break something. The tests here may need the following order: list, download/create, tag, untag, upload, delete
Tests are ugly and bad. We also need to structure them better, e.g.
test_base_for functions that don't need data from the server (e.g. config...).test_localcache_to test the getOML* functions using a local cache dir (maybe this could also betest_base_).test_mainserver_to test stuff except functions that require write access on the main server.test_paper_to test the code that was published in papers to ensure that this still works.test_testserver_to test stuff that requires write access (basically the upload, delete and tag functions). Here, we could also add tests for the getOML* functions to see whether API changes on the test server break something. The tests here may need the following order: list, download/create, tag, untag, upload, delete