sable

irctest.self_tests.cases.IrcTestCaseTestCase
	sable
test_message_matching_negative[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ... 123]	.
test_message_matching_negative[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ... :]	.
test_message_matching_negative[{'command': 'PING', 'params': ['abc']}-PONG def]	.
test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello2]	.
test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan2 hello]	.
test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan :hi]	.
test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan2 hello]	.
test_message_matching_negative[{'nick': 'foo', 'command': 'PRIVMSG'}-:foo2!baz@qux PRIVMSG #chan hello]	.
test_message_matching_negative[{'nick': 'foo', 'command': 'PRIVMSG'}-@tag1=bar :foo2!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_negative[{'nick': 'foo', 'command': 'PRIVMSG'}-PRIVMSG #chan :hi]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello2]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan2 hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2=baz PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello]	.
test_message_matching_negative[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-:foo!baz@qux PRIVMSG #chan hello]	.
test_message_matching_negative[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=bar;tag2= PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-PRIVMSG #chan hello]	.
test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]	.
test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]	.
test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMG #chan :hello]	.
test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello2]	.
test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan2 hello]	.
test_message_matching_negative_message[expected command to match PING, got PONG]	.
test_message_matching_negative_message[expected command to match PRIVMSG, got PRIVMG0]	.
test_message_matching_negative_message[expected command to match PRIVMSG, got PRIVMG1]	.
test_message_matching_negative_message[expected command to match PRIVMSG, got PRIVMG2]	.
test_message_matching_negative_message[expected nick to be foo, got None instead]	.
test_message_matching_negative_message[expected nick to be foo, got foo2 instead0]	.
test_message_matching_negative_message[expected nick to be foo, got foo2 instead1]	.
test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan', 'hello2']0]	.
test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan', 'hello2']1]	.
test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan', 'hello2']2]	.
test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan2', 'hello']0]	.
test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan2', 'hello']1]	.
test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan2', 'hello']2]	.
test_message_matching_negative_message[expected params to match ['#chan', StrRe(r'hello.*')], got ['#chan', 'hi']]	.
test_message_matching_negative_message[expected params to match ['#chan', StrRe(r'hello.*')], got ['#chan2', 'hello']]	.
test_message_matching_negative_message[expected params to match ['nick', '...', OptStrRe(r'[a-zA-Z]+')], got ['nick', '...', '']]	.
test_message_matching_negative_message[expected params to match ['nick', '...', OptStrRe(r'[a-zA-Z]+')], got ['nick', '...', '123']]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {'tag1': 'value1'}]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {}]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, got {'tag1': 'bar', 'tag2': ''}]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, got {'tag1': 'bar', 'tag2': 'baz'}]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, got {'tag1': 'value1'}]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {'tag1': 'bar', 'tag2': ''}]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {'tag1': 'value1'}]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {}0]	.
test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {}1]	.
test_message_matching_negative_message[expected tags to match {'tag1': ANYSTR}, got {'tag1': 'bar', 'tag2': ''}]	.
test_message_matching_negative_message[expected tags to match {'tag1': ANYSTR}, got {}0]	.
test_message_matching_negative_message[expected tags to match {'tag1': ANYSTR}, got {}1]	.
test_message_matching_negative_message[expected tags to match {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {'tag1': 'value1'}]	.
test_message_matching_negative_message[expected tags to match {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {}]	.
test_message_matching_positive[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ... abc]	.
test_message_matching_positive[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ...]	.
test_message_matching_positive[{'command': 'PING', 'params': ['abc']}-PING abc]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-:foo!baz@qux PRIVMSG #chan hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-@tag1=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-@tag1=bar;tag2= PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan :hello]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan hello2]	.
test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan hello]	.
test_message_matching_positive[{'nick': 'foo', 'command': 'PRIVMSG'}-:foo!baz@qux PRIVMSG #chan hello]	.
test_message_matching_positive[{'nick': 'foo', 'command': 'PRIVMSG'}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag3= PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=value1 PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=;tag2=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]	.
test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello0]	.
test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello1]	.
test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag2=bar PRIVMSG #chan :hello]	.
irctest.server_tests.account_registration.RegisterBeforeConnectDisallowedTestCase
	sable
testBeforeConnect	.
irctest.server_tests.account_registration.RegisterBeforeConnectTestCase
	sable
testBeforeConnect	s
irctest.server_tests.account_registration.RegisterEmailVerifiedAfterConnectTestCase
	sable
testAfterConnect	s
irctest.server_tests.account_registration.RegisterEmailVerifiedBeforeConnectTestCase
	sable
testBeforeConnect	s
irctest.server_tests.account_registration.RegisterTestCase
	sable
testRegisterDefaultName "If <account> is , then this value is the user’s current nickname." System Message: WARNING/2 (<string>, line 2); backlink* Inline emphasis start-string without end-string.	.
testRegisterDifferentName Requested account name differs from the nick	.
testRegisterSameName Requested account name is the same as the nick	.
irctest.server_tests.account_tag.AccountTagTestCase
	sable
testInvite	.
testPrivmsg	.
irctest.server_tests.away.AwayTestCase
	sable
testAway	.
testAwayAck "The server acknowledges the change in away status by returning the RPL_NOWAWAY and RPL_UNAWAY numerics." -- https://modern.ircdocs.horse/#away-message	.
testAwayEmptyMessage "If [AWAY] is sent with a nonempty parameter (the 'away message') then the user is set to be away. If this command is sent with no parameters, or with the empty string as the parameter, the user is no longer away." -- https://modern.ircdocs.horse/#away-message	.
testAwayPrivmsg "Servers SHOULD notify clients when a user they're interacting with is away when relevant" -- https://modern.ircdocs.horse/#away-message "<client> <nick> :<message>" -- https://modern.ircdocs.horse/#rplaway-301	.
testAwayUserhost "Servers SHOULD notify clients when a user they're interacting with is away when relevant" -- https://modern.ircdocs.horse/#away-message "<client> <nick> :<message>" -- https://modern.ircdocs.horse/#rplaway-301	.
testAwayWhois "Servers SHOULD notify clients when a user they're interacting with is away when relevant" -- https://modern.ircdocs.horse/#away-message "<client> <nick> :<message>" -- https://modern.ircdocs.horse/#rplaway-301	.
irctest.server_tests.away_notify.AwayNotifyTestCase
	sable
testAwayNotify Basic away-notify test.	.
testAwayNotifyOnJoin The away-notify specification states: "Clients will be sent an AWAY message [...] when a user joins and has an away message set."	.
irctest.server_tests.bot_mode.BotModeTestCase
	sable
testBotChannelMessage	s
testBotMode	s
testBotPrivateMessage	s
testBotWhois	s
testBotWhox	s
irctest.server_tests.buffering.BufferingTestCase
	sable
testNoTags[byteperbyte-colon]	.
testNoTags[byteperbyte-no colon]	.
testNoTags[charperchar-colon]	.
testNoTags[charperchar-no colon]	.
testNoTags[whole-colon]	.
testNoTags[whole-no colon]	.
irctest.server_tests.cap.CapTestCase
	sable
testCapRemovalByClient Test CAP LIST and removal of caps via CAP REQ :-tagname.	s
testInvalidCapSubcommand “If no capabilities are active, an empty parameter must be sent.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-list-subcommand>	.
testIrc301CapLs Current version: "The LS subcommand is used to list the capabilities supported by the server. The client should send an LS subcommand with no other arguments to solicit a list of all capabilities." "If a client has not indicated support for CAP LS 302 features, the server MUST NOT send these new features to the client." -- <https://ircv3.net/specs/core/capability-negotiation.html> Before the v3.1 / v3.2 merge: IRCv3.1: “The LS subcommand is used to list the capabilities supported by the server. The client should send an LS subcommand with no other arguments to solicit a list of all capabilities.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-ls-subcommand> IRCv3.2: “Servers MUST NOT send messages described by this document if the client only supports version 3.1.” -- <http://ircv3.net/specs/core/capability-negotiation-3.2.html#version-in-cap-ls>	.
testNakExactString “The argument of the NAK subcommand MUST consist of at least the first 100 characters of the capability list in the REQ subcommand which triggered the NAK.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-nak-subcommand>	.
testNakWhole “The capability identifier set must be accepted as a whole, or rejected entirely.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-req-subcommand>	.
testNoMultiline301Response Current version: "If the client supports CAP version 302, the server MAY send multiple lines in response to CAP LS and CAP LIST." This should be read as disallowing multiline responses to pre-302 clients. -- <https://ircv3.net/specs/extensions/capability-negotiation#multiline-replies-to-cap-ls-and-cap-list>	.
testNoReq Test the server handles gracefully clients which do not send REQs. “Clients that support capabilities but do not wish to enter negotiation SHOULD send CAP END upon connection to the server.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-end-subcommand>	.
testReqOne Tests requesting a single capability	.
testReqOneThenOne Tests requesting two capabilities in different messages	.
testReqPostRegistration Tests requesting more capabilities after CAP END	.
testReqTwo Tests requesting two capabilities at once	.
testReqUnavailable Test the server handles gracefully clients which request capabilities that are not available. <http://ircv3.net/specs/core/capability-negotiation-3.1.html>	.
irctest.server_tests.channel_rename.ChannelRenameTestCase Basic tests for channel-rename.
	sable
testChannelRename	.
irctest.server_tests.chathistory.ChathistoryTestCase
	sable
testChathistoryEventPlayback[AFTER]	s
testChathistoryEventPlayback[AROUND]	s
testChathistoryEventPlayback[BEFORE]	s
testChathistoryEventPlayback[BETWEEN]	s
testChathistoryEventPlayback[LATEST]	s
testChathistoryNoEventPlayback Tests that non-messages don't appear in the chat history when event-playback is not enabled.	s
testChathistory[AFTER]	s
testChathistory[AROUND]	s
testChathistory[BEFORE]	s
testChathistory[BETWEEN]	s
testChathistory[LATEST]	s
testInvalidTargets	s
irctest.server_tests.chmodes.ban.BanModeTestCase
	sable
testBan Basic ban operation	.
testBanException `Exception mode <https://modern.ircdocs.horse/#exception-channel-mode`_, detected using ISUPPORT EXCEPTS and checked against ISUPPORT CHANMODES Docutils System Messages System Message: ERROR/3 (<string>, line 1); backlink Unknown target name: "exception mode <https://modern.ircdocs.horse/#exception-channel-mode".	.
irctest.server_tests.chmodes.key.KeyTestCase
	sable
testKeyNormal	.
testKeyValidation[empty] key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F ) ; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " " System Message: WARNING/2 (<string>, line 5) Block quote ends without a blank line; unexpected unindent. -- https://tools.ietf.org/html/rfc2812#page-8 "Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following: [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696) [ERR_INVALIDKEY](#errinvalidkey-525) MODE echoed with a different key (eg. truncated or stripped of invalid characters) the key changed ignored, and no MODE echoed if no other mode change was valid. System Message: WARNING/2 (<string>, line 18) Bullet list ends without a blank line; unexpected unindent. " -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111	.
testKeyValidation[long] key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F ) ; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " " System Message: WARNING/2 (<string>, line 5) Block quote ends without a blank line; unexpected unindent. -- https://tools.ietf.org/html/rfc2812#page-8 "Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following: [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696) [ERR_INVALIDKEY](#errinvalidkey-525) MODE echoed with a different key (eg. truncated or stripped of invalid characters) the key changed ignored, and no MODE echoed if no other mode change was valid. System Message: WARNING/2 (<string>, line 18) Bullet list ends without a blank line; unexpected unindent. " -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111	.
testKeyValidation[only-space] key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F ) ; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " " System Message: WARNING/2 (<string>, line 5) Block quote ends without a blank line; unexpected unindent. -- https://tools.ietf.org/html/rfc2812#page-8 "Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following: [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696) [ERR_INVALIDKEY](#errinvalidkey-525) MODE echoed with a different key (eg. truncated or stripped of invalid characters) the key changed ignored, and no MODE echoed if no other mode change was valid. System Message: WARNING/2 (<string>, line 18) Bullet list ends without a blank line; unexpected unindent. " -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111	.
testKeyValidation[spaces] key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F ) ; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " " System Message: WARNING/2 (<string>, line 5) Block quote ends without a blank line; unexpected unindent. -- https://tools.ietf.org/html/rfc2812#page-8 "Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following: [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696) [ERR_INVALIDKEY](#errinvalidkey-525) MODE echoed with a different key (eg. truncated or stripped of invalid characters) the key changed ignored, and no MODE echoed if no other mode change was valid. System Message: WARNING/2 (<string>, line 18) Bullet list ends without a blank line; unexpected unindent. " -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111	.
irctest.server_tests.chmodes.modeis.RplChannelModeIsTestCase
	sable
testChannelModeIs Test RPL_CHANNELMODEIS and RPL_CHANNELCREATED as responses to MODE #channel: <https://modern.ircdocs.horse/#rplcreationtime-329> <https://modern.ircdocs.horse/#rplchannelmodeis-324>	.
irctest.server_tests.chmodes.moderated.ModeratedModeTestCase
	sable
testModeratedMode	.
irctest.server_tests.chmodes.mute_extban.MuteExtbanTestCase https://defs.ircdocs.horse/defs/isupport.html#extban It magically guesses what char the IRCd uses for mutes.
	sable
testMuteExtban Basic usage of mute	s
testMuteExtbanExempt Checks +e overrides the mute <https://defs.ircdocs.horse/defs/chanmodes.html#e-ban-exception>	s
testMuteExtbanVoiced Checks +v overrides the mute	s
irctest.server_tests.chmodes.no_external.NoExternalMessagesTestCase
	sable
testNoExternalMessagesMode	.
irctest.server_tests.chmodes.operator.ChannelOperatorModeTestCase Test various error and success cases around the channel operator mode: <https://modern.ircdocs.horse/#channel-operators> <https://modern.ircdocs.horse/#mode-message>
	sable
testChannelOperatorModeChannelAndTargetDoNotExist Test that +o targeting a nonexistent channel and nickname fails as expected.	.
testChannelOperatorModeChannelDoesNotExist Test that +o targeting a nonexistent channel fails as expected. "If <target> is a channel that does not exist on the network, # the ERR_NOSUCHCHANNEL (403) numeric is returned."	.
testChannelOperatorModeSenderAndTargetNonMembers Test that +o where neither the sender nor the target is a channel member fails as expected.	.
testChannelOperatorModeSenderNonMember Test that +o where the sender is not a channel member fails as expected.	.
testChannelOperatorModeSenderPrivsNeeded Test that +o from a channel member without the necessary privileges fails as expected.	.
testChannelOperatorModeSuccess Tests a successful grant of +o in a channel.	.
testChannelOperatorModeTargetDoesNotExist Test that +o targeting a nonexistent nick fails as expected.	.
testChannelOperatorModeTargetNotInChannel Test that +o targeting a user not present in the channel fails as expected.	.
irctest.server_tests.connection_registration.ConnectionRegistrationTestCase
	sable
testConnectionRegistration	.
testEarlyNickCollision Two users register simultaneously with the same nick.	.
testEmptyRealname Syntax: "<client> <command> :Not enough parameters" -- https://defs.ircdocs.horse/defs/numerics.html#err-needmoreparams-461 -- https://modern.ircdocs.horse/#errneedmoreparams-461 Use of this numeric: "The minimum length of <username> is 1, ie. it MUST not be empty. If it is empty, the server SHOULD reject the command with ERR_NEEDMOREPARAMS (even an empty parameter is provided)" https://github.com/ircdocs/modern-irc/issues/85	.
testNickCollision A user connects and requests the same nickname as an already registered user.	.
testNonutf8Realname	.
testNonutf8Username	.
testQuitDisconnects “The server must close the connection to a client which sends a QUIT message.” -- <https://tools.ietf.org/html/rfc1459#section-4.1.3>	.
testQuitErrors “A client session is terminated with a quit message. The server acknowledges this by sending an ERROR message to the client.” -- <https://tools.ietf.org/html/rfc2812#section-3.1.7>	.
irctest.server_tests.connection_registration.PasswordedConnectionRegistrationTestCase
	sable
testNoPassword	s
testPassBeforeNickuser	s
testWrongPassword "If the password supplied does not match the password expected by the server, then the server SHOULD send ERR_PASSWDMISMATCH and MUST close the connection with ERROR." -- https://github.com/ircdocs/modern-irc/pull/172	s
irctest.server_tests.echo_message.EchoMessageTestCase
	sable
testEchoMessage[NOTICE-False-True] <http://ircv3.net/specs/extensions/echo-message-3.2.html>	.
testEchoMessage[PRIVMSG-False-False] <http://ircv3.net/specs/extensions/echo-message-3.2.html>	.
testEchoMessage[PRIVMSG-False-True] <http://ircv3.net/specs/extensions/echo-message-3.2.html>	.
testEchoMessage[PRIVMSG-True-True] <http://ircv3.net/specs/extensions/echo-message-3.2.html>	.
irctest.server_tests.extended_join.MetadataTestCase
	sable
testLoggedIn	s
testNotLoggedIn	s
irctest.server_tests.help.HelpTestCase
	sable
testHelpNoArg[HELPOP]	s
testHelpNoArg[HELP]	s
testHelpPrivmsg[HELPOP]	s
testHelpPrivmsg[HELP]	s
testHelpUnknownSubject[HELPOP]	s
testHelpUnknownSubject[HELP]	s
irctest.server_tests.invite.InviteTestCase
	sable
testInviteAlreadyInChannel "If the user is already on the target channel, the server MUST reject the command with the ERR_USERONCHANNEL numeric." -- https://modern.ircdocs.horse/#invite-message	.
testInviteInviteOnly "To invite a user to a channel which is invite only (MODE +i), the client sending the invite must be recognised as being a channel operator on the given channel." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.7 "When the channel has invite-only flag set, only channel operators may issue INVITE command." -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.7 "When the channel has [invite-only](#invite-only-channel-mode) mode set, only channel operators may issue INVITE command. Otherwise, the server MUST reject the command with the ERR_CHANOPRIVSNEEDED numeric." -- https://modern.ircdocs.horse/#invite-message	.
testInviteNoNotificationForOtherMembers "Other channel members are not notified." -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.7 "Other channel members SHOULD NOT be notified." -- https://modern.ircdocs.horse/#invite-message	.
testInviteOnlyFromUsersInChannel "if the channel exists, only members of the channel are allowed to invite other users" -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.7 " 442 ERR_NOTONCHANNEL "<channel> :You're not on that channel" Returned by the server whenever a client tries to perform a channel affecting command for which the client isn't a member. System Message: WARNING/2 (<string>, line 12) Definition list ends without a blank line; unexpected unindent. " -- https://datatracker.ietf.org/doc/html/rfc2812 " Only members of the channel are allowed to invite other users. Otherwise, the server MUST reject the command with the ERR_NOTONCHANNEL numeric." -- https://modern.ircdocs.horse/#invite-message	.
testInvite[False]	.
testInvite[True]	.
testInvites Test some basic functionality related to INVITE and the +i mode. https://modern.ircdocs.horse/#invite-only-channel-mode https://modern.ircdocs.horse/#rplinviting-341	.
irctest.server_tests.isupport.IsupportTestCase
	sable
testParameters https://modern.ircdocs.horse/#rplisupport-005	.
testPrefix https://modern.ircdocs.horse/#prefix-parameter	.
testTargmax "Format: TARGMAX=[<command>:[limit]{,<command>:[limit]}]" -- https://modern.ircdocs.horse/#targmax-parameter "TARGMAX=[cmd:[number][,cmd:[number][,...]]]" -- https://defs.ircdocs.horse/defs/isupport.html#targmax	s
irctest.server_tests.join.JoinTestCase
	sable
testJoinKey Joins a single channel with a key	.
testJoinKeys Joins two channels, both with keys	.
testJoinManySingleKey Joins two channels, the first one has a key.	.
testJoinNamreply “353 RPL_NAMREPLY "( "=" / "" / "@" ) <channel> :[ "@" / "+" ] <nick> ( " " [ "@" / "+" ] <nick> )” System Message: WARNING/2 (<string>, line 3); backlink Inline emphasis start-string without end-string. System Message: WARNING/2 (<string>, line 4) Block quote ends without a blank line; unexpected unindent. -- <https://tools.ietf.org/html/rfc2812#section-5.2> This test makes a user join and check what is sent to them.	.
testJoinPartiallyInvalid TODO: specify this in Modern	.
testJoinPartiallyInvalidLabeledResponse TODO: specify this in Modern	.
testJoinTwice	.
irctest.server_tests.kick.KickTestCase
	sable
testDoubleKickMessages[False] “The server MUST NOT send KICK messages with multiple channels or users to clients. This is necessarily to maintain backward compatibility with old client software.” -- https://tools.ietf.org/html/rfc2812#section-3.2.8 "The server MUST NOT send KICK messages with multiple channels or users to clients. This is necessary to maintain backward compatibility with existing client software." -- https://modern.ircdocs.horse/#kick-message "Servers MAY limit the number of target users per KICK command via the [TARGMAX parameter of RPL_ISUPPORT](#targmax-parameter), and silently drop targets if the number of targets exceeds the limit." -- https://modern.ircdocs.horse/#kick-message "If the "TARGMAX" parameter is not advertised or a value is not sent then a client SHOULD assume that no commands except the "JOIN" and "PART" commands accept multiple parameters." -- https://defs.ircdocs.horse/defs/isupport.html#targmax "If this parameter is not advertised or a value is not sent then a client SHOULD assume that no commands except the JOIN and PART commands accept multiple parameters." -- https://github.com/ircdocs/modern-irc/pull/113 "If <limit> is not specified, then there is no maximum number of targets for that command." -- https://modern.ircdocs.horse/#targmax-parameter	s
testDoubleKickMessages[True] “The server MUST NOT send KICK messages with multiple channels or users to clients. This is necessarily to maintain backward compatibility with old client software.” -- https://tools.ietf.org/html/rfc2812#section-3.2.8 "The server MUST NOT send KICK messages with multiple channels or users to clients. This is necessary to maintain backward compatibility with existing client software." -- https://modern.ircdocs.horse/#kick-message "Servers MAY limit the number of target users per KICK command via the [TARGMAX parameter of RPL_ISUPPORT](#targmax-parameter), and silently drop targets if the number of targets exceeds the limit." -- https://modern.ircdocs.horse/#kick-message "If the "TARGMAX" parameter is not advertised or a value is not sent then a client SHOULD assume that no commands except the "JOIN" and "PART" commands accept multiple parameters." -- https://defs.ircdocs.horse/defs/isupport.html#targmax "If this parameter is not advertised or a value is not sent then a client SHOULD assume that no commands except the JOIN and PART commands accept multiple parameters." -- https://github.com/ircdocs/modern-irc/pull/113 "If <limit> is not specified, then there is no maximum number of targets for that command." -- https://modern.ircdocs.horse/#targmax-parameter	s
testKickDefaultComment "If a "comment" is given, this will be sent instead of the default message, the nickname of the user issuing the KICK." -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.8	.
testKickNoComment "If no comment is given, the server SHOULD use a default message instead." -- https://modern.ircdocs.horse/#kick-message	.
testKickNonexistentChannel “Kick command [...] Numeric replies: [...] ERR_NOSUCHCHANNEL.	.
testKickPrivileges Test who has the ability to kick / what error codes are sent for invalid kicks.	.
testKickSendsMessages “Once a user has joined a channel, he receives information about all commands his server receives affecting the channel. This includes […] KICK” -- <https://tools.ietf.org/html/rfc1459#section-4.2.1> and <https://tools.ietf.org/html/rfc2812#section-3.2.1> "If a comment is given, this will be sent instead of the default message, the nickname of the user targeted by the KICK." -- https://modern.ircdocs.horse/#kick-message	.
irctest.server_tests.labeled_responses.LabeledResponsesTestCase
	sable
testEmptyBatchForNoResponse	.
testLabeledNoticeResponsesToClient	.
testLabeledNoticeResponsesToSelf	.
testLabeledPrivmsgResponsesToClient	.
testLabeledPrivmsgResponsesToMultipleClients	s
testLabeledPrivmsgResponsesToSelf	.
testNoBatchForSingleMessage	.
testUnknownCommand	.
irctest.server_tests.links.LinksTestCase
	sable
testLinksSingleServer Only testing the parameter-less case. https://datatracker.ietf.org/doc/html/rfc1459#section-4.3.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.4.5 https://github.com/ircdocs/modern-irc/pull/175 " 364 RPL_LINKS System Message: ERROR/3 (<string>, line 10) Unexpected indentation. "<mask> <server> :<hopcount> <server info>" System Message: WARNING/2 (<string>, line 11) Block quote ends without a blank line; unexpected unindent. 365 RPL_ENDOFLINKS "<mask> :End of /LINKS list" In replying to the LINKS message, a server must send replies back using the RPL_LINKS numeric and mark the end of the list using an RPL_ENDOFLINKS reply. System Message: WARNING/2 (<string>, line 17) Definition list ends without a blank line; unexpected unindent. " -- https://datatracker.ietf.org/doc/html/rfc1459#page-51 -- https://datatracker.ietf.org/doc/html/rfc2812#page-48 RPL_LINKS: "<client> * <server> :<hopcount> <server info>" RPL_ENDOFLINKS: "<client> * :End of /LINKS list" -- https://github.com/ircdocs/modern-irc/pull/175/files	s
irctest.server_tests.links.ServicesLinksTestCase
	sable
testLinksWithServices Only testing the parameter-less case. https://datatracker.ietf.org/doc/html/rfc1459#section-4.3.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.4.5 " 364 RPL_LINKS System Message: ERROR/3 (<string>, line 9) Unexpected indentation. "<mask> <server> :<hopcount> <server info>" System Message: WARNING/2 (<string>, line 10) Block quote ends without a blank line; unexpected unindent. 365 RPL_ENDOFLINKS "<mask> :End of /LINKS list" In replying to the LINKS message, a server must send replies back using the RPL_LINKS numeric and mark the end of the list using an RPL_ENDOFLINKS reply. System Message: WARNING/2 (<string>, line 16) Definition list ends without a blank line; unexpected unindent. " -- https://datatracker.ietf.org/doc/html/rfc1459#page-51 -- https://datatracker.ietf.org/doc/html/rfc2812#page-48 RPL_LINKS: "<client> * <server> :<hopcount> <server info>" RPL_ENDOFLINKS: "<client> * :End of /LINKS list" -- https://github.com/ircdocs/modern-irc/pull/175/files	s
irctest.server_tests.messages.NoticeTestCase
	sable
testNotice <https://tools.ietf.org/html/rfc2812#section-3.3.2>	.
testNoticeNonexistentChannel "automatic replies must never be sent in response to a NOTICE message. This rule applies to servers too - they must not send any error reply back to the client on receipt of a notice" <https://tools.ietf.org/html/rfc1459#section-4.4.2> 'automatic replies MUST NEVER be sent in response to a NOTICE message. This rule applies to servers too - they MUST NOT send any error repl back to the client on receipt of a notice." <https://tools.ietf.org/html/rfc2812#section-3.3.2>	.
irctest.server_tests.messages.PrivmsgTestCase
	sable
testEmptyPrivmsg	.
testPrivmsg <https://tools.ietf.org/html/rfc2812#section-3.3.1>	.
testPrivmsgNonexistentChannel <https://tools.ietf.org/html/rfc2812#section-3.3.1>	.
testPrivmsgNonexistentUser <https://tools.ietf.org/html/rfc2812#section-3.3.1>	.
testPrivmsgToUser <https://tools.ietf.org/html/rfc2812#section-3.3.1>	.
irctest.server_tests.messages.TagsTestCase
	sable
testLineTooLong	s
irctest.server_tests.monitor.AuthenticatedExtendedMonitorTestCase
	sable
testExtendedMonitorAccountNotifyNoCap[-] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
testExtendedMonitorAccountNotifyNoCap[-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
testExtendedMonitorAccountNotifyNoCap[monitor_before_connect-] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
testExtendedMonitorAccountNotifyNoCap[monitor_before_connect-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
testExtendedMonitorAccountNotify[-] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
testExtendedMonitorAccountNotify[-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
testExtendedMonitorAccountNotify[monitor_before_connect-] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
testExtendedMonitorAccountNotify[monitor_before_connect-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when account-notify is not enabled by the watcher	s
irctest.server_tests.monitor.ExtendedMonitorTestCase
	sable
testExtendedMonitorAwayNoCap[-] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when away-notify is not enabled by the watcher	s
testExtendedMonitorAwayNoCap[-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when away-notify is not enabled by the watcher	s
testExtendedMonitorAwayNoCap[monitor_before_connect-] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when away-notify is not enabled by the watcher	s
testExtendedMonitorAwayNoCap[monitor_before_connect-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when away-notify is not enabled by the watcher	s
testExtendedMonitorAway[-] Tests https://ircv3.net/specs/extensions/extended-monitor.html with https://ircv3.net/specs/extensions/away-notify	s
testExtendedMonitorAway[-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html with https://ircv3.net/specs/extensions/away-notify	s
testExtendedMonitorAway[monitor_before_connect-] Tests https://ircv3.net/specs/extensions/extended-monitor.html with https://ircv3.net/specs/extensions/away-notify	s
testExtendedMonitorAway[monitor_before_connect-with-cap] Tests https://ircv3.net/specs/extensions/extended-monitor.html with https://ircv3.net/specs/extensions/away-notify	s
testExtendedMonitorSetNameNoCap[False] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when setname is not enabled by the watcher	s
testExtendedMonitorSetNameNoCap[True] Tests https://ircv3.net/specs/extensions/extended-monitor.html does nothing when setname is not enabled by the watcher	s
testExtendedMonitorSetName[False] Tests https://ircv3.net/specs/extensions/extended-monitor.html with https://ircv3.net/specs/extensions/setname	s
testExtendedMonitorSetName[True] Tests https://ircv3.net/specs/extensions/extended-monitor.html with https://ircv3.net/specs/extensions/setname	s
irctest.server_tests.monitor.MonitorTestCase
	sable
testMonitorClear “Clears the list of targets being monitored. No output will be returned for use of this command.“ -- <https://ircv3.net/specs/extensions/monitor#monitor-c>	.
testMonitorConnectedAndDisconnected “If any of the targets being added are online, the server will generate RPL_MONONLINE numerics listing those targets that are online. If any of the targets being added are offline, the server will generate RPL_MONOFFLINE numerics listing those targets that are online.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor--targettarget2>	.
testMonitorForbidsMasks “The MONITOR implementation also enhances user privacy by disallowing subscription to hostmasks, allowing users to avoid nick-change stalking.” -- <http://ircv3.net/specs/core/monitor-3.2.html#watch-vs-monitor> “For this specification, ‘target’ MUST be a valid nick as determined by the IRC daemon.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor-command>	.
testMonitorOneConnected “If any of the targets being added are offline, the server will generate RPL_MONOFFLINE numerics listing those targets that are online.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor--targettarget2>	.
testMonitorOneConnection	.
testMonitorOneConnectionWithQuit	.
testMonitorOneDisconnected “If any of the targets being added are online, the server will generate RPL_MONONLINE numerics listing those targets that are online.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor--targettarget2>	.
testMonitorStatus “Outputs for each target in the list being monitored, whether the client is online or offline. All targets that are online will be sent using RPL_MONONLINE, all targets that are offline will be sent using RPL_MONOFFLINE.“ -- <https://ircv3.net/specs/extensions/monitor#monitor-s>	.
testNickChange	.
testTwoMonitoringOneRemove Tests the following scenario: foo MONITORs qux bar MONITORs qux bar unMONITORs qux qux connects.	.
testUnmonitor	.
irctest.server_tests.multi_prefix.MultiPrefixTestCase
	sable
testMultiPrefix “When requested, the multi-prefix client capability will cause the IRC server to send all possible prefixes which apply to a user in NAMES and WHO output. These prefixes MUST be in order of ‘rank’, from highest to lowest.	.
testNoMultiPrefix When not requested, only the highest prefix should be sent	.
irctest.server_tests.multiline.MultilineTestCase
	sable
testBasic	s
testBlankLines	s
testInvalidBatchTag Test that an unexpected change of batch tag results in FAIL BATCH MULTILINE_INVALID.	s
testInvalidBlankConcatTag Test that the concat tag on a blank message results in FAIL BATCH MULTILINE_INVALID.	s
irctest.server_tests.names.NamesTestCase
	sable
testNames2812 https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5	.
testNames2812Secret The symbol sent for a secret channel is @ instead of =: https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5 https://modern.ircdocs.horse/#rplnamreply-353	.
testNamesInvalidChannel "There is no error reply for bad channel names." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.5 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5 "If the channel name is invalid or the channel does not exist, one RPL_ENDOFNAMES numeric containing the given channel name should be returned." -- https://modern.ircdocs.horse/#names-message	.
testNamesModern https://modern.ircdocs.horse/#names-message	.
testNamesMultipleChannels2812 https://modern.ircdocs.horse/#names-message https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.5 https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5	s
testNamesNonexistingChannel "There is no error reply for bad channel names." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.5 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5 "If the channel name is invalid or the channel does not exist, one RPL_ENDOFNAMES numeric containing the given channel name should be returned." -- https://modern.ircdocs.horse/#names-message	.
irctest.server_tests.part.PartTestCase
	sable
testBasicPart	.
testBasicPartRfc2812 “If a "Part Message" is given, this will be sent instead of the default message, the nickname.”	.
testPartMessage “If a "Part Message" is given, this will be sent instead of the default message, the nickname.”	.
testPartNotInEmptyChannel “442 ERR_NOTONCHANNEL "<channel> :You're not on that channel" Returned by the server whenever a client tries to perform a channel effecting command for which the client isn't a member.” -- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2> According to RFCs, ERR_NOSUCHCHANNEL should only be used for invalid channel names: “403 ERR_NOSUCHCHANNEL System Message: ERROR/3 (<string>, line 13) Unexpected indentation. "<channel name> :No such channel" Used to indicate the given channel name is invalid.” System Message: WARNING/2 (<string>, line 16) Bullet list ends without a blank line; unexpected unindent. -- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2> However, many implementations use 479 instead, so let's allow it. <http://danieloaks.net/irc-defs/defs/ircnumerics.html#403> <http://danieloaks.net/irc-defs/defs/ircnumerics.html#479>	.
testPartNotInNonEmptyChannel “442 ERR_NOTONCHANNEL "<channel> :You're not on that channel" Returned by the server whenever a client tries to perform a channel effecting command for which the client isn't a member.” -- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2> According to RFCs, ERR_NOSUCHCHANNEL should only be used for invalid channel names: “403 ERR_NOSUCHCHANNEL System Message: ERROR/3 (<string>, line 13) Unexpected indentation. "<channel name> :No such channel" Used to indicate the given channel name is invalid.” System Message: WARNING/2 (<string>, line 16) Bullet list ends without a blank line; unexpected unindent. -- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2> However, many implementations use 479 instead, so let's allow it. <http://danieloaks.net/irc-defs/defs/ircnumerics.html#403> <http://danieloaks.net/irc-defs/defs/ircnumerics.html#479>	.
irctest.server_tests.pingpong.PingPongTestCase
	sable
testPing https://github.com/ircdocs/modern-irc/pull/99	.
testPingEmptyToken https://github.com/ircdocs/modern-irc/pull/99	.
testPingNoToken https://github.com/ircdocs/modern-irc/pull/99	.
irctest.server_tests.quit.ChannelQuitTestCase
	sable
testQuit “Once a user has joined a channel, he receives information about all commands his server receives affecting the channel. This includes [...] QUIT” <https://tools.ietf.org/html/rfc2812#section-3.2.1>	.
irctest.server_tests.regressions.RegressionsTestCase
	sable
testCaseChanges	.
testEmptyNick	.
testFailedNickChange	.
testLabeledNick InspIRCd up to 3.16.1 used the new nick as source of NICK changes https://github.com/inspircd/inspircd/issues/2067 https://github.com/inspircd/inspircd/commit/83f01b36a11734fd91a4e7aad99c15463858fe4a	.
testNickRelease	.
testNickReleaseQuit	.
testStarNick	.
irctest.server_tests.sasl.RegistrationTestCase
	sable
testRegistration	.
irctest.server_tests.sasl.SaslTestCase
	sable
testMechanismNotAvailable “If authentication fails, a 904 or 905 numeric will be sent” -- <http://ircv3.net/specs/extensions/sasl-3.1.html#the-authenticate-command>	.
testPlain PLAIN authentication with correct username/password.	.
testPlainFailure PLAIN authentication with incorrect username/password.	.
testPlainLarge Test the client splits large AUTHENTICATE messages whose payload is not a multiple of 400. <http://ircv3.net/specs/extensions/sasl-3.1.html#the-authenticate-command>	.
testPlainLargeEquals400 Test the client splits large AUTHENTICATE messages whose payload is not a multiple of 400. <http://ircv3.net/specs/extensions/sasl-3.1.html#the-authenticate-command>	.
testPlainNoAuthzid “message = [authzid] UTF8NUL authcid UTF8NUL passwd […] Upon receipt of the message, the server will verify the presented (in the message) authentication identity (authcid) and password (passwd) with the system authentication database, and it will verify that the authentication credentials permit the client to act as the (presented or derived) authorization identity (authzid). If both steps succeed, the user is authenticated. […] When no authorization identity is provided, the server derives an authorization identity from the prepared representation of the provided authentication identity string. This ensures that the derivation of different representations of the authentication identity produces the same authorization identity.” -- <https://tools.ietf.org/html/rfc4616#section-2>	.
testPlainNonAscii	.
testScramSha256Failure	s
testScramSha256Success	s
irctest.server_tests.setname.SetnameMessageTestCase
	sable
testSetnameChannel “[Servers] MUST send the server-to-client version of the SETNAME message to all clients in common channels, as well as to the client from which it originated, to confirm the change has occurred. The SETNAME message MUST NOT be sent to clients which do not have the setname capability negotiated.“	s
testSetnameMessage	s
irctest.server_tests.statusmsg.StatusmsgTestCase
	sable
testStatusmsgFromOp Test that STATUSMSG are sent to the intended recipients, with the intended prefixes.	s
testStatusmsgFromRegular Test that STATUSMSG are sent to the intended recipients, with the intended prefixes.	s
irctest.server_tests.topic.TopicPrivilegesTestCase
	sable
testTopicPrivileges	.
irctest.server_tests.topic.TopicTestCase
	sable
testTopicMode “Once a user has joined a channel, he receives information about all commands his server receives affecting the channel. This includes […] TOPIC” -- <https://tools.ietf.org/html/rfc1459#section-4.2.1> and <https://tools.ietf.org/html/rfc2812#section-3.2.1>	.
testTopicModern "If the topic of a channel is changed or cleared, every client in that channel (including the author of the topic change) will receive a TOPIC command with the new topic as argument (or an empty argument if the topic was cleared) alerting them to how the topic has changed. Clients joining the channel in the future will receive a RPL_TOPIC numeric (or lack thereof) accordingly." -- https://modern.ircdocs.horse/#topic-message	.
testTopicNonexistentChannel RFC2812 specifies ERR_NOTONCHANNEL as the correct response to TOPIC on a nonexistent channel. The modern spec prefers ERR_NOSUCHCHANNEL. <https://tools.ietf.org/html/rfc2812#section-3.2.4> <http://modern.ircdocs.horse/#topic-message>	.
testTopicRfc “Once a user has joined a channel, he receives information about all commands his server receives affecting the channel. This includes […] TOPIC” -- <https://tools.ietf.org/html/rfc1459#section-4.2.1> and <https://tools.ietf.org/html/rfc2812#section-3.2.1>	.
testUnsetTopicResponses Test various cases related to RPL_NOTOPIC with set and unset topics.	.
irctest.server_tests.utf8.Utf8TestCase
	sable
testNonutf8Realname	.
testNonutf8Username	.
testUtf8Validation	.
irctest.server_tests.wallops.WallopsTestCase
	sable
testWallops "The WALLOPS command is used to send a message to all currently connected users who have set the 'w' user mode for themselves." -- https://datatracker.ietf.org/doc/html/rfc2812#section-4.7 -- https://github.com/ircdocs/modern-irc/pull/118 "Servers MAY echo WALLOPS messages to their sender even if they don't have the 'w' user mode. Servers MAY send WALLOPS only to operators." -- https://github.com/ircdocs/modern-irc/pull/118	s
testWallopsPrivileges https://github.com/ircdocs/modern-irc/pull/118	s
irctest.server_tests.who.WhoInvisibleTestCase
	sable
testWhoInvisible	.
irctest.server_tests.who.WhoServicesTestCase
	sable
testWhoxAccount	s
testWhoxNoAccount	s
irctest.server_tests.who.WhoTestCase
	sable
testWhoChan[casefolded]	.
testWhoChan[exact]	.
testWhoMultiChan When WHO <#chan> is sent, the second parameter of RPL_WHOREPLY must be #chan. See discussion on Modern: <https://github.com/ircdocs/modern-irc/issues/209>	.
testWhoNickAwayAndOper[casefolded]	X
testWhoNickAwayAndOper[exact]	X
testWhoNickAwayAndOper[mask]	X
testWhoNickAway[casefolded]	.
testWhoNickAway[exact]	.
testWhoNickAway[mask]	.
testWhoNickNotExists When WHO is sent with a non-existing nickname, the server must reply with a single RPL_ENDOFWHO. See: <https://github.com/ircdocs/modern-irc/pull/216>	.
testWhoNickOper[casefolded]	X
testWhoNickOper[exact]	X
testWhoNickOper[mask]	X
testWhoNick[casefolded]	.
testWhoNick[exact]	.
testWhoNick[mask]	.
testWhoRealNameSpaces	s
testWhoStar	.
testWhoUsernameRealName[hostname]	s
testWhoUsernameRealName[realname-mask]	s
testWhoUsernameRealName[username]	s
testWhoxFull https://github.com/ircv3/ircv3-specifications/pull/482	s
testWhoxFullReversed https://github.com/ircv3/ircv3-specifications/pull/482	s
testWhoxOneChar[a]	s
testWhoxOneChar[c]	s
testWhoxOneChar[d]	s
testWhoxOneChar[f]	s
testWhoxOneChar[h]	s
testWhoxOneChar[i]	s
testWhoxOneChar[l]	s
testWhoxOneChar[n]	s
testWhoxOneChar[o]	s
testWhoxOneChar[r]	s
testWhoxOneChar[s]	s
testWhoxOneChar[u]	s
testWhoxToken https://github.com/ircv3/ircv3-specifications/pull/482	s
irctest.server_tests.whois.ServicesWhoisTestCase
	sable
testWhoisAccount Test numeric 330, RPL_WHOISACCOUNT. <https://defs.ircdocs.horse/defs/numerics.html#rpl-whoisaccount-330>	.
testWhoisNumerics[normal] Tests all numerics are in the exhaustive list defined in the Modern spec, on an authenticated user. <https://modern.ircdocs.horse/#whois-message>	.
testWhoisNumerics[oper] Tests all numerics are in the exhaustive list defined in the Modern spec, on an authenticated user. <https://modern.ircdocs.horse/#whois-message>	.
irctest.server_tests.whois.WhoisTestCase
	sable
testWhoisMissingUser Test WHOIS on a nonexistent nickname.	X
testWhoisNumerics[away] Tests all numerics are in the exhaustive list defined in the Modern spec. <https://modern.ircdocs.horse/#whois-message>	.
testWhoisNumerics[normal] Tests all numerics are in the exhaustive list defined in the Modern spec. <https://modern.ircdocs.horse/#whois-message>	.
testWhoisNumerics[oper] Tests all numerics are in the exhaustive list defined in the Modern spec. <https://modern.ircdocs.horse/#whois-message>	.
testWhoisUser[no-target] Test basic WHOIS behavior	.
testWhoisUser[target-nick] Test basic WHOIS behavior	.
testWhoisUser[target_server] Test basic WHOIS behavior	.
irctest.server_tests.whowas.WhowasTestCase
	sable
testWhowasCount1 "If there are multiple entries, up to <count> replies will be returned" -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasCount2 "If there are multiple entries, up to <count> replies will be returned" -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasCountNegative "If a non-positive number is passed as being <count>, then a full search is done." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 "If given, <count> SHOULD be a positive number. Otherwise, a full search "is done. -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasCountZero "If a non-positive number is passed as being <count>, then a full search is done." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 "If given, <count> SHOULD be a positive number. Otherwise, a full search "is done. -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasEnd "At the end of all reply batches, there must be RPL_ENDOFWHOWAS" -- https://datatracker.ietf.org/doc/html/rfc1459#page-50 -- https://datatracker.ietf.org/doc/html/rfc2812#page-45 "Servers MUST reply with either ERR_WASNOSUCHNICK or [...], both followed with RPL_ENDOFWHOWAS" -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasMultiTarget[nick2,nick3] https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3	s
testWhowasMultiTarget[nick3,nick2] https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3	s
testWhowasMultiple "The history is searched backward, returning the most recent entry first." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasNoParamModern "If the <nick> argument is missing, they SHOULD send a single reply, using either ERR_NONICKNAMEGIVEN or ERR_NEEDMOREPARAMS" -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasNoSuchNick https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message and: "At the end of all reply batches, there must be RPL_ENDOFWHOWAS (even if there was only one reply and it was an error)." -- https://datatracker.ietf.org/doc/html/rfc1459#page-50 -- https://datatracker.ietf.org/doc/html/rfc2812#page-45 and: "Servers MUST reply with either ERR_WASNOSUCHNICK or [...], both followed with RPL_ENDOFWHOWAS" -- https://modern.ircdocs.horse/#whowas-message	.
testWhowasNumerics https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3	.

irctest.self_tests.cases.IrcTestCaseTestCase

sable

test_message_matching_negative[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ... 123]

test_message_matching_negative[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ... :]

test_message_matching_negative[{'command': 'PING', 'params': ['abc']}-PONG def]

test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello2]

test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan2 hello]

test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan :hi]

test_message_matching_negative[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan2 hello]

test_message_matching_negative[{'nick': 'foo', 'command': 'PRIVMSG'}-:foo2!baz@qux PRIVMSG #chan hello]

test_message_matching_negative[{'nick': 'foo', 'command': 'PRIVMSG'}-@tag1=bar :foo2!baz@qux PRIVMSG #chan :hello]

test_message_matching_negative[{'nick': 'foo', 'command': 'PRIVMSG'}-PRIVMSG #chan :hi]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello2]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan2 hello]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2=baz PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]

test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello]

test_message_matching_negative[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-:foo!baz@qux PRIVMSG #chan hello]

test_message_matching_negative[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=bar;tag2= PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-PRIVMSG #chan hello]

test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]

test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=value1 PRIVMSG #chan :hello]

test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMG #chan :hello]

test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello2]

test_message_matching_negative[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan2 hello]

test_message_matching_negative_message[expected command to match PING, got PONG]

test_message_matching_negative_message[expected command to match PRIVMSG, got PRIVMG0]

test_message_matching_negative_message[expected command to match PRIVMSG, got PRIVMG1]

test_message_matching_negative_message[expected command to match PRIVMSG, got PRIVMG2]

test_message_matching_negative_message[expected nick to be foo, got None instead]

test_message_matching_negative_message[expected nick to be foo, got foo2 instead0]

test_message_matching_negative_message[expected nick to be foo, got foo2 instead1]

test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan', 'hello2']0]

test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan', 'hello2']1]

test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan', 'hello2']2]

test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan2', 'hello']0]

test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan2', 'hello']1]

test_message_matching_negative_message[expected params to match ['#chan', 'hello'], got ['#chan2', 'hello']2]

test_message_matching_negative_message[expected params to match ['#chan', StrRe(r'hello.*')], got ['#chan', 'hi']]

test_message_matching_negative_message[expected params to match ['#chan', StrRe(r'hello.*')], got ['#chan2', 'hello']]

test_message_matching_negative_message[expected params to match ['nick', '...', OptStrRe(r'[a-zA-Z]+')], got ['nick', '...', '']]

test_message_matching_negative_message[expected params to match ['nick', '...', OptStrRe(r'[a-zA-Z]+')], got ['nick', '...', '123']]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {'tag1': 'value1'}]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {}]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, got {'tag1': 'bar', 'tag2': ''}]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, got {'tag1': 'bar', 'tag2': 'baz'}]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, got {'tag1': 'value1'}]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {'tag1': 'bar', 'tag2': ''}]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {'tag1': 'value1'}]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {}0]

test_message_matching_negative_message[expected tags to match {'tag1': 'bar'}, got {}1]

test_message_matching_negative_message[expected tags to match {'tag1': ANYSTR}, got {'tag1': 'bar', 'tag2': ''}]

test_message_matching_negative_message[expected tags to match {'tag1': ANYSTR}, got {}0]

test_message_matching_negative_message[expected tags to match {'tag1': ANYSTR}, got {}1]

test_message_matching_negative_message[expected tags to match {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {'tag1': 'value1'}]

test_message_matching_negative_message[expected tags to match {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, got {}]

test_message_matching_positive[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ... abc]

test_message_matching_positive[{'command': '004', 'params': ['nick', '...', OptStrRe(r'[a-zA-Z]+')]}-004 nick ...]

test_message_matching_positive[{'command': 'PING', 'params': ['abc']}-PING abc]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-:foo!baz@qux PRIVMSG #chan hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-PRIVMSG #chan hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-:foo!baz@qux PRIVMSG #chan hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-@tag1=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-@tag1=bar;tag2= PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan :hello]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan hello2]

test_message_matching_positive[{'command': 'PRIVMSG', 'params': ['#chan', StrRe(r'hello.*')]}-PRIVMSG #chan hello]

test_message_matching_positive[{'nick': 'foo', 'command': 'PRIVMSG'}-:foo!baz@qux PRIVMSG #chan hello]

test_message_matching_positive[{'nick': 'foo', 'command': 'PRIVMSG'}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar', RemainingKeys(NotStrRe(r'tag2')): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag3= PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': 'bar'}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {'tag1': ANYSTR}, 'command': 'PRIVMSG', 'params': ['#chan', ANYSTR]}-@tag1=value1 PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=;tag2=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar :foo!baz@qux PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar PRIVMSG #chan :hello]

test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello0]

test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag1=bar;tag2= PRIVMSG #chan :hello1]

test_message_matching_positive[{'tags': {StrRe(r'tag[12]'): 'bar', RemainingKeys(ANYSTR): ANYOPTSTR}, 'command': 'PRIVMSG', 'params': ['#chan', 'hello']}-@tag2=bar PRIVMSG #chan :hello]

irctest.server_tests.account_registration.RegisterBeforeConnectDisallowedTestCase

sable

testBeforeConnect

irctest.server_tests.account_registration.RegisterBeforeConnectTestCase

sable

testBeforeConnect

irctest.server_tests.account_registration.RegisterEmailVerifiedAfterConnectTestCase

sable

testAfterConnect

irctest.server_tests.account_registration.RegisterEmailVerifiedBeforeConnectTestCase

sable

testBeforeConnect

irctest.server_tests.account_registration.RegisterTestCase

sable

testRegisterDefaultName

"If <account> is *, then this value is the user’s current nickname."

System Message: WARNING/2 (<string>, line 2); backlink

Inline emphasis start-string without end-string.

testRegisterDifferentName

Requested account name differs from the nick

testRegisterSameName

Requested account name is the same as the nick

irctest.server_tests.account_tag.AccountTagTestCase

sable

testInvite

testPrivmsg

irctest.server_tests.away.AwayTestCase

sable

testAway

testAwayAck

"The server acknowledges the change in away status by returning the RPL_NOWAWAY and RPL_UNAWAY numerics." -- https://modern.ircdocs.horse/#away-message

testAwayEmptyMessage

"If [AWAY] is sent with a nonempty parameter (the 'away message') then the user is set to be away. If this command is sent with no parameters, or with the empty string as the parameter, the user is no longer away." -- https://modern.ircdocs.horse/#away-message

testAwayPrivmsg

"Servers SHOULD notify clients when a user they're interacting with is away when relevant" -- https://modern.ircdocs.horse/#away-message

"<client> <nick> :<message>" -- https://modern.ircdocs.horse/#rplaway-301

testAwayUserhost

"Servers SHOULD notify clients when a user they're interacting with is away when relevant" -- https://modern.ircdocs.horse/#away-message

"<client> <nick> :<message>" -- https://modern.ircdocs.horse/#rplaway-301

testAwayWhois

"Servers SHOULD notify clients when a user they're interacting with is away when relevant" -- https://modern.ircdocs.horse/#away-message

"<client> <nick> :<message>" -- https://modern.ircdocs.horse/#rplaway-301

irctest.server_tests.away_notify.AwayNotifyTestCase

sable

testAwayNotify

Basic away-notify test.

testAwayNotifyOnJoin

The away-notify specification states:: "Clients will be sent an AWAY message [...] when a user joins and has an away message set."

irctest.server_tests.bot_mode.BotModeTestCase

sable

testBotChannelMessage

testBotMode

testBotPrivateMessage

testBotWhois

testBotWhox

irctest.server_tests.buffering.BufferingTestCase

sable

testNoTags[byteperbyte-colon]

testNoTags[byteperbyte-no colon]

testNoTags[charperchar-colon]

testNoTags[charperchar-no colon]

testNoTags[whole-colon]

testNoTags[whole-no colon]

irctest.server_tests.cap.CapTestCase

sable

testCapRemovalByClient

Test CAP LIST and removal of caps via CAP REQ :-tagname.

testInvalidCapSubcommand

“If no capabilities are active, an empty parameter must be sent.”: -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-list-subcommand>

testIrc301CapLs

Current version:

"The LS subcommand is used to list the capabilities supported by the server. The client should send an LS subcommand with no other arguments to solicit a list of all capabilities."

"If a client has not indicated support for CAP LS 302 features, the server MUST NOT send these new features to the client." -- <https://ircv3.net/specs/core/capability-negotiation.html>

Before the v3.1 / v3.2 merge:

IRCv3.1: “The LS subcommand is used to list the capabilities supported by the server. The client should send an LS subcommand with no other arguments to solicit a list of all capabilities.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-ls-subcommand>

IRCv3.2: “Servers MUST NOT send messages described by this document if the client only supports version 3.1.” -- <http://ircv3.net/specs/core/capability-negotiation-3.2.html#version-in-cap-ls>

testNakExactString

“The argument of the NAK subcommand MUST consist of at least the: first 100 characters of the capability list in the REQ subcommand which triggered the NAK.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-nak-subcommand>

testNakWhole

“The capability identifier set must be accepted as a whole, or: rejected entirely.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-req-subcommand>

testNoMultiline301Response

Current version: "If the client supports CAP version 302, the server MAY send multiple lines in response to CAP LS and CAP LIST." This should be read as disallowing multiline responses to pre-302 clients. -- <https://ircv3.net/specs/extensions/capability-negotiation#multiline-replies-to-cap-ls-and-cap-list>

testNoReq

Test the server handles gracefully clients which do not send

REQs.

“Clients that support capabilities but do not wish to enter negotiation SHOULD send CAP END upon connection to the server.” -- <http://ircv3.net/specs/core/capability-negotiation-3.1.html#the-cap-end-subcommand>

testReqOne

Tests requesting a single capability

testReqOneThenOne

Tests requesting two capabilities in different messages

testReqPostRegistration

Tests requesting more capabilities after CAP END

testReqTwo

Tests requesting two capabilities at once

testReqUnavailable

Test the server handles gracefully clients which request: capabilities that are not available. <http://ircv3.net/specs/core/capability-negotiation-3.1.html>

irctest.server_tests.channel_rename.ChannelRenameTestCase

Basic tests for channel-rename.

sable

testChannelRename

irctest.server_tests.chathistory.ChathistoryTestCase

sable

testChathistoryEventPlayback[AFTER]

testChathistoryEventPlayback[AROUND]

testChathistoryEventPlayback[BEFORE]

testChathistoryEventPlayback[BETWEEN]

testChathistoryEventPlayback[LATEST]

testChathistoryNoEventPlayback

Tests that non-messages don't appear in the chat history when event-playback: is not enabled.

testChathistory[AFTER]

testChathistory[AROUND]

testChathistory[BEFORE]

testChathistory[BETWEEN]

testChathistory[LATEST]

testInvalidTargets

irctest.server_tests.chmodes.ban.BanModeTestCase

sable

testBan

Basic ban operation

testBanException

`Exception mode <https://modern.ircdocs.horse/#exception-channel-mode`_,: detected using ISUPPORT EXCEPTS and checked against ISUPPORT CHANMODES

Docutils System Messages

irctest.server_tests.chmodes.key.KeyTestCase

sable

testKeyNormal

testKeyValidation[empty]

key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F )

; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " "

System Message: WARNING/2 (<string>, line 5)

Block quote ends without a blank line; unexpected unindent.

-- https://tools.ietf.org/html/rfc2812#page-8

"Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following:

[ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696)

[ERR_INVALIDKEY](#errinvalidkey-525)

MODE echoed with a different key (eg. truncated or stripped of invalid characters)

the key changed ignored, and no MODE echoed if no other mode change was valid.

System Message: WARNING/2 (<string>, line 18)

Bullet list ends without a blank line; unexpected unindent.

" -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111

testKeyValidation[long]

key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F )

; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " "

System Message: WARNING/2 (<string>, line 5)

Block quote ends without a blank line; unexpected unindent.

-- https://tools.ietf.org/html/rfc2812#page-8

"Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following:

[ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696)

[ERR_INVALIDKEY](#errinvalidkey-525)

MODE echoed with a different key (eg. truncated or stripped of invalid characters)

the key changed ignored, and no MODE echoed if no other mode change was valid.

System Message: WARNING/2 (<string>, line 18)

Bullet list ends without a blank line; unexpected unindent.

" -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111

testKeyValidation[only-space]

key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F )

; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " "

System Message: WARNING/2 (<string>, line 5)

Block quote ends without a blank line; unexpected unindent.

-- https://tools.ietf.org/html/rfc2812#page-8

"Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following:

[ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696)

[ERR_INVALIDKEY](#errinvalidkey-525)

MODE echoed with a different key (eg. truncated or stripped of invalid characters)

the key changed ignored, and no MODE echoed if no other mode change was valid.

System Message: WARNING/2 (<string>, line 18)

Bullet list ends without a blank line; unexpected unindent.

" -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111

testKeyValidation[spaces]

key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F )

; any 7-bit US_ASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " "

System Message: WARNING/2 (<string>, line 5)

Block quote ends without a blank line; unexpected unindent.

-- https://tools.ietf.org/html/rfc2812#page-8

"Servers may validate the value (eg. to forbid spaces, as they make it harder to use the key in JOIN messages). If the value is invalid, they SHOULD return [ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696). However, clients MUST be able to handle any of the following:

[ERR_INVALIDMODEPARAM](#errinvalidmodeparam-696)

[ERR_INVALIDKEY](#errinvalidkey-525)

MODE echoed with a different key (eg. truncated or stripped of invalid characters)

the key changed ignored, and no MODE echoed if no other mode change was valid.

System Message: WARNING/2 (<string>, line 18)

Bullet list ends without a blank line; unexpected unindent.

" -- https://modern.ircdocs.horse/#key-channel-mode -- https://github.com/ircdocs/modern-irc/pull/111

irctest.server_tests.chmodes.modeis.RplChannelModeIsTestCase

sable

testChannelModeIs

Test RPL_CHANNELMODEIS and RPL_CHANNELCREATED as responses to: MODE #channel: <https://modern.ircdocs.horse/#rplcreationtime-329> <https://modern.ircdocs.horse/#rplchannelmodeis-324>

irctest.server_tests.chmodes.moderated.ModeratedModeTestCase

sable

testModeratedMode

irctest.server_tests.chmodes.mute_extban.MuteExtbanTestCase

https://defs.ircdocs.horse/defs/isupport.html#extban

It magically guesses what char the IRCd uses for mutes.

sable

testMuteExtban

Basic usage of mute

testMuteExtbanExempt

Checks +e overrides the mute

<https://defs.ircdocs.horse/defs/chanmodes.html#e-ban-exception>

testMuteExtbanVoiced

Checks +v overrides the mute

irctest.server_tests.chmodes.no_external.NoExternalMessagesTestCase

sable

testNoExternalMessagesMode

irctest.server_tests.chmodes.operator.ChannelOperatorModeTestCase

Test various error and success cases around the channel operator mode:: <https://modern.ircdocs.horse/#channel-operators> <https://modern.ircdocs.horse/#mode-message>

sable

testChannelOperatorModeChannelAndTargetDoNotExist

Test that +o targeting a nonexistent channel and nickname: fails as expected.

testChannelOperatorModeChannelDoesNotExist

Test that +o targeting a nonexistent channel fails as expected.

"If <target> is a channel that does not exist on the network, # the ERR_NOSUCHCHANNEL (403) numeric is returned."

testChannelOperatorModeSenderAndTargetNonMembers

Test that +o where neither the sender nor the target is a channel: member fails as expected.

testChannelOperatorModeSenderNonMember

Test that +o where the sender is not a channel member: fails as expected.

testChannelOperatorModeSenderPrivsNeeded

Test that +o from a channel member without the necessary privileges: fails as expected.

testChannelOperatorModeSuccess

Tests a successful grant of +o in a channel.

testChannelOperatorModeTargetDoesNotExist

Test that +o targeting a nonexistent nick fails as expected.

testChannelOperatorModeTargetNotInChannel

Test that +o targeting a user not present in the channel fails: as expected.

irctest.server_tests.connection_registration.ConnectionRegistrationTestCase

sable

testConnectionRegistration

testEarlyNickCollision

Two users register simultaneously with the same nick.

testEmptyRealname

Syntax: "<client> <command> :Not enough parameters" -- https://defs.ircdocs.horse/defs/numerics.html#err-needmoreparams-461 -- https://modern.ircdocs.horse/#errneedmoreparams-461

Use of this numeric: "The minimum length of <username> is 1, ie. it MUST not be empty. If it is empty, the server SHOULD reject the command with ERR_NEEDMOREPARAMS (even an empty parameter is provided)" https://github.com/ircdocs/modern-irc/issues/85

testNickCollision

A user connects and requests the same nickname as an already: registered user.

testNonutf8Realname

testNonutf8Username

testQuitDisconnects

“The server must close the connection to a client which sends a: QUIT message.” -- <https://tools.ietf.org/html/rfc1459#section-4.1.3>

testQuitErrors

“A client session is terminated with a quit message. The server: acknowledges this by sending an ERROR message to the client.” -- <https://tools.ietf.org/html/rfc2812#section-3.1.7>

irctest.server_tests.connection_registration.PasswordedConnectionRegistrationTestCase

sable

testNoPassword

testPassBeforeNickuser

testWrongPassword

"If the password supplied does not match the password expected by the server, then the server SHOULD send ERR_PASSWDMISMATCH and MUST close the connection with ERROR." -- https://github.com/ircdocs/modern-irc/pull/172

irctest.server_tests.echo_message.EchoMessageTestCase

sable

testEchoMessage[NOTICE-False-True]

<http://ircv3.net/specs/extensions/echo-message-3.2.html>

testEchoMessage[PRIVMSG-False-False]

<http://ircv3.net/specs/extensions/echo-message-3.2.html>

testEchoMessage[PRIVMSG-False-True]

<http://ircv3.net/specs/extensions/echo-message-3.2.html>

testEchoMessage[PRIVMSG-True-True]

<http://ircv3.net/specs/extensions/echo-message-3.2.html>

irctest.server_tests.extended_join.MetadataTestCase

sable

testLoggedIn

testNotLoggedIn

irctest.server_tests.help.HelpTestCase

sable

testHelpNoArg[HELPOP]

testHelpNoArg[HELP]

testHelpPrivmsg[HELPOP]

testHelpPrivmsg[HELP]

testHelpUnknownSubject[HELPOP]

testHelpUnknownSubject[HELP]

irctest.server_tests.invite.InviteTestCase

sable

testInviteAlreadyInChannel

"If the user is already on the target channel, the server MUST reject the command with the ERR_USERONCHANNEL numeric." -- https://modern.ircdocs.horse/#invite-message

testInviteInviteOnly

"To invite a user to a channel which is invite only (MODE +i), the client sending the invite must be recognised as being a channel operator on the given channel." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.7

"When the channel has invite-only flag set, only channel operators may issue INVITE command." -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.7

"When the channel has [invite-only](#invite-only-channel-mode) mode set, only channel operators may issue INVITE command. Otherwise, the server MUST reject the command with the ERR_CHANOPRIVSNEEDED numeric." -- https://modern.ircdocs.horse/#invite-message

testInviteNoNotificationForOtherMembers

"Other channel members are not notified." -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.7

"Other channel members SHOULD NOT be notified." -- https://modern.ircdocs.horse/#invite-message

testInviteOnlyFromUsersInChannel

"if the channel exists, only members of the channel are allowed to invite other users" -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.7

" 442 ERR_NOTONCHANNEL

"<channel> :You're not on that channel"

Returned by the server whenever a client tries to perform a channel affecting command for which the client isn't a member.

System Message: WARNING/2 (<string>, line 12)

Definition list ends without a blank line; unexpected unindent.

" -- https://datatracker.ietf.org/doc/html/rfc2812

" Only members of the channel are allowed to invite other users. Otherwise, the server MUST reject the command with the ERR_NOTONCHANNEL numeric." -- https://modern.ircdocs.horse/#invite-message

testInvite[False]

testInvite[True]

testInvites

Test some basic functionality related to INVITE and the +i mode.

https://modern.ircdocs.horse/#invite-only-channel-mode https://modern.ircdocs.horse/#rplinviting-341

irctest.server_tests.isupport.IsupportTestCase

sable

testParameters

https://modern.ircdocs.horse/#rplisupport-005

testPrefix

https://modern.ircdocs.horse/#prefix-parameter

testTargmax

"Format: TARGMAX=[<command>:[limit]{,<command>:[limit]}]" -- https://modern.ircdocs.horse/#targmax-parameter

"TARGMAX=[cmd:[number][,cmd:[number][,...]]]" -- https://defs.ircdocs.horse/defs/isupport.html#targmax

irctest.server_tests.join.JoinTestCase

sable

testJoinKey

Joins a single channel with a key

testJoinKeys

Joins two channels, both with keys

testJoinManySingleKey

Joins two channels, the first one has a key.

testJoinNamreply

“353 RPL_NAMREPLY

"( "=" / "*" / "@" ) <channel>

:[ "@" / "+" ] <nick> *( " " [ "@" / "+" ] <nick> )”

System Message: WARNING/2 (<string>, line 3); backlink

Inline emphasis start-string without end-string.

-- <https://tools.ietf.org/html/rfc2812#section-5.2>

This test makes a user join and check what is sent to them.

testJoinPartiallyInvalid

TODO: specify this in Modern

testJoinPartiallyInvalidLabeledResponse

TODO: specify this in Modern

testJoinTwice

irctest.server_tests.kick.KickTestCase

sable

testDoubleKickMessages[False]

“The server MUST NOT send KICK messages with multiple channels or

users to clients. This is necessarily to maintain backward compatibility with old client software.” -- https://tools.ietf.org/html/rfc2812#section-3.2.8

"The server MUST NOT send KICK messages with multiple channels or users to clients. This is necessary to maintain backward compatibility with existing client software." -- https://modern.ircdocs.horse/#kick-message

"Servers MAY limit the number of target users per KICK command via the [TARGMAX parameter of RPL_ISUPPORT](#targmax-parameter), and silently drop targets if the number of targets exceeds the limit." -- https://modern.ircdocs.horse/#kick-message

"If the "TARGMAX" parameter is not advertised or a value is not sent then a client SHOULD assume that no commands except the "JOIN" and "PART" commands accept multiple parameters." -- https://defs.ircdocs.horse/defs/isupport.html#targmax

"If this parameter is not advertised or a value is not sent then a client SHOULD assume that no commands except the JOIN and PART commands accept multiple parameters." -- https://github.com/ircdocs/modern-irc/pull/113

"If <limit> is not specified, then there is no maximum number of targets for that command." -- https://modern.ircdocs.horse/#targmax-parameter

testDoubleKickMessages[True]

“The server MUST NOT send KICK messages with multiple channels or

users to clients. This is necessarily to maintain backward compatibility with old client software.” -- https://tools.ietf.org/html/rfc2812#section-3.2.8

"If <limit> is not specified, then there is no maximum number of targets for that command." -- https://modern.ircdocs.horse/#targmax-parameter

testKickDefaultComment

"If a "comment" is given, this will be sent instead of the default message, the nickname of the user issuing the KICK." -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.8

testKickNoComment

"If no comment is given, the server SHOULD use a default message instead." -- https://modern.ircdocs.horse/#kick-message

testKickNonexistentChannel

“Kick command [...] Numeric replies: [...] ERR_NOSUCHCHANNEL.

testKickPrivileges

Test who has the ability to kick / what error codes are sent: for invalid kicks.

testKickSendsMessages

“Once a user has joined a channel, he receives information about

all commands his server receives affecting the channel. This includes […] KICK” -- <https://tools.ietf.org/html/rfc1459#section-4.2.1> and <https://tools.ietf.org/html/rfc2812#section-3.2.1>

"If a comment is given, this will be sent instead of the default message, the nickname of the user targeted by the KICK." -- https://modern.ircdocs.horse/#kick-message

irctest.server_tests.labeled_responses.LabeledResponsesTestCase

sable

testEmptyBatchForNoResponse

testLabeledNoticeResponsesToClient

testLabeledNoticeResponsesToSelf

testLabeledPrivmsgResponsesToClient

testLabeledPrivmsgResponsesToMultipleClients

testLabeledPrivmsgResponsesToSelf

testNoBatchForSingleMessage

testUnknownCommand

irctest.server_tests.links.LinksTestCase

sable

testLinksSingleServer

Only testing the parameter-less case.

https://datatracker.ietf.org/doc/html/rfc1459#section-4.3.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.4.5 https://github.com/ircdocs/modern-irc/pull/175

" 364 RPL_LINKS

System Message: ERROR/3 (<string>, line 10)

Unexpected indentation.

"<mask> <server> :<hopcount> <server info>"

System Message: WARNING/2 (<string>, line 11)

Block quote ends without a blank line; unexpected unindent.

365 RPL_ENDOFLINKS

"<mask> :End of /LINKS list"

In replying to the LINKS message, a server must send replies back using the RPL_LINKS numeric and mark the end of the list using an RPL_ENDOFLINKS reply.

System Message: WARNING/2 (<string>, line 17)

Definition list ends without a blank line; unexpected unindent.

" -- https://datatracker.ietf.org/doc/html/rfc1459#page-51 -- https://datatracker.ietf.org/doc/html/rfc2812#page-48

RPL_LINKS: "<client> * <server> :<hopcount> <server info>" RPL_ENDOFLINKS: "<client> * :End of /LINKS list" -- https://github.com/ircdocs/modern-irc/pull/175/files

irctest.server_tests.links.ServicesLinksTestCase

sable

testLinksWithServices

Only testing the parameter-less case.

https://datatracker.ietf.org/doc/html/rfc1459#section-4.3.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.4.5

" 364 RPL_LINKS

System Message: ERROR/3 (<string>, line 9)

Unexpected indentation.

"<mask> <server> :<hopcount> <server info>"

System Message: WARNING/2 (<string>, line 10)

Block quote ends without a blank line; unexpected unindent.

365 RPL_ENDOFLINKS

"<mask> :End of /LINKS list"

In replying to the LINKS message, a server must send replies back using the RPL_LINKS numeric and mark the end of the list using an RPL_ENDOFLINKS reply.

System Message: WARNING/2 (<string>, line 16)

Definition list ends without a blank line; unexpected unindent.

" -- https://datatracker.ietf.org/doc/html/rfc1459#page-51 -- https://datatracker.ietf.org/doc/html/rfc2812#page-48

RPL_LINKS: "<client> * <server> :<hopcount> <server info>" RPL_ENDOFLINKS: "<client> * :End of /LINKS list" -- https://github.com/ircdocs/modern-irc/pull/175/files

irctest.server_tests.messages.NoticeTestCase

sable

testNotice

<https://tools.ietf.org/html/rfc2812#section-3.3.2>

testNoticeNonexistentChannel

"automatic replies must never be sent in response to a NOTICE message. This rule applies to servers too - they must not send any error reply back to the client on receipt of a notice" <https://tools.ietf.org/html/rfc1459#section-4.4.2>

'automatic replies MUST NEVER be sent in response to a NOTICE message. This rule applies to servers too - they MUST NOT send any error repl back to the client on receipt of a notice." <https://tools.ietf.org/html/rfc2812#section-3.3.2>

irctest.server_tests.messages.PrivmsgTestCase

sable

testEmptyPrivmsg

testPrivmsg

<https://tools.ietf.org/html/rfc2812#section-3.3.1>

testPrivmsgNonexistentChannel

<https://tools.ietf.org/html/rfc2812#section-3.3.1>

testPrivmsgNonexistentUser

<https://tools.ietf.org/html/rfc2812#section-3.3.1>

testPrivmsgToUser

<https://tools.ietf.org/html/rfc2812#section-3.3.1>

irctest.server_tests.messages.TagsTestCase

sable

testLineTooLong

irctest.server_tests.monitor.AuthenticatedExtendedMonitorTestCase

sable

testExtendedMonitorAccountNotifyNoCap[-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

testExtendedMonitorAccountNotifyNoCap[-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

testExtendedMonitorAccountNotifyNoCap[monitor_before_connect-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

testExtendedMonitorAccountNotifyNoCap[monitor_before_connect-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

testExtendedMonitorAccountNotify[-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

testExtendedMonitorAccountNotify[-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

testExtendedMonitorAccountNotify[monitor_before_connect-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

testExtendedMonitorAccountNotify[monitor_before_connect-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when account-notify is not enabled by the watcher

irctest.server_tests.monitor.ExtendedMonitorTestCase

sable

testExtendedMonitorAwayNoCap[-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when away-notify is not enabled by the watcher

testExtendedMonitorAwayNoCap[-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when away-notify is not enabled by the watcher

testExtendedMonitorAwayNoCap[monitor_before_connect-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when away-notify is not enabled by the watcher

testExtendedMonitorAwayNoCap[monitor_before_connect-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when away-notify is not enabled by the watcher

testExtendedMonitorAway[-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: with https://ircv3.net/specs/extensions/away-notify

testExtendedMonitorAway[-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: with https://ircv3.net/specs/extensions/away-notify

testExtendedMonitorAway[monitor_before_connect-]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: with https://ircv3.net/specs/extensions/away-notify

testExtendedMonitorAway[monitor_before_connect-with-cap]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: with https://ircv3.net/specs/extensions/away-notify

testExtendedMonitorSetNameNoCap[False]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when setname is not enabled by the watcher

testExtendedMonitorSetNameNoCap[True]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: does nothing when setname is not enabled by the watcher

testExtendedMonitorSetName[False]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: with https://ircv3.net/specs/extensions/setname

testExtendedMonitorSetName[True]

Tests https://ircv3.net/specs/extensions/extended-monitor.html: with https://ircv3.net/specs/extensions/setname

irctest.server_tests.monitor.MonitorTestCase

sable

testMonitorClear

“Clears the list of targets being monitored. No output will be returned: for use of this command.“ -- <https://ircv3.net/specs/extensions/monitor#monitor-c>

testMonitorConnectedAndDisconnected

“If any of the targets being added are online, the server will

generate RPL_MONONLINE numerics listing those targets that are online.

If any of the targets being added are offline, the server will generate RPL_MONOFFLINE numerics listing those targets that are online.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor--targettarget2>

testMonitorForbidsMasks

“The MONITOR implementation also enhances user privacy by

disallowing subscription to hostmasks, allowing users to avoid nick-change stalking.” -- <http://ircv3.net/specs/core/monitor-3.2.html#watch-vs-monitor>

“For this specification, ‘target’ MUST be a valid nick as determined by the IRC daemon.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor-command>

testMonitorOneConnected

“If any of the targets being added are offline, the server will: generate RPL_MONOFFLINE numerics listing those targets that are online.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor--targettarget2>

testMonitorOneConnection

testMonitorOneConnectionWithQuit

testMonitorOneDisconnected

“If any of the targets being added are online, the server will: generate RPL_MONONLINE numerics listing those targets that are online.” -- <http://ircv3.net/specs/core/monitor-3.2.html#monitor--targettarget2>

testMonitorStatus

“Outputs for each target in the list being monitored, whether: the client is online or offline. All targets that are online will be sent using RPL_MONONLINE, all targets that are offline will be sent using RPL_MONOFFLINE.“ -- <https://ircv3.net/specs/extensions/monitor#monitor-s>

testNickChange

testTwoMonitoringOneRemove

Tests the following scenario:

foo MONITORs qux
bar MONITORs qux
bar unMONITORs qux
qux connects.

testUnmonitor

irctest.server_tests.multi_prefix.MultiPrefixTestCase

sable

testMultiPrefix

“When requested, the multi-prefix client capability will cause the

IRC server to send all possible prefixes which apply to a user in NAMES and WHO output.

These prefixes MUST be in order of ‘rank’, from highest to lowest.

testNoMultiPrefix

When not requested, only the highest prefix should be sent

irctest.server_tests.multiline.MultilineTestCase

sable

testBasic

testBlankLines

testInvalidBatchTag

Test that an unexpected change of batch tag results in: FAIL BATCH MULTILINE_INVALID.

testInvalidBlankConcatTag

Test that the concat tag on a blank message results in: FAIL BATCH MULTILINE_INVALID.

irctest.server_tests.names.NamesTestCase

sable

testNames2812

https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5

testNames2812Secret

The symbol sent for a secret channel is @ instead of =:: https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5 https://modern.ircdocs.horse/#rplnamreply-353

testNamesInvalidChannel

"There is no error reply for bad channel names." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.5 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5

"If the channel name is invalid or the channel does not exist, one RPL_ENDOFNAMES numeric containing the given channel name should be returned." -- https://modern.ircdocs.horse/#names-message

testNamesModern

https://modern.ircdocs.horse/#names-message

testNamesMultipleChannels2812

https://modern.ircdocs.horse/#names-message https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.5 https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5

testNamesNonexistingChannel

"There is no error reply for bad channel names." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.2.5 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.5

"If the channel name is invalid or the channel does not exist, one RPL_ENDOFNAMES numeric containing the given channel name should be returned." -- https://modern.ircdocs.horse/#names-message

irctest.server_tests.part.PartTestCase

sable

testBasicPart

testBasicPartRfc2812

“If a "Part Message" is given, this will be sent instead of the default message, the nickname.”

testPartMessage

“If a "Part Message" is given, this will be sent instead of the default message, the nickname.”

testPartNotInEmptyChannel

“442 ERR_NOTONCHANNEL

"<channel> :You're not on that channel"

Returned by the server whenever a client tries to perform a channel effecting command for which the client isn't a member.” -- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2>

According to RFCs, ERR_NOSUCHCHANNEL should only be used for invalid channel names: “403 ERR_NOSUCHCHANNEL

"<channel name> :No such channel"

Used to indicate the given channel name is invalid.”

-- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2>

However, many implementations use 479 instead, so let's allow it. <http://danieloaks.net/irc-defs/defs/ircnumerics.html#403> <http://danieloaks.net/irc-defs/defs/ircnumerics.html#479>

testPartNotInNonEmptyChannel

“442 ERR_NOTONCHANNEL

"<channel> :You're not on that channel"

Returned by the server whenever a client tries to perform a channel effecting command for which the client isn't a member.” -- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2>

According to RFCs, ERR_NOSUCHCHANNEL should only be used for invalid channel names: “403 ERR_NOSUCHCHANNEL

"<channel name> :No such channel"

Used to indicate the given channel name is invalid.”

-- <https://tools.ietf.org/html/rfc1459#section-6.1> and <https://tools.ietf.org/html/rfc2812#section-5.2>

However, many implementations use 479 instead, so let's allow it. <http://danieloaks.net/irc-defs/defs/ircnumerics.html#403> <http://danieloaks.net/irc-defs/defs/ircnumerics.html#479>

irctest.server_tests.pingpong.PingPongTestCase

sable

testPing

https://github.com/ircdocs/modern-irc/pull/99

testPingEmptyToken

https://github.com/ircdocs/modern-irc/pull/99

testPingNoToken

https://github.com/ircdocs/modern-irc/pull/99

irctest.server_tests.quit.ChannelQuitTestCase

sable

testQuit

“Once a user has joined a channel, he receives information about: all commands his server receives affecting the channel. This includes [...] QUIT” <https://tools.ietf.org/html/rfc2812#section-3.2.1>

irctest.server_tests.regressions.RegressionsTestCase

sable

InspIRCd up to 3.16.1 used the new nick as source of NICK changes

https://github.com/inspircd/inspircd/issues/2067

https://github.com/inspircd/inspircd/commit/83f01b36a11734fd91a4e7aad99c15463858fe4a

testNickRelease

testNickReleaseQuit

testStarNick

irctest.server_tests.sasl.RegistrationTestCase

sable

testRegistration

irctest.server_tests.sasl.SaslTestCase

sable

testMechanismNotAvailable

“If authentication fails, a 904 or 905 numeric will be sent”: -- <http://ircv3.net/specs/extensions/sasl-3.1.html#the-authenticate-command>

testPlain

PLAIN authentication with correct username/password.

testPlainFailure

PLAIN authentication with incorrect username/password.

testPlainLarge

Test the client splits large AUTHENTICATE messages whose payload: is not a multiple of 400. <http://ircv3.net/specs/extensions/sasl-3.1.html#the-authenticate-command>

testPlainLargeEquals400

Test the client splits large AUTHENTICATE messages whose payload: is not a multiple of 400. <http://ircv3.net/specs/extensions/sasl-3.1.html#the-authenticate-command>

testPlainNoAuthzid

“message = [authzid] UTF8NUL authcid UTF8NUL passwd

[…]

Upon receipt of the message, the server will verify the presented (in the message) authentication identity (authcid) and password (passwd) with the system authentication database, and it will verify that the authentication credentials permit the client to act as the (presented or derived) authorization identity (authzid). If both steps succeed, the user is authenticated.

[…]

When no authorization identity is provided, the server derives an authorization identity from the prepared representation of the provided authentication identity string. This ensures that the derivation of different representations of the authentication identity produces the same authorization identity.” -- <https://tools.ietf.org/html/rfc4616#section-2>

testPlainNonAscii

testScramSha256Failure

testScramSha256Success

irctest.server_tests.setname.SetnameMessageTestCase

sable

testSetnameChannel

“[Servers] MUST send the server-to-client version of the

SETNAME message to all clients in common channels, as well as to the client from which it originated, to confirm the change has occurred.

The SETNAME message MUST NOT be sent to clients which do not have the setname capability negotiated.“

testSetnameMessage

irctest.server_tests.statusmsg.StatusmsgTestCase

sable

testStatusmsgFromOp

Test that STATUSMSG are sent to the intended recipients,: with the intended prefixes.

testStatusmsgFromRegular

Test that STATUSMSG are sent to the intended recipients,: with the intended prefixes.

irctest.server_tests.topic.TopicPrivilegesTestCase

sable

testTopicPrivileges

irctest.server_tests.topic.TopicTestCase

sable

testTopicMode

“Once a user has joined a channel, he receives information about: all commands his server receives affecting the channel. This includes […] TOPIC” -- <https://tools.ietf.org/html/rfc1459#section-4.2.1> and <https://tools.ietf.org/html/rfc2812#section-3.2.1>

testTopicModern

"If the topic of a channel is changed or cleared, every client in that

channel (including the author of the topic change) will receive a TOPIC command with the new topic as argument (or an empty argument if the topic was cleared) alerting them to how the topic has changed.

Clients joining the channel in the future will receive a RPL_TOPIC numeric (or lack thereof) accordingly." -- https://modern.ircdocs.horse/#topic-message

testTopicNonexistentChannel

RFC2812 specifies ERR_NOTONCHANNEL as the correct response to TOPIC

on a nonexistent channel. The modern spec prefers ERR_NOSUCHCHANNEL.

<https://tools.ietf.org/html/rfc2812#section-3.2.4> <http://modern.ircdocs.horse/#topic-message>

testTopicRfc

“Once a user has joined a channel, he receives information about: all commands his server receives affecting the channel. This includes […] TOPIC” -- <https://tools.ietf.org/html/rfc1459#section-4.2.1> and <https://tools.ietf.org/html/rfc2812#section-3.2.1>

testUnsetTopicResponses

Test various cases related to RPL_NOTOPIC with set and unset topics.

irctest.server_tests.utf8.Utf8TestCase

sable

testNonutf8Realname

testNonutf8Username

testUtf8Validation

irctest.server_tests.wallops.WallopsTestCase

sable

testWallops

"The WALLOPS command is used to send a message to all currently connected users who have set the 'w' user mode for themselves." -- https://datatracker.ietf.org/doc/html/rfc2812#section-4.7 -- https://github.com/ircdocs/modern-irc/pull/118

"Servers MAY echo WALLOPS messages to their sender even if they don't have the 'w' user mode. Servers MAY send WALLOPS only to operators." -- https://github.com/ircdocs/modern-irc/pull/118

testWallopsPrivileges

https://github.com/ircdocs/modern-irc/pull/118

irctest.server_tests.who.WhoInvisibleTestCase

sable

testWhoInvisible

irctest.server_tests.who.WhoServicesTestCase

sable

testWhoxAccount

testWhoxNoAccount

irctest.server_tests.who.WhoTestCase

sable

testWhoChan[casefolded]

testWhoChan[exact]

testWhoMultiChan

When WHO <#chan> is sent, the second parameter of RPL_WHOREPLY must be #chan. See discussion on Modern: <https://github.com/ircdocs/modern-irc/issues/209>

testWhoNickAwayAndOper[casefolded]

testWhoNickAwayAndOper[exact]

testWhoNickAwayAndOper[mask]

testWhoNickAway[casefolded]

testWhoNickAway[exact]

testWhoNickAway[mask]

testWhoNickNotExists

When WHO is sent with a non-existing nickname, the server must reply with a single RPL_ENDOFWHO. See: <https://github.com/ircdocs/modern-irc/pull/216>

testWhoNickOper[casefolded]

testWhoNickOper[exact]

testWhoNickOper[mask]

testWhoNick[casefolded]

testWhoNick[exact]

testWhoNick[mask]

testWhoRealNameSpaces

testWhoStar

testWhoUsernameRealName[hostname]

testWhoUsernameRealName[realname-mask]

testWhoUsernameRealName[username]

testWhoxFull

https://github.com/ircv3/ircv3-specifications/pull/482

testWhoxFullReversed

https://github.com/ircv3/ircv3-specifications/pull/482

https://github.com/ircv3/ircv3-specifications/pull/482

irctest.server_tests.whois.ServicesWhoisTestCase

sable

testWhoisAccount

Test numeric 330, RPL_WHOISACCOUNT.

<https://defs.ircdocs.horse/defs/numerics.html#rpl-whoisaccount-330>

testWhoisNumerics[normal]

Tests all numerics are in the exhaustive list defined in the Modern spec,

on an authenticated user.

<https://modern.ircdocs.horse/#whois-message>

testWhoisNumerics[oper]

Tests all numerics are in the exhaustive list defined in the Modern spec,

on an authenticated user.

<https://modern.ircdocs.horse/#whois-message>

irctest.server_tests.whois.WhoisTestCase

sable

testWhoisMissingUser

Test WHOIS on a nonexistent nickname.

testWhoisNumerics[away]

Tests all numerics are in the exhaustive list defined in the Modern spec.

<https://modern.ircdocs.horse/#whois-message>

testWhoisNumerics[normal]

Tests all numerics are in the exhaustive list defined in the Modern spec.

<https://modern.ircdocs.horse/#whois-message>

testWhoisNumerics[oper]

Tests all numerics are in the exhaustive list defined in the Modern spec.

<https://modern.ircdocs.horse/#whois-message>

testWhoisUser[no-target]

Test basic WHOIS behavior

testWhoisUser[target-nick]

Test basic WHOIS behavior

testWhoisUser[target_server]

Test basic WHOIS behavior

irctest.server_tests.whowas.WhowasTestCase

sable

testWhowasCount1

"If there are multiple entries, up to <count> replies will be returned" -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message

testWhowasCount2

"If there are multiple entries, up to <count> replies will be returned" -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message

testWhowasCountNegative

"If a non-positive number is passed as being <count>, then a full search is done." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3

"If given, <count> SHOULD be a positive number. Otherwise, a full search "is done. -- https://modern.ircdocs.horse/#whowas-message

testWhowasCountZero

"If a non-positive number is passed as being <count>, then a full search is done." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3

"If given, <count> SHOULD be a positive number. Otherwise, a full search "is done. -- https://modern.ircdocs.horse/#whowas-message

testWhowasEnd

"At the end of all reply batches, there must be RPL_ENDOFWHOWAS" -- https://datatracker.ietf.org/doc/html/rfc1459#page-50 -- https://datatracker.ietf.org/doc/html/rfc2812#page-45

"Servers MUST reply with either ERR_WASNOSUCHNICK or [...], both followed with RPL_ENDOFWHOWAS" -- https://modern.ircdocs.horse/#whowas-message

testWhowasMultiTarget[nick2,nick3]

https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3

testWhowasMultiTarget[nick3,nick2]

https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3

testWhowasMultiple

"The history is searched backward, returning the most recent entry first." -- https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 -- https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message

testWhowasNoParamModern

"If the <nick> argument is missing, they SHOULD send a single reply, using either ERR_NONICKNAMEGIVEN or ERR_NEEDMOREPARAMS" -- https://modern.ircdocs.horse/#whowas-message

testWhowasNoSuchNick

https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3 -- https://modern.ircdocs.horse/#whowas-message

and:

"At the end of all reply batches, there must be RPL_ENDOFWHOWAS (even if there was only one reply and it was an error)." -- https://datatracker.ietf.org/doc/html/rfc1459#page-50 -- https://datatracker.ietf.org/doc/html/rfc2812#page-45

and:

"Servers MUST reply with either ERR_WASNOSUCHNICK or [...], both followed with RPL_ENDOFWHOWAS" -- https://modern.ircdocs.horse/#whowas-message

testWhowasNumerics

https://datatracker.ietf.org/doc/html/rfc1459#section-4.5.3 https://datatracker.ietf.org/doc/html/rfc2812#section-3.6.3