Need some kind of automated testing for actual end-result functionality.
a069026 broke the path to the data file needed for +rules command.
Immediately after fixing that, I broke 6a349d6 the path to the data file needed for messageReactionRemove
There may be a way to store these paths in a more stable way, but at the end of the day it looks like one kind of error that we may generate somewhat regularly and not catch for a long time for infrequently-used functions. It would be amazing if there was an automated way to test the full set of expected/stable functions against every build.
Super quick googling for inspiration:
https://github.com/DXsmiley/dismock
https://pypi.org/project/distest/
This may be a place where rolling our own solution would be best, or there may be an existing solution which works great for us.
Need some kind of automated testing for actual end-result functionality.
a069026 broke the path to the data file needed for +rules command.
Immediately after fixing that, I broke 6a349d6 the path to the data file needed for messageReactionRemove
There may be a way to store these paths in a more stable way, but at the end of the day it looks like one kind of error that we may generate somewhat regularly and not catch for a long time for infrequently-used functions. It would be amazing if there was an automated way to test the full set of expected/stable functions against every build.
Super quick googling for inspiration:
https://github.com/DXsmiley/dismock
https://pypi.org/project/distest/
This may be a place where rolling our own solution would be best, or there may be an existing solution which works great for us.