Changeset

9708:6507df6d2c55

MUC: Test that subject is still empty after sending a non-subject change message with a subject (#667)
author Kim Alvefur <zash@zash.se>
date Sun, 16 Dec 2018 22:59:14 +0100
parents 9707:9171eddcce93
children 9710:8649a6b010e2
files spec/scansion/muc_subject_issue_667.scs
diffstat 1 files changed, 27 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/spec/scansion/muc_subject_issue_667.scs	Sun Dec 16 22:53:56 2018 +0100
+++ b/spec/scansion/muc_subject_issue_667.scs	Sun Dec 16 22:59:14 2018 +0100
@@ -42,6 +42,33 @@
 		<body>Hello everyone</body>
 	</message>
 
+# Resync
+Romeo sends:
+	<presence to="issue667@conference.localhost/Romeo">
+		<x xmlns="http://jabber.org/protocol/muc"/>
+	</presence>
+
+# Presences
+Romeo receives:
+	<presence from="issue667@conference.localhost/Romeo">
+		<x xmlns="http://jabber.org/protocol/muc#user">
+			<item affiliation="owner" role="moderator" jid="${Romeo's full JID}"/>
+			<status code="110"/>
+		</x>
+	</presence>
+
+Romeo receives:
+	<message type="groupchat" from="issue667@conference.localhost/Romeo">
+		<subject>Greetings</subject>
+		<body>Hello everyone</body>
+	</message>
+
+# the still empty subject
+Romeo receives:
+	<message type="groupchat" from="issue667@conference.localhost">
+		<subject/>
+	</message>
+
 # this is a subject change
 Romeo sends:
 	<message to="issue667@conference.localhost" type="groupchat">