Add "Forbidden: bot was kicked from the group chat" exception

[karb0f0s]

From @karb0f0s on April 4, 2018 11:32

HTTP code: 403
Error message:

• Forbidden: bot was kicked from the group chat exception
• Forbidden: bot was kicked from the group channel exception
• Forbidden: bot was kicked from the group supergroup exception

You receive this error if you add bot to group, remove it, and try to send message to that group afterwards

Copied from original issue: TelegramBots/Telegram.Bot#662

[karb0f0s]

I see two possible test runs for this exception:

• user should remove bot from test chat before excecution (and add back after)
• create some BotBlockedChat and add/remove bot from there (i created two chats, deleted them, but I still receive this error when send messages)

[karb0f0s]

For my test case I created 3 groups in which I added and then removed my testbot:

long[] groups =
{
  -1001100532129, // BotBlockedSupergroup
  -1001298749133, // BotBlockedGroup
  -262679471, // BotBlockedChannel
};

after upgrading BotBlockedSupergroup from regular group to supergroup I caught a Bad Request: group chat was upgraded to a supergroup chat error

[karb0f0s]

I'd like to commit the tests with fixed chatIds, and maybe move them to settings/class fixture later. Is this appropriate?

[karb0f0s]

From @tuscen on April 4, 2018 13:55

I'm okay with more interactivity during integ tests because some of them couldn't really be done either without more configs (several group chats and channels for different tests, etc) or without user interaction. But @pouladpld have different opinion on this.

[karb0f0s]

@tuscen Sergey Khabibullin unofficially created a wrapper classes for TDLib and published them as NuGet package TDLib.
I'm planning to add Telegram client features to tests, so we do not have to wait for user interactions, but send actions through TDLib.

[karb0f0s]

From @tuscen on April 4, 2018 14:48

@karb0f0s Nice. It would be super helpful 👍

[mihailmariusiondev]

Any news for this?