jupiter_atp.pdf

JUPITER Acceptance Test Specification Revision A 2014-08-11

Proprietary and Confidential Information

All rights reserved. No part of this document may be reproduced or sent to third party companies without the express prior written permission of Polystar OSIX AB. All intellectual property rights of whatever nature in the business concepts, products or product concepts and any associated documentation including know-how, copyright, patent, design right, moral right, registered design or trademark is and shall remain the exclusive property of Polystar OSIX AB.

Document name: Jupiter AcceptanceTest Revision: C Date: 2012-09-28 Responsible: CPM/PT

[2]

Table of Contents

Scope ..................................................................................................................................................... 4 Test results ............................................................................................................................................. 5 1. Start up .......................................................................................................................................... 7

1.1. Login to Jupiter Passed [ ] Failed [ ] ............................................................................. 7 1.2. Verify installed and licensed Solution Packages Passed [ ] Failed [ ] ................................ 8 1.3. Verify user privileges settings Passed [ ] Failed [ ] ............................................................. 8 1.4. Verify users access privileges Passed [ ] Failed [ ].......................................................... 10

2. User Accounts ............................................................................................................................... 11 2.1. Start the User Account manager Passed [ ] Failed [ ] ...................................................... 11 2.2. Create a User Group Passed [ ] Failed [ ]..................................................................... 11 2.3. Create a User account Passed [ ] Failed [ ] ................................................................... 12 2.4. Change privileges for a User Group Passed [ ] Failed [ ] .................................................. 13 2.5. Change User Settings Passed [ ] Failed [ ] .................................................................... 14

3. Dashboard .................................................................................................................................... 15 3.1. Start the Dashboard Passed [ ] Failed [ ] ...................................................................... 15 3.2. Insert Objects into the Dashboard Passed [ ] Failed [ ] ................................................... 15 3.3. Save the dashboard using 'Save As' Passed [ ] Failed [ ] ................................................. 16 3.4. Open in Inspector Passed [ ] Failed [ ] ......................................................................... 18

4. Inspector ...................................................................................................................................... 19 4.1. Start the Inspector Passed [ ] Failed [ ] ........................................................................ 19 4.2. Create a new report Passed [ ] Failed [ ] ..................................................................... 20 4.3. Save the report Passed [ ] Failed [ ]............................................................................ 21 4.4. Charts Passed [ ] Failed [ ] ........................................................................................ 22 4.5. Verify drill-down to possible objects Passed [ ] Failed [ ] ................................................... 24

5. KPI Builder.................................................................................................................................... 25 5.1. Start the KPI builder Passed [ ] Failed [ ] ..................................................................... 25 5.2. Create a Folder Passed [ ] Failed [ ] .......................................................................... 25 5.3. Create a KPI Passed [ ] Failed [ ] .............................................................................. 26 5.4. Save a KPI Passed [ ] Failed [ ] ................................................................................. 27 5.5. Verify KPI visibility in Inspector Passed [ ] Failed [ ] ....................................................... 27 5.6. Test various combinations of formulas and resources Passed [ ] Failed [ ] ....................... 28

6. KPI and aggregate validation .......................................................................................................... 29 6.1. Check if data comes into system for different KPIs Passed [ ] Failed [ ] ........................... 29 6.2. Check if data comes into system for different aggregates levels Passed [ ] Failed [ ] ........... 30

7. Reference Data ............................................................................................................................. 33 7.1. Verify reference data dimensions and values Passed [ ] Failed [ ] .................................. 33

8. Alarms / Alarm Configuration .......................................................................................................... 35 8.1. Basic Function Passed [ ] Failed [ ] ............................................................................. 35 8.2. View History Passed [ ] Failed [ ] ................................................................................ 35 8.3. Create Reports Passed [ ] Failed [ ] ............................................................................. 36


[3]

8.4. Use Time Schema Passed [ ] Failed [ ] ......................................................................... 36 Acceptance Certificate ........................................................................................................................... 37


[4]

Scope

This document is System Acceptance Test procedure performed on the Jupiter system installation. All test cases are numbered with a unique number. The Acceptance Tests (AT) is divided into two (2) main tasks:

1. Basic test covering Licensing, User access and Applications (GUI) 2. Test to verify configuration as KPIs, Aggregates and Reference Data

. Subject of testing are all servers and functionality of Jupiter system. Vendor is obligated to install configure and solve all eventually appeared problems. All remarks and outstanding items mentioned bellow, Polystar is obligated to solve in agreed period after signing of the Acceptance Test Document or separately defined period for solving of each outstanding-item/remark.


