directi / desktop-features-2.0 Goto Github PK

• Upon opening a Chat from the Roster that Chat should take the topmost position in the Active Chats section, unless that Chat Tab is already present in the active chats list
• This test case should be performed for both one-to-one chats and Groups

• Upon hitting the 'Esc' key the the Chat Window which is in focus should be closed

The systray should continue to be present at all times when the App is running. Once the app is exited the Systray should not be present

• The Available presence of a user in the Active Chats section should match the presence displayed for that contact in the Chat Window & Roster

• Clicking on 'Add Another Account' should display the add account modal to the user
• Upon adding another account the account should move to the existing meta only if an existing meta exists for that account (This move should happen automatically)
• If no meta exists then that account should be moved directly and it should be added to the existing meta

• Try adding a Windows Live account which is already present in your existing meta
• The following error message should be displayed. Error Message: Account already exists

• If sending an sms has failed. For example sending an sms to an incorrect number or there could be some network or server-side issue the sms message along with the failure icon should be displayed in the active chats section

• Clicking on 'Cancel' should stop the Sign-In process

• Upon receiving an incoming message a blue unread message counter should be displays which signifies the number of incoming messages received from that particular contact or group
• This test case should be performed for both one-to-one chats and Groups

Case 1:

• If the Username & Password is correct the account should be added successfully
• If a meta exists this account should be added to the existing meta
• If there are no accounts in the existing application a new meta should be created

Case 2: If the Username & Password is incorrect the account should not be added and appropriate error messages should be displayed by Gtalk

• The last message whether sent or received for each contact should always be displayed in the Active Chats section
• If no messages are exchanged with that user no messages should be displayed in the Active Chats preview section

• When you hover on an Active Chat a close option should be displayed so that the user can close that chat
• When you hover on top of the close option is should be dark gray otherwise if you hover anywhere else in the active chat section it should be light gray

• Try adding a Gtalk account which is already present in your existing meta
• The following error message should be displayed. Error Message: Account already exists

• Upon hitting 'Shift+Esc' the last Chat which was closed should be Re-opened and its position in the Active Chats list should be right at the top
• This can also be done with 'Ctrl+Shif+T' on neodesktop

• Upon closing the Google Talk OAuth login page the page should close and a continuous spinner should not be displayed

• The Avatar in the Active Chats section should match the one displayed in the Chat Window for that contact
• If the user does not have an Avatar the Default Avatar should be displayed in the Active Chats section

• If a message is in the Sending state the sending state annimation should also be displayed in the Active Chats section along with the Sending state in the Chat Tab
• To test this send a message after you have disconnected yourself from the network

• The link should resolve to http://talk.to/

• The link should resolve to http://talk.to/account/reset

• Try adding a Facebook account which is already present in your existing meta
• The following error message should be displayed. Error Message: Account already exists

• When a message displays the Sent state in the Chat Tab the same should also be displayed in the Active Chats section
• You can test this issue by sending a message to a person who has exited Talk.to

• Alt+↑: Cycle through open chat tabs (upward)
• Alt+↓: Cycle through open chat tabs (downward)
• This needs to be checked for both one-to-one chats and Group chats

• A blue dot should be displayed along with the message which is unread in the Active Chats section
• This test case should be performed for both one-to-one chats and Groups
• For one-to-one chats only the last unread incoming message will be displayed
• For Groups the name of the sender should also be displayed along with the unread incoming message

Case 1:

• If the Username & Password is correct the account should be added successfully
• If a meta exists this account should be added to the existing meta
• If there are no accounts in the existing application a new meta should be created

Case 2: If the Username & Password is incorrect the account should not be added and appropriate error messages should be displayed by Facebook

• The process should work fine and the account should be added successfully
• If a meta exists this account should be added to the existing meta
• If there are no accounts in the existing application a new meta should be created

• The contacts name in the active chats section should be the same as displayed in the Chat Window

• A scroll-bar should only be displayed on hover if the active chats exceed the number of chats that can be displayed for different screen resolutions and sizes

• Try adding a Pingpong account which is already present in your existing meta
• The following error message should be displayed. Error Message: Account already exists

Case 1:

• If the Username & Password is correct the account should be added successfully
• If a meta exists this account should be added to the existing meta
• If there are no accounts in the existing application a new meta should be created

Case 2: If the Username & Password is incorrect the account should not be added and appropriate error messages should be displayed by Window Live

• Upon sending a message and if the receiver has read that message the Read state should only be displayed in the Chat Tab and not in the Active Chats section

• On clicking 'Cancel' on the Facebook OAuth login page the page should get closed and a continuous spinner should not be displayed

• Upon closing the Windows Live OAuth login page the page should close and a continuous spinner should not be displayed

• Once the message is read the unread blue dot should not be displayed anymore in the active chats section
• This test case should be performed for both one-to-one chats and Groups
• For one-to-one chats only the read incoming message should be displayed in the active chats section
• For Groups the senders name along with the read incoming message should be displayed in the active chats section

• Upon receiving an incoming message that chat should bubble up to the top most position in the Active Chats section
• This test case should be performed for both one-to-one chats and Groups

• Upon closing the Facebook OAuth login page the page should close and a continuous spinner should not be displayed

• In the responsive state the Avatar should be displayed above the name of the contact

• Upon sending a message and if that message has been Delivered to the Receivers client the same should be displayed in the Chat Tab and in the Active Chats section
• A message will be in the Delivered state once a message has been Delivered to the recipient and until that user has not read that message

Case 1: Enter an incorrect email address
Error Message: Error adding {email address}. Please check your username and password

Case 2: Enter an incorrect password
Error Message: Error adding {email address}. Please check your username and password

Case 3: Leave the Email address field blank
Error Message: Please enter a valid email address

Case 4: Leave the Password field blank
Error Message: The Password field cannot be empty

• The process should fail with following error message

Error Message: Error adding {email address}. Please verify your account and try again

• Upon closing all Active Chats the Active chats section should not be displayed anymore in the app

• Upon sending a message it could fail due to various reasons eg network connectivity, server issues etc
• When the client re-connects again the failed message should still be displayed in the Active Chats section with a failed receipt such that the user can try sending that message again upon re-connection or the app itself can attempt to re-deliver that message