It's definitely time to add testing for this bot. I'd certainly rathernot take the route of writing a second bot that feeds commands / examines output, so I'd like to try using a library called dpytest to do this.
The library is still in alpha (0.5.3) and may have feature gaps and/or breaking changes at times ... but I'd really rather not write a second bot just to test this one.
This issue has been replaced by Issue #16; rather than using the dpytest library, I will be abstracting the work into testable files without dependence on Discord api/websockets.
It's definitely time to add testing for this bot. I'd certainly rathernot take the route of writing a second bot that feeds commands / examines output, so I'd like to try using a library called dpytest to do this.
The library is still in alpha (0.5.3) and may have feature gaps and/or breaking changes at times ... but I'd really rather not write a second bot just to test this one.