[5]

Test results

Test Case Passed Failed Comment

1 Start up

1.1 Login to Jupiter

1.2 Verify installed and licensed Solution Packages

1.3 Verify user privileges settings

1.4 Verify users access privileges

2 User Accounts

2.1 Start the User Account manager

2.2 Create a User Group

2.3 Create a User account

2.4 Change privileges for a User Group

2.5 Change User Settings

3 Dashboard

3.1 Start the Dashboard

3.2 Insert Objects into the Dashboard

3.3 Save the dashboard using 'Save As'

3.4 Open in Inspector

4 Inspector

4.1 Start the Inspector

4.2 Create a new report

4.3 Save the report

4.4 Charts

4.5 Verify drill-down to possible

5 KPI Builder

5.1 Start the KPI builder

5.2 Create a Folder

5.3 Create a KPI

5.4 Save a KPI

5.5 Verify KPI visibility in Inspector


[6]

5.6 Test various combinations of formulas & resources

6 KPI and aggregate validation

6.1 Check if data comes into system for different KPIs

6.2 Check if data comes into system for different aggregates levels

7 Reference Data

7.1 Verify reference data dimensions and values

8 Alarms / Alarm Configuration

8.1 Alarms Basic Function

8.2 Alarms Configuration

8.3 Alarms Create Reports

8.4 Alarms Use Time Schema


[7]

1. Start up

1.1. Login to Jupiter Passed [ ] Failed [ ] Steps

1. Start the web browser

2. Browse to the Jupiter server 3. A web page with Polystar logo star is open

4. A pop-up window Log on to Jupiter appear 5. Enter un-valid User Name and Password

6. Enter valid User Name and Password

Expected Result

A pop-up Warning with information Incorrect username and password. Please try again... appears when wrong Username and Password is used

Login to Jupiter is successful when valid User Name and Password is entered. Icons for the licensed programs will be shown on the Jupiter desktop (Dashboard, Inspector, and Alarms)

Comment


[8]

1.2. Verify installed and licensed Solution Packages Passed [ ] Failed [ ] Steps

1. Right click in Jupiter workspace

A pop-up menu appears

2. Hover the mouse over System Settings

A pop-up menu appears 3. Select KPI Builder

Expected Result

A pop-up window presents the installed solution packages in the map structure (BellTelSMSAccoutning)

Comment

1.3. Verify user privileges settings Passed [ ] Failed [ ] Steps

1. Open up User Accounts in System Settings

2. Click on selected user group

3. A window tab for Program Access appears 4. Check program access privileges for selected user group

5. Click on tab for Folder Access 6. Check folder access privileges for selected user group

Expected Result

Program and Folder Access privileges should correspond to whats defined for each user group


[9]

Comment


[10]

1.4. Verify users access privileges Passed [ ] Failed [ ] Steps

1. Login as a standard user


3. A pop-up menu appears


5. A pop-up menu appears

6. Check program access privileges for standard user group

Expected Result

Program Access privileges should correspond to whats defined for each user group

Comment


[11]

2. User Accounts

2.1. Start the User Account manager Passed [ ] Failed [ ] Steps



3. Select User Accounts

Expected Result

1. The User Accounts manager opens The user who log in should be chosen on left tree The right panel can not be edited The information of the user should be display correctly The information of the title should be display correctly

2. The gui should be display correctly.

Comment

2.2. Create a User Group Passed [ ] Failed [ ] Steps



3. Select User Accounts

4. Left click in the left pane of the User Account manager

5. A pop-up menu appear

6. Select New Group

7. Enter some name for the group in the pop-up dialog box New Group and click OK

Expected Result

The new group that you added is visible in the left panel of the User Accounts manager


[12]

Comment

2.3. Create a User account Passed [ ] Failed [ ] Steps

1. Right click on the User Group that was created in previous test

A pop-up menu appear 2. Select New User

3. Enter some User ID for the user in the pop-up dialog box New User and click OK

A tab User Setting is opened 4. Fill in Password and Confirm Password and click Save

5. Try to log on as the new user

6. Try to create users under the existing user groups

Expected Result

The new user that you added is visible in the left pane of the User Accounts manager under the group that it was connected to

It is possible to log in as the new user

It is possible to create users under already existing user groups

Comment


[13]

2.4. Change privileges for a User Group Passed [ ] Failed [ ] Steps

1. Right click on the User group that was created in previous test


2. Select Edit

3. Change some privileges in the Program Access tab and in the Folder Access tab 4. Log in as a User belonging to the modified group and verify that the privilege settings

Expected Results

It is possible to change Program Access privileges

It is possible to change Folder Access privileges

The user is affected by the groups privilege settings

Comment


[14]

2.5. Change User Settings Passed [ ] Failed [ ] Steps

1. Right click on the User that was created in previous test

A pop-up menu appears 1. Select Edit

2. Change password and try to log in as the user

3. Unmark the Active box and try to log in as the user

Expected Result

It is possible to change Password

It is not possible to login as a not active user

Comment


[15]

3. Dashboard

3.1. Start the Dashboard Passed [ ] Failed [ ] Steps

1. Double-click the Dashboard icon on the Jupiter desktop

2. Close the Dashboard main window

3. Right-click on the Jupiter desktop

4. A shortcut menu is displayed

5. Hover with the mouse pointer over Software Programs to display the hierarchical menu showing Jupiters applications

6. Click Dashboard to start the application

Expected Result

The Dashboard program is started both when using the desktop icon and the menu shortcut

Comment

3.2. Insert Objects into the Dashboard Passed [ ] Failed [ ] Steps

1. Left-click on Insert in the menu bar in the Dashboard created in previous test (Untitled(0)), a drop down menu opens

2. Left click on Insert report in the dropdown menu, a pop-up menu opens

3. Choose some various reports from the pop-up menu and click OK

4. Repeat the steps above for Image and text

5. Modify the layout of the dashboard

6. Click on Unlock View to unlock the dashboard


[16]

7. Modify the time settings for the dashboard by left click on the Time in the lower left bar of the Dashboard

Expected Result

The reports, Images and text that is chosen is inserted in the dashboard

The layout and Time options of the dashboard can be modified

Comment

3.3. Save the dashboard using 'Save As' Passed [ ] Failed [ ] Steps

1. Left-click on Save in the menu bar in I the Dashboard created in previous TC, a drop down menu opens

2. Left click on Save as in the dropdown menu, a pop-up menu opens 3. Mark the folder dashboard in your user folder

4. Choose a name for the dashboard click OK


[17]

5. Save the dashboard in the public folder, using the Save as function above

Expected Result

The dashboard is saved with the name of your choice

The dashboard is visible in Private folder in the left upper pane of the Dashboard manager

The public dashboard is visible in Public folder in the left upper pane of the Dashboard manager

Comment


[18]

3.4. Open in Inspector Passed [ ] Failed [ ] Steps

1. Open a dashboard that contain some different reports

2. Unlock the view

3. Right click on one report, the report will be selected and a drop down menu appears

4. Left click on Open in Inspector in the drop down menu

Expected Result

The selected report is opened in Inspector with the same filters, Time settings etc that was defined for the report in the dashboard view

Comment


[19]

4. Inspector

4.1. Start the Inspector Passed [ ] Failed [ ] Steps

1. Double-click the Inspector icon on the Jupiter desktop

2. Close the Inspector main window

3. Right-click on the Jupiter desktop.

4. A shortcut menu is displayed.

5. Hover with the mouse pointer over Software Programs to display the hierarchical menu showing Jupiters applications.

6. Click Inspector to start the application

Expected Result

The Inspector program is started both when using the desktop icon and the menu shortcut

Comment


[20]

4.2. Create a new report Passed [ ] Failed [ ] Preconditions

Jupiter is connected to a SMACK data base populated with data for the KPIs

Steps

1. Left click on New in Inspector bar menu, a new tab Untitled is shown in the right pane of the Inspector

2. Right click on Data in the lower left pane of the Inspector

3. Left click on Add KPI from the pop-up menu

4. Choose a KPI from the Add KPI pop-up menu. Do also try the Search function.

5. Left click on Time in the lower left corner of the Inspector frame and set relevant Time properties

6. Refresh the report by left-click on the Refresh icon in the top right corner of the Inspector

7. Toggle between the list view and the chart view by left-click on the icon List View/Chart View in the top right corner of the Inspector

Expected Result

The report is created and data is fetched when doing refresh


[21]

Comment

4.3. Save the report Passed [ ] Failed [ ] Steps

1. Left-click on Save in the menu bar in the Inspector

2. Left click on Save in the dropdown menu

3. Mark the folder Private and choose a name for the report and then click OK

4. Left click on Save as in the dropdown menu 5. Mark the folder Private and choose the same name for the report as in step 3 and then click

OK

6. Mark the folder Private and choose a different name for the report than in step 3 and then click OK

7. Repeat the steps 4-1 above but now you shall save the report in the public folder, using the Save as function above.

Expected Result

1. A drop down menu opens

2. The "Save as a file" window opens

3. The report is saved and visible in Private folder in the left upper pane of the Inspector

4. The "Save as a file" window opens

5. A "Confirm" window appears saying "File already exist, override it?"

6. The report is saved and visible in Private folder in the left upper pane of the Inspector

7. The public report is visible in Public folder in the left upper pane of the Inspector


[22]

Comment

4.4. Charts Passed [ ] Failed [ ] Steps

1. Open the report according to test case "Open the Report"

2. Display the data in different Chart types by right click on the Chart type in the lower left pane of the Inspector and the choose Change Chart from the appearing drop down menu

3. By expanding the Chat Type in the lower left pane of the Inspector a list of Chart attributes are shown. Test to change a random choice of the attributes to random properties values

4. Hoover the mouse pointer over some points in the graph. Values for that point shall be displayed. Compare those values with the values in the List View

Expected Result

Different Chart types display the data in correct way


[23]

Various combinations of graph attributes are possible to change

Values are displayed correct when hovering the mouse in the graph

Comment


[24]

4.5. Verify drill-down to possible objects Passed [ ] Failed [ ] Steps

1. Open the report (SUNToOther) according to "Open the report" in the List View

2. Left click on any value in a column in the table


1. Select Drill down by MAP Error 2. Repeat the test in the Chart View. The pop-up menu is obtained by left-click on a point in the

chart

Expected Result

A new tab is opened in inspector for the selected object

The values for the object corresponds to the value in the Inspector report

Comment


[25]

5. KPI Builder

5.1. Start the KPI builder Passed [ ] Failed [ ] Steps 1. Right click in Jupiter workspace




3. Select KPI Builder Expected Result

The KPI builder opens

Comment

5.2. Create a Folder Passed [ ] Failed [ ] Steps

1. Start the KPI Builder

2. Right click in the left pane of the KPI Builder.

3. A pop-up menu will appear.

4. Left click on New Folder.

5. A pop-up window will appear.

6. Enter a name for your folder and click OK.

Expected Result

The new folder is shown in the left pane of the KPI builder.


[26]

Comment

5.3. Create a KPI Passed [ ] Failed [ ] Steps

1. Create a new folder according to test case "Create a Folder"

2. Right click on the new folder

3. A pop-up menu will appear

4. Left click on New KPI

5. A pop-up window New KPI will appear 6. Enter the name for the new KPI and click OK

Expected Result

The new folder and the new KPI is shown in left pane of the KPI builder.

Comment


[27]

5.4. Save a KPI Passed [ ] Failed [ ] Steps

1. Mark the KPI created in test case "Create a KPI" in the left pane of the KPI Builder

2. Right click on Formula in the right pane of the KPI Builder

3. Left click on Select Counter 4. A pop-up window Counter Selection will appear 5. Mark a Counter and click OK

6. Click on Save at the bottom right in the KPI Builder window

7. A Pop-up window appears with Save changes? 8. Click on Yes

Expected Result

A pop-up window appears with information KPI building successful!

Comment

5.5. Verify KPI visibility in Inspector Passed [ ] Failed [ ] Steps

1. Open the Inspector by clicking on the Inspector icon

2. Right click on Data in the lower left pane in the Inspector

3. A pop-up menu will appear

4. Click on add KPI

5. A pop-up window Add KPI appear with a list of available KPI structure (a refresh might be needed)

Expected Result

The KPI created in test case "Create a KPI" is visible in the Add KPI window


[28]

Comment

5.6. Test various combinations of formulas and resources Passed [ ] Failed [ ] Steps

1. Right click on the KPI created in TC "Create a KPI"

2. Right click on formula in the right pane of the KPI builder 3. Left click on Select Formula from the pop-up menu

4. Choice a formula from the pop-up window Formula Selection 5. Choose counters by right click on the variables and choose Select Counter from the pop-up

menu

6. Verify the formula by open the KPI in inspector

7. Repeat for various formulas and counters

Expected Result

The KPI is successfully opened in Inspector

The formulas tested are working

Comment


[29]

6. KPI and aggregate validation

6.1. Check if data comes into system for different KPIs Passed [ ] Failed [ ] Steps

1. Open up Inspector

2. Right click on Data in below left window and click Add New KPI

3. Open up selected interface map (SUNSMSAccounting) and select all KPI (use Ctrl-Click)

4. Click Refresh and values for selected KPIs will appear in window

5. Repeat step 1-4 for all protocol maps

Active KPIs OK/Not OK

Comment

SMS Accounting KPI

SMS Attempts

SMS Timeout

SMS Failed

SMS Success

SMSSuccessRate

Expected Result

A window presents all KPIs for selected interface and all are expected to contain values


[30]

Comment

6.2. Check if data comes into system for different aggregates levels Passed [ ] Failed [ ] Steps



3. Open up selected interface map and select one KPI (SMS Attempts from SMSAccountingKPI)

4. Click Time in below left corner

5. Set Use Relative Time to true 6. Set Aggregation to 1 day

7. Set Relative Time to Previous 2 days and click Refresh 8. Click Refresh and values for selected KPIs will appear in window

9. Repeat step 1-3 and change to 1 hour and Previous 43 hours 10. Repeat step 1-3 and change to 15 min and Previous 1 hours 11. Repeat step 3-10 for all the SMS Accounting KPIs


[31]

Loading of data 1day 1hour 15 min OK/Not OK

SMS Accounting KPI

SMS Attempts

SMS Timeout

SMS Failed

SMS Success

SMSSuccessRate

Expected Result

Windows presents all data for all selected time periods divided by aggregation level


[32]

Comment


[33]

7. Reference Data

7.1. Verify reference data dimensions and values Passed [ ] Failed [ ] Steps



3. Open up selected interface map(SUNSMSAccounting) and select one KPI (SMS Attempts)

4. Click Time in below left corner

5. Set Use Relative Time to true 6. Set Aggregation to 1 hour

7. Set Relative Time to Previous 24 hours 8. Click Refresh and values for selected KPI will appear in window 9. Right click to select drill down

10. Repeat 2-10 for all list reference data below

Reference Data OK/Not OK Comment

SMS Accounting Refernce Data

Orinating Node

Terminating Node

Map Error

MAP OP Code

Expected Result

All values presented should have a valid reference information


[34]

Comment


[35]

8. Alarms / Alarm Configuration

8.1. Basic Function Passed [ ] Failed [ ] Steps

1. Right click on the desktop and select System Settings -> Alarm Configuration

2. Click on New to open a new alarm tab

3. Select any KPI by right click the Data in the lower right pane and open the Add KPI pane.

4. Set the alarm Level Configuration so one of the levels (higher than clear) will cause be registered as alarm (tip: use the Inspector to find suitable values).

5. Do NOT select a Time Schema

Expected Result

Check in the Alarms that the alarm is generated. And that the severity is according to the level configuration.

Comment

8.2. View History Passed [ ] Failed [ ] Steps

1. Use the alarm created in Basic Function or create a new


3. In Alarms select an alarm and right click it and choose among the different options. For example deactivate and activate it back.

Expected Result

Right click the alarm and select History. Compare the history with your earlier actions.

Comment


[36]

8.3. Create Reports Passed [ ] Failed [ ] Steps



3. Right click on an alarm in Alarms and select Create Report.

Expected Result

The Inspector opens showing the value of the KPI of the alarm.

The Time Properties are set by default.

Comment

8.4. Use Time Schema Passed [ ] Failed [ ]

Steps


2. Set the Time Schema to a suitable schema. Can be necessary to create a schema (a schema that is limited within a certain time or if possible only certain days).

3. Make sure that the Level Configuration is set so one of the levels (higher than clear) will be set.

Expected Result

Verify that it behaves accordingly. E.g. that the alarm, do follow the Time Schema definition.

Comment


[37]

Acceptance Certificate

Customer BellTel

Project SMS Accounting

Customer ref

Polystar ref

Acceptance Date

Scope Being Accepted

Jupiter for SMS Accounting in accordance with P.O. XXXXX to BellTel, in Manila, Philippines. This signed document signifies formal acceptance of Jupiter supplied by Polystar AB according to the terms stated in the PO XXXXX. Any exceptions to this are noted below and acknowledged by Polystar AB, which remains responsible for their resolution.

Exception Agreed Completion Date

The Polystar Project Manager confirms that all the contractual requirements agreed with the client for OSIX complies to P.O. 5500045342/ 5500045344/ 5500045350 and by this letter requests the acceptance from Digitel Mobile Philippines Inc.

BellTel, Project Manager

Shawn Teng, Customer Project Manager

BellTelError! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not found.Error! Reference source not

Polystar AB


[38]

found.Error! Reference source not found.Error! Reference source not found.

Date: 2014-10-10 Date: 2014-10-10

jupiter_atp.pdf

Documents

user group

user settings

user privileges settings

user accounts

user account manager

design right

intellectual property

users access privileges