Test new XiVO UC installation on Deneb or newer XiVO

Test XiVO UC upgrade

Test Incoming calls listing page

This tests check if the user list API works as intended

Objectif : Le caller id de l'utilisateur principal est utilisé pour tout les types d'appel

Import csv file with labels.

• Import user with labels : import_labels.csv
• import_labels.csv

User with labels can be updated

• users_voicemail.csv
• users_voicemail.csv

Verify that users with labels are exported in CSV

• Line creates correctly
• Line context changes correctly in all three database tables.
• It is not possible to create two lines with the same number and context.

Test fix https://projects.xivo.solutions/issues/536

1. New template line should be editable and deletable
2. Existing template lines should be editable and deletable or it should be documented how to delete them. Documented in release notes.
3. Template device can be added / edited / deleted

Test creating/editing user with combination of:

• having line
• group membership
• queue membership

Test that it is not possible to delete line from user who is

• group member

and/or:

• queue member

Test creating/editing UA user with combination of:

•  the Boss/Secretary select box
•  the Agent select box
•  the Group combo box
•  the Queue combo box

The purpose of this tests is to check that there is no timeout or too long execution time when saving user with many funckeys

Test adding, editing and deleting funckeys

this testcase cover the edit label webi page

this testcase cover the add label page of the webi

This testcase cover the delete function of labels

This test check if the user filtering and searching are working as intended

This test cover the configmgt api to add / edit / delete an user line from the web interface

Modification of a user must be possible without undesirable side effects

Objectif: Il doit être possible d'ajouter un utilisateur avec une ligne de type custom pour éventuellement utiliser une interface définie manuellement.

Par exemple: DAHDI/i1/4185551234 ou Local/4185551234@internal

We will make sure the call filtering can be activated and canceled by the boss and the secretary only

Objectif : Lorsqu'un utilisateur avec une terminaison est supprimé, la terminaison est desassociée.

Objectif : Valider que le fait de supprimer une terminaisons SCCP associée désassocie complètement la terminaison de son ancienne ligne.

Test monitoring on Webi > Services > Monitoring page

Recording saves call records and Configuration manages users that can access it

Agen can login, change styate, see available agents on its queue

Checks the Kibana panels

Checks SpagoBI and statistics using sample reports

Validate that the call history is generated and available through xuc interfaces

Verify that desktop assistant is available to be downbloaded from web interface and at least runs on Windows

Check organizer actions on other attendees

For webrtc users 

This test aims to check if :

- A toast message appears when a user cannot receive a flashtext

- The css for the long usernames is ok 

Be able to send a chat message while other party is offline

Verify that user receives unread notification after log in

Verify that chat message can be sent to every xivo user.

Verify that a chat message can be send to a user who was never logged in

Verify that users can continue send and receive messages in case Asterisk/cti link crashed and is restored

Check assistant is working correctly with users with a phone / softphone / webRTC / SCCP / Custom Line

When I add user (with WebRTC line or line with provisioned SIP phone) after Xuc start, I want him to be able to log-in Web Assistant and call without Xuc restart 

Login just after  Xuc server restart may fail, but should not result in state, when user is unabkle to login at all (until next Xuc server restart)

If test fail, please attach relevant portion of xuc.log (starting with first xuc start after which test fail)

Validates #935

When logging on while there's some ongoing calls, the tab should initialize to reflect these

Test that notification and a popup are displayed when a long call is put On Hold

this test checks if the containerResizable directive is working properly

this test is to make sure that we cannot play the ringing audio by pressing a media key.

Checks if the warning message is displayed before reloading the page when a call is ongoing. 

Check that webrtc users can mute themselves during a call : 

- by clicking on the mute button 

- by clicking on the voice meter 

On the login page of the web assistant, I can download the desktop assistant by clicking on the windows link. 
The Linux-Debian link should lead to the documentation. 

When a yealink user receives a second call, he is not able to answer from the uc assistant. 

When I'm chatting with someone, I can call them direclty from the chat window. 

This test checks if you can get back to parties list from a chat window

User should see a letter icon when receiving a message

During conversation the letter is not displayed if the message is for this conversation

This test aims to check if :

- A toast message appears when a user cannot receive a flashtext

- The css for the long usernames is ok 

The goal is to verify that the operator can retrieve a call while he has a ringing incoming call

 Swichboard operator can answer and hangup calls with the shortcuts.

 Swichboard operator can make an attended transfer to another user with the shortcuts.  

Making sure that the switchboard operator can make a direct transfer to the hold queue by pressing F9 

Verify if the page, mouse and keyboard focuses are right on switchboard.  

Download switchboard stats reports using webi in pdf

