SMS Test Plan

Connections To Gateways

• mBlox - xml#.mblox.com these are all connected on Port 8180.
• Zamano - mmg.zamano.com Port 80
• MXTelecom - sms.mxtelecom.com Port 80
• Dialogue - sms.dialogue.net Port 80

Test Plan

The following test plan is used to verify that all systems within the SMS Module are functioning correctly, and should be performed after every major update to the code, and every installation.

1. Pending API
• This file must be kept up to date to replicate the exact messages that are sent in from the gateway companies.
1. Create a pending message using the incoming_test.php script.
2. Pending message creation for mBlox
3. Pending message creation for MXTelecom
2. Test Service Creation
1. Create 3 services for each service Type - Normal / Content / Chat. Label as such.
2. Create a keyword on each service label them normal / content / chat to fit in with the service type also.
3. Create another keyword on the Normal service that is on a different short code. I.e. call this 'normal89099'
4. During testing it is advisable to change the settings for free messages and multiple signups.
3. User and options generation
• When an incoming message is detected the script will create the user and assign that user to the service, if the user is already created then the service will be added, if the service is already found and Multiple Services check box is set to off then no service will be appended.
1. Firstly send in the Keyword 'normal', make sure no actions are assigned.
2. This will enable the easy debug of the user and options generation.
3. Clear all the users and test, we should see a New user, several new options and the link from customer to service generated.
4. Re-test - no user or options should be created, if multiple services is enabled then the customer should be signed up for the service twice.
4. Chat Service Testing
• Each short code may have multiple chat services, but one customer can only be a member of one chat service on a single short code. The reason for this is the free text nature of a chat service. Initially a customer must send in an activation keyword to subscribe, after that they can send in any message and expect it to go through to chat. This means that we must exclude the customer from the likelihood that during there chat messages they will send in another service keyword.
1. Send in the keyword 'Chat', this should initially subscribe the customer to the service
2. Need to see an incoming message logged with the correct user, service and keyword IDs and correct match action. I.e. MATCHchat
3. Outgoing welcome message should be seen.
4. Service logged in customer services table.
5. On subsequent messages the message should get logged straight into the incoming message table no other actions are needed.
6. If the same customer sends a message in on a different short code then this should be processed as normal.
7. Certain service may require the message to be forwarded back into the MX Telecom chat platform test that this action is being activated and the messages are being forwarded correctly.
5. Chat Centre Testing
• When messages are entered into the Chat centre the operators should have the ability to log in and view and send replies to these messages.
1. Check the operator log in and service screens are correct.
6. Message Actions
1. Create all actions within the test service and check that the actions are created properly with the correct parameters for each.

External Links

• SMS
• Accounts
• Actions
• Blacklist
• Chat
• Delivery
• Guidelines
• Incoming
• Outgoing
• Location Services
• MX Telecom Statistics
• Network Codes
• WAP
• US Short Codes
• Payouts
• Permissions
• Testing
• To Do
• Glossary