You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: