Needs tests

[hannesveit]

Since there are currently no tests, it's hard to judge whether a new contribution will introduce subtle bugs / break currently supported functionality. It's basically up to the developer and/or the reviewer to manually test the tool in all supported scenarios as best as they can.

I'm working on a test suite with some unit tests and functional tests, which authenticate the API and create new test groups / supergroups, send random messages to those groups, and then delete those messages, and finally clean up and delete the test groups.

This should make testing and reviewing changes much safer.

[hannesveit]

One thing to think about... I’d like to confirm that the script doesn’t try to delete someone else’s messages, for instance. That can’t be tested in groups that we create during the tests, since those will only contain our own messages obviously.

Maybe post and delete a few messages in an existing public group? Are there appropriate “test groups” where people wouldn’t be offended by a bunch of random messages?

Or we could create one for this purpose...

[hannesveit]

Ah, we can just invite a bot and make it to say something :)