-
Notifications
You must be signed in to change notification settings - Fork 11
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
Implement current integrations tests as rust tests #54
Conversation
8be8073
to
8d75688
Compare
The way I see it, the current tests should still remain as tests for the cli, which is why they weren't removed or modified by this PR. |
Anothony, thanks for introducing me to |
Honestly, that's about it. |
Also, if you would like to merge this, give me time to fix the failing CI, cargo check is failing and I need to investigate that update: Okay, I just need to update the tests to account for the changes from #51 |
another pro is being able to distinguish between whether an issue exists in the CLI or the library itself (if existing tests fail but new ones don't, the CLI is the issue whereas if both fail then it's probably a library issue) |
Thanks for sharing those details @AnthonyMichaelTDM. For the sake of simplicity, I prefer we leave this one out. Testing the CLI/lib in two ways sounds more complicated than needs be. As for the niceties of integrating with That being said, would you care to join me in maintaining this repo? what about |
Sure, I’m down to help maintain these repos
|
just to confirm, we're leaving this out right? if so I"m going to close the PR |
uses the goldenfile crate to fail tests if the "goldenfile" is changed
merging will require updating both #53 (to add the tests to the CI) and #51 (to add a test for const numeric enums), or if those are merged first then this will need to be updated (which is probably the better approach).