Created by: mkszuba
The test registry_public_cores.t now uses frozen test database
Using the public registry server in tests is fragile, especially around release time. See https://www.ebi.ac.uk/panda/jira/browse/ENSCORESW-2325
Registry tests can now work offline and not have to worry about version mismatches between the API and what the public server provides.
Had to rewrite the "registry knows more than 10 DBAs" test to "registry knows at least 1 DBA" because by default that is what MultiTestDB provides. Might make sense to tweak the settings to get at least two so that we can make sure the list of DBAdaptor is really appended to.
Have you added/modified unit tests to test the changes?
It was a test itself that needed changes.
If so, do the tests pass/fail?
The modified test passes.
Have you run the entire test suite and no regression was detected?
Not run, under the assumption that a change in one test suite that does not write anything to the database really shouldn't affect any of the others.