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

Tests against command output #62

Open
ChaoticTempest opened this issue Sep 10, 2021 · 0 comments
Open

Tests against command output #62

ChaoticTempest opened this issue Sep 10, 2021 · 0 comments

Comments

@ChaoticTempest
Copy link
Member

ChaoticTempest commented Sep 10, 2021

With a lot of changes hitting in the future, testing will prove vital to making sure we get all of them working properly.

Currently output for commands are being printed to stdout which is really hard to test against. Some potential solutions could include just returning it and allowing some tests to be ran against them. Each of the commands from what I've seen just return Result<()> AFAIK.

This could be a large undertaking though, due to the amount of types that are present. Hopefully after reducing the boilerplate and deduplicating several types like Sender, we can get to a point where we can do this more easily.

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

No branches or pull requests

1 participant