Move tests of export archive migration into aiida-core #3059
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes aiida-export-migration-tests' issue.
In order to easier skip tests from aiida-core (using
unittest.skip()
), the tests that were implemented in theaiida-export-migration-tests
repo have been moved to aiida-core underaiida.backends.tests.tools.importexport.migration.
.Furthermore, the accompanying utility functions have been merged into
aiida.backends.tests.utils.archives
.Note: There is no need to change the version dependency of
aiida-export-migration-tests
,however, a new version should be released and used in PR #3052. However, I will not introduce this change until this PR has been merged, since more changes will need to be done to the imports of these test-files.Edit: I have upped the dependency of
aiida-export-migration-tests
to v0.5.2.