This tests aims to verify if a switchboard operator can navigate with the keyboard in the search results and make transfers from the call action dropdown.   

The goal is to verify that the operator can not retrieve a call while he has an originating incoming call

Verify that newly created queue is available for switchboard operator to login and receive calls

Agent should hear notification when manager starts to listen to its call

Agent A1 receives acd call, pause while ringing, answer call, then hangup. The last state is Pause.

Test agent states with every (or almost) transfer cases on a Snom phoneset.

There is a common pattern for these tests :

 a call which answered on A1's phone set which he transfers to A2 (either directly or via another queue, either with the phone set ot via the ccagent)

Test agent states with every (or almost) transfer cases with a Yealink phoneset.

There is a common pattern for these tests :

 a call which answered on A1's phone set which he transfers to A2 (either directly or via another queue, either with the phone set ot via the ccagent)

Test agent states with every (or almost) transfer cases with a Polycom phoneset.

There is a common pattern for these tests :

 a call which answered on A1's phone set which he transfers to A2 (either directly or via another queue, either with the phone set ot via the ccagent)

Test agent states with every (or almost) transfer cases with a WebRTC user.

There is a common pattern for these tests :

 a call which is answered on A1's webrtc line which he transfers to A2 (either directly or via another queue via the ccagent)

Validates that XuC correctly initialize agent state after restart

The purpose is to verify that agent state does not change when you edit user linked with an agent.

Test that we can retrieve all call history of a customer when call is ongoing.

Purpose is to test that history is refreshed when a call is ongoing, missed or emited with correct agent information.

Agent outgoing calls are displayed in ccagent history

- Outgoing on its affected place when logged on it

- Outgoing on any place the agent is logged on

- Outgoing on phone set when not logged on is not taken into account

This tests aims to verify if an agent can navigate with the keyboard in the search results and make a call from the call action dropdown.   

Checks if the warning message appears before reloading the page during an ongoing call.

Verify that newly created queue is available for agent to login and receive calls

Check that webrtc peer is correctly unregistered when logout / quitting application.

This testlink checks that the webrtc doesnt explode if somebody with special letters in his name calls the webrtc user

This test check if ccagent and switchboard users can mute themselves as webrtc

This test only checks that we can't reach Asterisk from outside (and particulary from XiVOCC enviroment)

You can get the list of all XDS CELs with the recording server API.

Test Real time calculated Queue statistic generated by xuc - see documentation.

 Test if successive calls from UC assistant and desktop phone directly are shown in history

Verify that I can create a Unique Account user and provision a phone on it (and still having the webrtc line).

Test that a UA user can connect to UC Assistant, be recognized as a WebRTC user, and call

Test voicemail for unique account user

Test that a UA user can receive call

• on its deskphone (when not connected to UC Assistant)
• or on its UC Assistant (when logged in the UC Assistant)

The noanswer/busy rule should applies to the UC Assistant 'state' as soon as you're logged on the UC Assistant or to the phone 'state' if you're not.

This test is to verify that presence states are changing if User UA is logged in with deskphone and web rtc 

Here a reference table

The goal is verify that the current (ongoing) call can be send directly to the hold queue

Verify that changes made to the line are reflected.

Verify that a user with line type UA is not available to be added to the groups, queues or agents

This intends to test the behavior of our plantronics service, communicating with the plantronics API.

This intends to test the behavior of our plantronics service, communicating with the plantronics API.

This intends to test the behavior of our plantronics service, communicating with the plantronics API.

Making sure the electron window can stretch to full screen during a video call.

This test needs to be launched on two platforms (Windows and Linux), it checks :

- When you click on close button of the desktop assistant it does'nt close the app if configured in settings. 

- It launches at startup of the OS if defined

- Test notification icons in Tray notification bar

Check if the electron tray icon gets updated correctly on missed calls and on new flashtext

this test will make sure that the desktop assistant displays correctly on every resolution and also with custom zoom factor

check if the display works on windows 10 when the user has a different zoom on each of his screen, for example an user with a thinkpad laptop zoomed at 125% and a 1080p screen with standard 100% zoom

Checks that a warning is displayed when refreshing the desktop apps during an ongoing call. 

Ensure routing between MDS is working when forwarding a user to another one 

This test aims to verify that a webrtc user on mds1 can call and receive internal calls from a phone user on MDS0.  

Calls between webrtc users on different MDS

Calls between external user and webrtc on MDS 

I can call a Group/Queue/Meetme configured on XiVO Main

When in an XDS installation I should see the correct status of every user of installation.

Note that currently (Callisto.02) the initial state is incorrect but becomes eventually correct.