system acceptance tests

7/22/2019 System Acceptance Tests

1/32

Nokia MMS Center 2.0

System Acceptance Tests

Installation Guides

DN00148805Issue 3a-0 en

Nokia Corporation 1 (32)


2/32


The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means withoutthe prior written permission of Nokia. The document has been prepared to be used by

professional and properly trained personnel, and the customer assumes full responsibilitywhen using it. Nokia welcomes customer comments as part of the process of continuousdevelopment and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However,Nokia has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia will, if necessary,explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDINGMONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright accordingto the applicable laws.

NOKIA logo is a registered trademark of Nokia Oyj.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright Nokia Oyj 2002. All rights reserved.

2 (32) Nokia Corporation DN00148805Issue 3a-0 en


3/32

Contents

Contents

1 About this document ...........................................................................5

1.1 Scope.....................................................................................................51.2 Audience................................................................................................5

2 Preparing for system acceptance tests .............................................. 72.1 Test environment....................................................................................72.2 Preconditions for testing.........................................................................82.2.1 Starting the system acceptance tests ..................................................... 82.2.2 Configuring the mail gateway .................................................................8

3 Performing system acceptance tests .................................................93.1 GUI tests................................................................................................93.1.1 Login/logout............................................................................................93.1.2 Component management.....................................................................103.1.3 System configuration............................................................................113.2 Messaging tests ...................................................................................123.2.1 MO-MT messages................................................................................123.2.2 MO-AT messages ................................................................................133.2.3 AO-MT messages ................................................................................143.2.4 MO - multiple MT and AT messages .................................................... 153.3 Alarm tests ...........................................................................................163.3.1 WAP Gateway down ............................................................................163.3.2 Application missing............................................................................... 163.3.3 System Logging enabling .....................................................................17

3.4 Subscriber database component tests..................................................193.4.1 Subscriber database with subscriber barring........................................193.5 Address hiding tests.............................................................................203.5.1 Address Hiding enabled in the MMS Center kernel

configuration, MOMT messages.........................................................203.6 Content adaptation tests....................................................................... 223.6.1 Resolution and size reduction, SMIL+JPEG.........................................223.7 Prepaid tests ........................................................................................243.7.1 Credit OK .............................................................................................24




4/32


Summary of changes

Date Issue Summary of changes

March 2001 1-0 en First issue

October 2001 2-0 en Document revised for release MC1CD1

November 2001 2a-0 en Configuration filegws_number_conversion.cf added to Section 3.1.3 Systemconfiguration.

Added Section 3.5 Subscriberdatabase component tests.

May 2002 3-0 en Updated for MMS Center release 2.0.

Added sections

3.3.3 System Logging enabling.

3.6Address hiding test

3.7 Content adaptation tests

3.8 Prepaid test

Removed section Billing tests.

June 2002 3a-0 en Minor corrections after pilot phase.



5/32

About this document

About this document

1.1 Scope

This document describes the system acceptance tests for Nokia MMS Centerrelease 2.0. The system acceptance tests consist of a number of procedures thatare performed to check that the MMS Center is functioning properly.

This document also describes the test environment and provides worksheets forrecording the results of the tests. In addition, this document includes acertificate which, when completed, provides confirmation that the systemacceptance tests have been performed and accepted.

1.2 Audience

This document is intended for the engineers and technical personnel involved inthe installation of the MMS Center at the operators site.




6/32




7/32

Preparing for system acceptance tests

Preparing for system acceptance tests

This chapter describes the test environment and explains the procedures thatshould be performed before starting the system acceptance tests.

2.1 Test environment

The test environment consists of:

Nokia MMS Center, properly installed and configured

connection to a mail gateway, installed in the same server with the MMS

Center ($SC_TMPPATH/sat/)

WAP Gateway, properly installed and configured

two MM enabled mobile phones (for example Nokia 9210 with MMSapplication)

SMS Center connected to the WAP Gateway

Figure 1 illustrates the test environment.




8/32


MT 2MT 1

BSS

WAPGW

MMSCenter

Applicationserver

SMSCenter

Figure 1. Test environment for system acceptance tests

2.2 Preconditions for testing

Before starting the system acceptance tests, complete the procedures describedin the following sections. See the customer documentsOperating MMS CenterandInternet Mail Gateway.

2.2.1 Starting the system acceptance tests

Start the MMS Center from the GUI.

2.2.2 Configuring the mail gateway

Configure the mail gateway application through the GUI.



9/32

Performing system acceptance tests


Perform the following procedures in the order they are presented in the sectionsbelow. Record your observations in the tables provided in the worksheets in theAppendix.

3.1 GUI tests

3.1.1 Login/logout

Purpose

To prove that when the GUI is opened, the login/logout process functions asexpected.

Preconditions

MMS Center server configured and ready.

Procedure, step 1

1. Open Netscape and start the MMS Center GUI.

2. Log in as user admin, password admin.

Expected result, step 1

Login window appears.

Login successful, Home Page is displayed.

Procedure, step 2

Click the Logoutbutton.




10/32



Logout successful and system returns to Login window.

3.1.2 Component management

Purpose

To prove that when a user is correctly logged into the system, the componentmanagement process functions as expected.

Preconditions

Test 3.1.1 Login Step 1 has been completed successfully, with permission forcomponent management.

Procedure

Open the Component management window.

Expected result

All components are listed and their status is Running or Not Running:

MMS Center

Kernel

EAIF

Database Log Writer

Alarm daemon



11/32


3.1.3 System configuration

Purpose

To prove that when a user is correctly logged into the system, the systemconfiguration process functions as expected.

Preconditions

Test 3.1.1 Login Step 1 has been completed successfully.

Procedure

Open the System configuration window.

Expected result

All configuration files are listed.

See the files in documentNokia MMS Center Configuring Files.




12/32


3.2 Messaging tests

3.2.1 MO-MT messages

Purpose

To prove that if a text + picture message is sent MO-MT, it is successfullyprocessed.

Preconditions

Clean configuration, no ported numbers. Send a message with text and picture.

Message has not been requested by the terminating MS.

Procedure, step 1

View the parameters of this message in the message database:

1. Select the Messagesoption from the GUI main menu.

2. Select this message and open the Message Detailwindow.


The message details conform to the sent message.

Procedure, step 2

View the event log record for this message.

1. Select the Event Logoption from the GUI main menu.

2. Select this message and open the Log Detailwindow.


Log details conform to the sent message. Success indicator is OK.

Procedure, step 3

Check for message notification at the terminating MS.


The message notification is present.



13/32


Procedure, step 4

1. Request a message at the terminating MS.

2. View the event log record for this message:

- Select event log option from the GUI main menu.

- Select this message and open the Log Detailview,


The message is successfully received.

Log details conform to the sent message.

3.2.2 MO-AT messages

Purpose

To prove that if a text + picture message is sent MO-AT, it is successfullyprocessed.

Preconditions

The terminating application is running.

Send a message with text and picture.

Procedure

1. Check the arrival of the message at the terminating application.

2. View the event log record for this message.

- Select the Event Logoption from the GUI main menu.

- Select this message and open the Log Detailwindow.

Expected result






14/32


3.2.3 AO-MT messages

Purpose

To prove that if a text + picture message is sent AO-MT, it is successfullyprocessed.

Preconditions

The sending application is running.

Send a message with text and picture.

The message has not been requested by the terminating MS.

Procedure, step 1

View the parameters of this message in the message database.





Procedure, step 2

View the event log record for this message.

1. Select the Event Logoption from the GUI main menu.




Success indicator is OK.

Procedure, step 3

Check for a message notification at the terminating MS.



Procedure, step 4

1. Request message at terminating MS.




15/32



- Select this message and open the Log Detailwindow.


Message is successfully received.


3.2.4 MO - multiple MT and AT messages

Purpose

To prove that if a text + picture message is sent MO - multiple MT and AT, it is

successfully processed.

Preconditions

The terminating MS and applications are running.

Send a message with text and picture to 2x terminating MS, 2x mailaddresses and 2x terminating applications (e.g. e-mail).

The terminating MS has not retrieved the message.

Procedure, step 1

View the parameters of this message in the message database.1. Select the Messagesoption from the GUI main menu.



The MT message details conform to the sent message.

The status is OK.

Procedure, step 2

View the event log record for this message.1. Select the Event Logoption from the GUI main menu.








16/32


3.3 Alarm tests

3.3.1 WAP Gateway down

Purpose

To prove that if the WAP Gateway is down, the alarm process functionscorrectly.

Preconditions

The MMS Center is running and the WAP Gateway is up.

Login completed successfully, with permission for componentmanagement.

Procedure, step 1

1. Open the Component Managementwindow.

2. Stop the WAP Gateway.

3. Send an application-originated message.


A relevant alarm is generated.

3.3.2 Application missing

Purpose

To prove that if a message is sent and the terminating application is NOTrunning, the alarm process functions correctly.

Preconditions

Login completed successfully, with permission for external applications.

The target application is properly configured.

Procedure, step 1

4. Open the External Applications window.

5. Select an application for deletion and stop.



17/32



The application is stopped.

Procedure, step 21. Start sending an MS.

2. Send an MO-AT message with text and picture.



- Select this message and open the Log Detail window.



Log details conform to details for sent message.

3.3.3 System Logging enabling

Purpose

To prove that if system logging is enabled, all events are logged.

Preconditions

The MMS Center is running.

The Alarmwindow is open.

Procedure, step 1

1. Check that syslog is enabled in xlwmanmx.cfin $SC_CONFPATHe.g. [thread_2].

- ENABLED TYPE = 254

2. Modify the syslog section as follows:

- LOGFILES = 5

- MAX_SIZE = 8176

3. Remove all syslog files from $SC_LOGPATH/syslog.

4. Restart the log writer. ($SC_BINPATH/xsccmdmx c xlwmanmx)

5. Generate alarms, e.g. start/stop MMSC, so that all 5 syslog files are fulland first one is overwritten.

6. Verify that all events are logged to the syslog files.




18/32



5 syslog files are created in $SC_LOGPATH/syslog.

When the last syslog file becomes full, storing continues from the first

file and data in that file is overwritten.

All events have been logged to syslog files.



19/32


3.4 Subscriber database component tests

3.4.1 Subscriber database with subscriber barring

Purpose

To prove that if the subscriber is added to the subscriber database, the systembehaves as set in the database.

Preconditions

Two MSs are ready and switched on. Two subscribers have been added to the NAP database without any

special settings.

The MMS Center and NAP have been connected.

Procedure, step 1

1. Send a message from MS1 to MS2.

2. Check the event log record for this message.


The notification is shown at the receiving MS.

The message is delivered to the receiving MS.

The Log window shows that the message is delivered normally.

Procedure, step 2

1. Bar all incoming messages for MS2 in NAP.

2. Send a message from MS1 to MS2.

3. Check the Event Log window and the log record for this message.


The message is not delivered to MS2.

The Event Log record shows that the message is barred.




20/32


3.5 Address hiding tests

3.5.1 Address Hiding enabled in the MMS Center kernel configuration,MOMT messages

Purpose

To prove that if Address Hiding is enabled in the MMS Center kernelconfiguration, the sender can decide whether to show his address to the messagerecipient or not.

Preconditions

Modify routing section in ymc_mmsc.cf in $SC_CONFPATH as follows:

ADDRESS_HIDING_ENABLED = 1

Activate modifications:

reinitialize the kernel in GUI Component Management window.

Originating and terminating MS switched ON and ready.

Procedure, step 1

4. Send an MO-MT message and don't set any value for the MS'sM-

Send.req X-Mms-Sender Visibilityfield.

5. Select the Messagesoption from the GUI main menu.6. Open the Message Detailswindow.


In the Message Details view:

Originating address is shown

Address Hiding = Shown

Address is not hidden -> Originating address is shown on the receivedmessage in the terminating MS.

Procedure, step 2

7. Send an MO-MT message and set MS's M-Send.req X-Mms-

Sender Visibilityfield as 'hide'.

8. Select the Messages option from the GUI main menu.

9. Open the Message Detailswindow.



21/32





Address Hiding = Hide

Address is hidden -> Originating address is NOT shown on the receivedmessage in the terminating MS.

Procedure, step 3

1. Send an MO-MT message and set MS's M-Send.req X-Mms-

Sender Visibilityfield as 'show'.


3. Open the Message Detailswindow.




Address Hiding = Show

Address is not hidden -> Originating address is shown on the receivedmessage in the terminating MS

Procedure, step 4

1. Execute step 1 step 3again, but now switch the terminating MS offbefore message sending.

2. After sending a message, switch the terminating MS on.


The same as in step 1 step 3.




22/32


3.6 Content adaptation tests

3.6.1 Resolution and size reduction, SMIL+JPEG

Purpose

To prove that if a valid SMIL+JPEG message is sent MO-MT, the resolutionand size reduction is made according to terminal capabilities.

Preconditions

3. The MMS Center is running.

4. The content adaptation log has been set on (the default is ON,$SC_LOGPATH/calog).

5. Environment variables SC_CONFPATH and UA_CONFPATH havebeen set properly.

6. UA_HEADER_NAME parameter in gwrmanmx.cf has been set properly:UA_HEADER_NAME=user agent

7. Adaptation is enabled in the kernel configuration:

In xkrmanmx.cf : ADAPTATION_ENABLED = 1

8. The capacity license key allows message adaptation.

9. UA header information is available in ytcUAHeader.cf.

10. Terminal capabilities:

MmsCppAccept=text/plain,image/jpeg,application/smil

MmsMaxMessageSize=32kb

MmsMaxImageResolution=120x90

11. The originating and terminating MSs are switched on and ready.

12. MMAE has been configured to use the FRS policy (configured inyad_policy.cf).

Procedure, step 1

1. Send a message consisting of simple SMIL presentation, totaling ~62kb:

Text: 2kb

+ image/jpeg: 60kb

image resolution = 200 x 150

2. View the parameters of this message in the Message Database:

