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.

Sign up for GitHub

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

Jump to bottom

Testing mepo #276

Open
pchakraborty opened this issue Apr 15, 2024 · 5 comments
Open

Testing mepo #276

pchakraborty opened this issue Apr 15, 2024 · 5 comments
Assignees
@pchakraborty

Comments

@pchakraborty
Copy link
Collaborator

pchakraborty commented Apr 15, 2024 •
edited
Loading

Evolving list of tests we need to create

  • create/delete annotated tags
  • test registry, component and other classes, and not just the mepo commands
@pchakraborty pchakraborty self-assigned this Apr 15, 2024
@pchakraborty pchakraborty mentioned this issue Apr 15, 2024
Closed
@mathomp4
Copy link
Member

Query: is registry a hepo thing? (I don't remember it in mepo land...but maybe?)

@pchakraborty
Copy link
Collaborator Author

I renamed config_file (components.yaml) as registry. With mepo config, there were too many configs.

@mathomp4
Copy link
Member

Ah. Makes sense.

I suppose with a major version number, you are free to rename all commands. config config config :)

@pchakraborty
Copy link
Collaborator Author

The only "external" change is in mepo clone's optional argument (--config-file becomes --registry). All other changes are internal.

@pchakraborty
Copy link
Collaborator Author

Added some more tests #316. This time used pytest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pchakraborty pchakraborty

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mathomp4 @pchakraborty