Using the SMStestframe tool

 

 

msXsms comes with a utility called SMSTestFrame.EXE which is copied to disk  during setup on the msXsms server.  A number of simple scripts are provided to allow SMTP messages to be generated as though they were being sent from Outlook, Business Applications or Network Management systems.

This may be useful for testing where Outlook may already exist to view SMS confirmations being delivered to Outlook mailboxes.

 

Location of the SMStestframe

 

 

SMSTestFrame.exe is the utility program which can send test messages from the GUI or can process scripts to automate a series of tests..

Folder - Logs, contains log files of your actions.

Folder - Script, contains some sample scripts which you can copy to create your own for testing purposes.

 

Overview and approach to testing

 

The test frame simulates messages from business applications and Outlook users or even network management systems.

Setting up simple scripts using notepad, can greatly improve your ability to set up repeatable testing procedures for initial implementation and upgrades of msXsms enterprise software.

 

msXsms services are represented by white boxes in the diagram above.

Consider setting up a number of different mailboxes and assigning permissions to allow Outlook to open all of the mailboxes from one profile.  This will greatly improve your ability to see that confirmations and inbound SMS messages are going to the correct destination.

 

Scripts for use in SMS testing

 

A series of examples are provided as part of the installation.

Scripts do not support keyword generation in the body.

Let’s look at a sample test script supplied with msXsms. The highlighted comments are not actually in the script but are shown to help you understand how easy it is to set up your own scripts. 

 

* this a test script for msXsms enterprise (SMSTESTFRAME.EXE)

 

* version 1.7.03

* BNS testing

 

* Preparation notes:

* Set up in Exchange a new mailbox called App1

* Set up in Exchange a new mailbox called App2

* Set up in Exchange a new mailbox called ReplyAddress1

* Set up in Exchange a new mailbox called InboundAddress1

* assign full permissions to each of these mailboxes to your Outlook account (eg: Administrator)

* Login to Outlook using Administrator (or whatever Account) and open these additional mailboxes using the Tools, Account Settings,Change, Advanced)

*

* additional tests should be done which test functionality of application default controls when the apps send simple messages. ie: the application control defaults are applied first before any user provided over-ride keywords.

*

*

 

* Count must equal the number if TestSeries entries in this script

 

[Series]

Count=3  (see above note)

 

**********************************************************************************************************

* test series #1

* Simulation of Outlook user sending a short message 

*

***********************************************************************************************************

[TestSeries1]

Host=192.168.1.25 (This is your Exchange Hub Transport server. Make sure you setup permissions on a receive connector to allow SMTP messages to be sent to it)

Port=25

SenderEmail=administrator@f2company.com  Use any account for testing

RecipientEmail=614xxxxxxxx@f2company.sms  This is the destination SMS address

Subject=This is an SMS message created by test script to simulate Outlook users sending

Body=

iteration=1  (This is how many times the message is to be sent, note duplicate messages not allowed, see below for more information)

 

 

**********************************************************************************************************

* test series #2

* Simulation of Outlook user sending 234 characters which will generate 2 SMS messages dumped 9 lots of a to z

*

***********************************************************************************************************

[TestSeries2]

Host=192.168.1.25

Port=25

SenderEmail=administrator@f2company.com

RecipientEmail=61412869531@f2company.sms

Subject=abcdefghijklmnopqrstuvwxyzabcdefgh*jklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghi*klmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabc*efghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz*bcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz

Body=

iteration=1

 

 

**********************************************************************************************************

* test series #3

* Simulation of Outlook user sending 5 SMS messages

* this is a series of unique iterations (%1 is replaced by a numeric value to make the sms msg unique

***********************************************************************************************************

[TestSeries3]

Host=192.168.1.25

Port=25

SenderEmail=administrator@f2company.com

RecipientEmail=61412869531@f2company.sms

Subject=Test sms message series 3 %1    (%1 creates a unique message by adding a counter)

Body=

iteration=5

 

Using the SMSTestframe

The following example shows how the GUI can be used without using a script to send 1 or more messages via SMTP to Exchange server as though a user or application send the message.

 

 

Your message should be delivered via Exchange Send Connectors to the queue in the folder structure below.

 

 

 

note: To prevent msXsms’s submission service processing the .EML files, stop the msXsms Submission Engine and System Attendant. This will allow you to follow the message flow through the system.  

 

Opening one of the messages reveals the unique message count added to the end of the subject.

 

Confirmations will be sent to the Sender’s Email address.  Open Outlook to open the sender’s email address to view the confirmations.

 

 

Create your own Knowledge Base