Select the Messagesoption in the GUI main menu.



23/32


Select this message and open the Message Detailwindow.

3. Check for message notification at the terminating MS.

4. Check the Event Log.



A message notification is present at the terminating MS.

The Event Log details conform to the sent message, the log type isAccepted.

No events about failed adaptation are shown in the MMS Center EventLog.

The message is delivered, resolution and size reduction are performed.




24/32


3.7 Prepaid tests

3.7.1 Credit OK

Purpose

To prove that IF a prepaid customer has enough credits, THEN message isdelivered successfully.

Preconditions

The MMS Center is running. PREPAID_METHOD has been set to 1 in xkrmanmx.cf.

The terminating MS is switched on and ready.

Procedure, step 1

1. Send an MO-MT message.

2. The message is requested by the terminating MS.

3. Check that correct data is written to the CDR file. Compare the contentsto the Event Log details.


Money reservation from the prepaid system is done and committed whenthe message is accepted to the system.

The message is delivered to the terminating MS.

Correct data is written to the CDR file.



25/32

Appendix. System acceptance test worksheets


GUI

1. Login/Logout

Result OK Notes

Login window appears.

Login successful, home page isdisplayed

Logout successful and systemreturns to Login window.

2. Component management

Result OK Notes

All components are listed andtheir status is Running or NotRunning:

MMS Center

Kernel

EAIF

Database Log Writer

Alarm daemon

3. System configuration

Result OK Notes

All configuration files are listed:

Kernel configuration files

Logging configuration files

Control files




26/32


MESSAGING TESTS

4. MO - MT messages

Result OK Notes

The message details conform tothe sent message.

Log details conform to the detailsof the sent message.


The message notification ispresent.

The message is successfully

received.


5. MO-AT messages

Result OK Notes

The message is successfullyreceived.


6. AO-MT messages

Result OK Notes

Message details conform to thesent message.



The message is successfullyreceived.




27/32


7. MO - multiple MT and AT messages

Result OK Notes

The MT message detailsconform to the sent message.

The status is OK.






28/32


ALARM TESTS

8. WAP Gateway down

Result OK Notes


9. Application missing

Result OK Notes

The application is stopped.



10. System Logging enabling

Result OK Notes

5 syslogs file are created in$SC_LOGPATH/syslog.

When the last syslog filebecomes full, storing continuesfrom the first file and data in thatfile is overwritten.

All events have been logged tosyslog files.



29/32


SUBSCRIBER DATABASE COMPONENT TESTS

11. Subscriber database with subscriber barring

Result OK Notes

The notification is shown at thereceiving MS.

The message is delivered to thereceiving MS.

The Log window shows that themessage is delivered normally.

The message is not delivered to

MS2.

The Event Log record shows thatthe message is barred.

ADDRESS HIDING TESTS

12. Address Hiding enabled in MMSC Kernel Configuration, MOMTMessages

Result OK Notes

The originating address is shownin the Message Details window.

Address Hiding = Shown in theMessage Details window.

Address is not hidden, whichmeans that the originatingaddress is shown on thereceived message in theterminating MS.

The originating address is shownin the Message Details window.

Address Hiding = Hide in theMessage Details window.

Address is hidden, which meansthat the originating address isNOT shown on the receivedmessage in the terminating MS.




30/32


CONTENT ADAPTATION TESTS

13. Resolution and size reduction, SMIL+JPEG

Result OK Notes

Message details conform to thesent message.

A message notification is presentat the terminating MS.

The Event Log details conform tothe sent message, the log type is

Accepted.

No events about failed

adaptation are shown in theMMS Center Event Log.

The message is delivered,resolution and size reduction areperformed.

PREPAID TESTS

14. Credit OK

Result OK Notes

Money reservation from the prepaid

system is done and committed when

the message is accepted to the

system.

The message is delivered to the

terminating MS.

Correct data is written to theCDR file.



31/32

References

Certificate. Verifying MMS Center system acceptance tests

Customer name:MMS Center SW level:

WAP Gateway SW level:

Change / technical notes:

SMS Center vendor and release:

MSC&HLR vendor and release:

Function OK(Initials)

Comments

Login/Logout

Component management

System configuration

MO-MT messages

MO-AT messages

AO-MT messages

MO - multiple MT and AT messages

WAP Gateway down

Application missing

CDR file writing, no rotation

CDR file writing, rotation level 1

Valid MO-MT message

Subscriber database with subscriberbarring

_______________________________________________________ _____________________

Customer representative(sign and print name) Date

_______________________________________________________ _____________________

Nokia representative(sign and print name) Date

Notes:




32/32


References

1. Operating MMS Center DN00148786

2. Internet Mail Gateway DN00148868

3. Nokia MMS Center Configuration Files

system acceptance tests

Documents