Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate tests for old codebase #53

Open
mih opened this issue Sep 7, 2023 · 1 comment
Open

Migrate tests for old codebase #53

mih opened this issue Sep 7, 2023 · 1 comment

Comments

@mih
Copy link
Member

mih commented Sep 7, 2023

My suggestion for an implementation strategy and to #3 would be to start with a minimalistic implementation. Following the pattern of the archivist remote in next, just a few lines that import the old code base.

Next migrate/copy the old test implementations here, and run them in the coming CI setup (#51).

Once this has established a test and coverage baseline, we can broaden the coverage and depth of testing.

@mih
Copy link
Member Author

mih commented Sep 13, 2023

This more I think about a migration path, the more questions and fewer confidence I have (#57). Therefore, I would want to revise my proposal above.

We should NOT start with a minimalistic implementation, but start with no implementation at all, and plainly use what is installed by datalad-core.

We should start with JUST the migration of test code, and then proceed with the broadening of the coverage.

My hope is that this generated the necessary insight to comeup with a strategy -- while avoiding the distraction of a new implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant