vanitasvitae/Smack
1
0
Fork 0
mirror of https://github.com/vanitasvitae/Smack.git synced 2024-11-25 21:42:07 +01:00
Code Issues Releases Wiki Activity

[sinttest] Add ejabberd specific behavior for mucMaxUsersLimitJoinRoomTest

Browse source 
ejabberd returns resource-constraint instead of service-unavailable if
the maximum number of participants is reached.
This commit is contained in:
Florian Schmaus 2024-05-20 22:00:56 +02:00
parent e69e7d2342
commit 6cda9a6379
1 changed files with 15 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
smack-integration-test/src/main/java/org/jivesoftware/smackx/muc/MultiUserChatOccupantIntegrationTest.java
View file

@ -728,18 +728,23 @@ public class MultiUserChatOccupantIntegrationTest extends AbstractMultiUserChatI
// it can kick user 2. Both strategies would comply with the specification. So the only thing we can
// reasonably test here is whether the room doesn't have more occupants than its max size.
try {
mucAsSeenByThree.join(nicknameThree);
} catch (XMPPException.XMPPErrorException unavailableErrorException) {
// This exception is expected if the muc implementation employs the strategy to deny access beyond the
// maxusers value
if (unavailableErrorException.getStanzaError() == null
|| !StanzaError.Condition.service_unavailable.equals(
unavailableErrorException.getStanzaError().getCondition())) {
throw unavailableErrorException;
}
XMPPException.XMPPErrorException errorException = assertThrows(XMPPException.XMPPErrorException.class, () -> mucAsSeenByThree.join(nicknameThree));
final StanzaError.Condition expectedCondition;
switch (sinttestConfiguration.compatibilityMode) {
default:
expectedCondition = StanzaError.Condition.service_unavailable;
break;
case ejabberd:
expectedCondition = StanzaError.Condition.resource_constraint;
break;
}
StanzaError stanzaError = errorException.getStanzaError();
assertNotNull(stanzaError);
assertEquals(expectedCondition, stanzaError.getCondition());
// Now we should wait until participant one is informed about the (probably failed) new participant three
// room join. But if joining failed, there will be no such update. All we can reasonably do is wait until
// participant three has received its own presence response. This is not watertight though.