make a standard set of bot behaviors for automated library testing

[yourWaifu]

I was asked by Jamieλ on discord to open a issue about this

[yourWaifu]

I think we should of course start with connecting, and heartbeet
and then sending messages like noramal one then all types of embeds and attactments
and then testing rate limits for sending messages
not in order:
deleting messages, editing messages,
creating, deleting, editing channels
dms
bans
kicking
unban
create, delete, edit servers
users leaving and joining
Channel events, Message events, Role events, Presence, Server events on websocket
and I think typing

[TiltMeSenpai]

Do we want to test ETF on the websocket also? Erlang also has a quickcheck module so it wouldn't be too hard (I think)

[yourWaifu]

if you need to test erlang stuff. sure, I guess. I don't know what erlang is tho

[TiltMeSenpai]

So basic plan (that imma start working on): After a lib confirms that auth/ratelimits work properly (fuck knows how), connect to an orchestration server on Discord. Server has bot connect to a testing server, where #general logs test progress. Bot is assigned a testing channel through dm with "?test ." Set of commands are ran in that channel, with pass|fail, completed/total and percentage progresses sent to #general by the testing bot. After testing completes, the bot being tested is kicked from the orchestration server to keep things clean.