-
Notifications
You must be signed in to change notification settings - Fork 446
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #12959 from nextcloud/feat/12887/user-statuses-in-…
…federated-conversations feat(statuses): Post-load local user statuses in federated conversations
- Loading branch information
Showing
4 changed files
with
89 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
tests/integration/features/federation/user-statuses.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
Feature: federation/user-statuses | ||
|
||
Background: | ||
Given using server "REMOTE" | ||
And user "participant2" exists | ||
And user "participant3" exists | ||
And the following "spreed" app config is set | ||
| federation_enabled | yes | | ||
And using server "LOCAL" | ||
And user "participant1" exists | ||
And the following "spreed" app config is set | ||
| federation_enabled | yes | | ||
|
||
Scenario: User statuses are added to the participant request in federated conversations | ||
Given user "participant1" creates room "room" (v4) | ||
| roomType | 2 | | ||
| roomName | room | | ||
And user "participant1" adds federated_user "participant2@REMOTE" to room "room" with 200 (v4) | ||
And user "participant1" adds federated_user "participant3@REMOTE" to room "room" with 200 (v4) | ||
And using server "REMOTE" | ||
And user "participant2" has the following invitations (v1) | ||
| remoteServerUrl | remoteToken | state | inviterCloudId | inviterDisplayName | | ||
| LOCAL | room | 0 | participant1@http://localhost:8080 | participant1-displayname | | ||
And user "participant2" accepts invite to room "room" of server "LOCAL" with 200 (v1) | ||
| id | name | type | remoteServer | remoteToken | | ||
| LOCAL::room | room | 2 | LOCAL | room | | ||
Then user "participant2" set status to "away" with 200 (v1) | ||
And user "participant3" has the following invitations (v1) | ||
| remoteServerUrl | remoteToken | state | inviterCloudId | inviterDisplayName | | ||
| LOCAL | room | 0 | participant1@http://localhost:8080 | participant1-displayname | | ||
And user "participant3" accepts invite to room "room" of server "LOCAL" with 200 (v1) | ||
| id | name | type | remoteServer | remoteToken | | ||
| LOCAL::room | room | 2 | LOCAL | room | | ||
Then user "participant3" set status to "dnd" with 200 (v1) | ||
And user "participant2" is participant of room "LOCAL::room" (v4) | ||
And user "participant2" sees the following attendees with status in room "LOCAL::room" with 200 (v4) | ||
| actorType | actorId | participantType | status | | ||
| federated_users | participant1@{$LOCAL_URL} | 1 | ABSENT | | ||
| users | participant2 | 3 | away | | ||
| users | participant3 | 3 | dnd | |