Mercury-IM/Smack
Mercury-IM/Smack
1
0
Fork 0
mirror of https://codeberg.org/Mercury-IM/Smack synced 2025-12-05 12:41:08 +01:00
Code Issues Releases Wiki Activity

Enable trailing whitespace checkstyle check

Browse source 
for all source code regions, including javadoc.
This commit is contained in:
Florian Schmaus 2018-05-09 23:06:12 +02:00
parent 9d61a6de7d
commit e8923b9d16
545 changed files with 3713 additions and 3715 deletions
Download patch file Download diff file Expand all files Collapse all files

12
smack-extensions/src/integration-test/java/org/jivesoftware/smackx/MessageEventManagerTest.java
View file

@ -37,10 +37,10 @@ public class MessageEventManagerTest extends SmackTestCase {
/**
* High level API test.
* This is a simple test to use with an XMPP client and check if the client receives the
* This is a simple test to use with an XMPP client and check if the client receives the
* message
* 1. User_1 will send a message to user_2 requesting to be notified when any of these events
* occurs: offline, composing, displayed or delivered
* occurs: offline, composing, displayed or delivered
*/
public void testSendMessageEventRequest() {
// Create a chat for each connection
@ -64,10 +64,10 @@ public class MessageEventManagerTest extends SmackTestCase {
/**
* High level API test.
* This is a simple test to use with an XMPP client, check if the client receives the
* This is a simple test to use with an XMPP client, check if the client receives the
* message and display in the console any notification
* 1. User_1 will send a message to user_2 requesting to be notified when any of these events
* occurs: offline, composing, displayed or delivered
* occurs: offline, composing, displayed or delivered
* 2. User_2 will use an XMPP client (like Exodus) to display the message and compose a reply
* 3. User_1 will display any notification that receives
*/
@ -120,9 +120,9 @@ public class MessageEventManagerTest extends SmackTestCase {
/**
* High level API test.
* 1. User_1 will send a message to user_2 requesting to be notified when any of these events
* occurs: offline, composing, displayed or delivered
* occurs: offline, composing, displayed or delivered
* 2. User_2 will receive the message
* 3. User_2 will simulate that the message was displayed
* 3. User_2 will simulate that the message was displayed
* 4. User_2 will simulate that he/she is composing a reply
* 5. User_2 will simulate that he/she has cancelled the reply
*/