Software /
code /
prosody
File
spec/scansion/basic_roster.scs @ 11040:c560531d9a6e
mod_external_services: Validate services added via events
While writing developer documentation it became obvious that i was silly
to have one item format for config and items API, and another format for
the event API.
Then there's the stanza format, but that's a common pattern.
This change reduces the possible input formats to two and allows other
modules the benefit of the processing and validation performed on items
from the config.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 17 Aug 2020 00:24:11 +0200 |
parent | 9305:f14c81fd44a4 |
line wrap: on
line source
# Basic roster test [Client] Romeo jid: user@localhost password: password [Client] Juliet jid: juliet@localhost password: password --------- Romeo connects Juliet connects Romeo sends: <presence/> Romeo receives: <presence from="${Romeo's full JID}" /> Romeo sends: <iq type="get" id="roster1"> <query xmlns='jabber:iq:roster'/> </iq> Romeo receives: <iq type="result" id="roster1"> <query ver='{scansion:any}' xmlns="jabber:iq:roster"/> </iq> # Add nurse to roster Romeo sends: <iq type="set" id="roster2"> <query xmlns="jabber:iq:roster"> <item jid='nurse@localhost'/> </query> </iq> # Receive the roster add result Romeo receives: <iq type="result" id="roster2"/> # Receive the roster push Romeo receives: <iq type="set" id="{scansion:any}"> <query xmlns='jabber:iq:roster' ver='{scansion:any}'> <item jid='nurse@localhost' subscription='none'/> </query> </iq> Romeo sends: <iq type="result" id="fixme"/> # Fetch the roster, it should include nurse now Romeo sends: <iq type="get" id="roster3"> <query xmlns='jabber:iq:roster'/> </iq> Romeo receives: <iq type="result" id="roster3"> <query xmlns='jabber:iq:roster' ver="{scansion:any}"> <item subscription='none' jid='nurse@localhost'/> </query> </iq> Romeo disconnects