One-click test for signatures
When the filing status of a signature is Filed for verification or Filed, you can run a one-click test to quickly verify that the signature can be used to send SMS messages. No additional service fees are charged; you pay only for the sent SMS messages.
Overview
The one-click test for signatures verifies the availability of a signature with each carrier. When you run a one-click test, the system calls carrier APIs to send SMS messages and checks if the signature works correctly. This feature is available only in the console, not through any API.
If the test passes, the signature's filing status is updated to Filed.
If the test fails, the system automatically re-submits the signature for filing, and the filing status is updated to Filing. If the signature is already being filed with other carriers, the system waits for those processes to complete before re-submitting the signature to the carrier that failed the test.
Prerequisites
A signature must meet all the following conditions to use the one-click test feature:
The signature availability status is Available-Normal or Available-Abnormal. The latter excludes compliance issues that severely impact message delivery success rates.
NoteYou cannot use the one-click test feature if the signature has issues such as a mismatch between the signature and the organization's name, incomplete signature or qualification information, inaccurate qualification details, one person associated with multiple enterprises, or failing carrier compliance checks.
The filing result for at least one carrier is Filed for verification or Filed.
Currently, the one-click test is only available for the verification code message type. Notification and promotional messages are not supported.
Procedure
Access one-click test
Log on to the Short Message Service console.
In the left-side navigation pane, choose .
In the signature management list, find the SMS Test column and click the test icon for the desired signature.
NoteIf the icon is disabled, hover over it to view the reason. The signature must meet the conditions listed in the Prerequisites section to use the one-click test feature.
Start a test
In the Expand dialog box, click Expand to read the feature description, user agreement, and pricing information. You only need to click I acknowledge on your first use.
In the Product Type section, Captcha is selected by default and cannot be changed.
In the Carrier section, select the carriers you want to test. You can select a carrier only if its filing status is "Filed for verification" or "Filed" and it is not currently being tested.
Enter the mobile numbers for the selected carriers in the corresponding input boxes.
NoteRules for entering mobile numbers:
Each carrier has its own input box. A maximum of three input boxes are displayed for China Mobile, China Unicom, and China Telecom.
You can enter up to five mobile numbers per carrier network, separated by commas (,).
The system validates the mobile number format and checks if the mobile number matches the carrier.
You must use real mobile numbers. Do not enter invalid numbers.
Click Perform SMS Test.
Wait for test completion
After you submit the test task, the system starts the test. You can view the test progress and results on the Test Report tab.
Test results
The system dynamically calculates the pass criteria for a test. The following table describes the possible test results and their meanings.
Test result | Description |
Testing | The SMS test is in progress. Please wait. |
Test Passed | The signature's filing status with the corresponding carrier is updated to Filed. If the status was already Filed when the test was initiated, it remains unchanged. |
Test Failed | The system re-submits the signature for filing with the corresponding carrier. The signature's filing status is updated to Filing. |
Special mechanism for re-filing after a failed test: If a test fails for one carrier, re-filing is not triggered immediately. Instead, the system waits for the filing results (Filed, Filed for verification, or filing failed) from all carriers. It then triggers re-filing for the carrier that failed the test.
For example, if the test for China Mobile fails while the signature filing for China Unicom is in progress, the system waits for the China Unicom filing result before re-submitting the signature to China Mobile.
Test report
On the tab, you can view the test history for all carriers associated with the current signature.
The test report includes the following fields:
Field | Description |
Carrier tested | Each row represents a single SMS test for a specific carrier. |
SMS test result | Displays the status: Testing, Passed, or Failed. |
Task creation time | The time when the test task was successfully submitted, in |
Test completion time | The time when the test result was updated. A hyphen (-) is displayed if the test is in progress. |
Successfully sent messages | The number of SMS messages that were successfully sent during the test. |
Click View Test Report to see a detailed report that includes information such as the signature name, product type, carrier, test result, and filing status.
Pricing
The one-click test feature is billed based on the pricing for Messages in Chinese Mainland.
Test fees vary because the pass criteria are calculated dynamically by the system.
The maximum cost for each test task (defined by signature, carrier, and product type) is capped at the price of sending the maximum number of SMS messages that the system allows per carrier.
Charges may still apply even if a test fails.
Due to delays in receiving delivery receipts, billing for successfully sent messages may occur after the test is complete.
You can view the delivery records for test messages in .
Delivery records
The delivery records for messages sent via the one-click test feature can be viewed on the page. Note the following:
In the delivery records for one-click tests, the template code and serial number fields show a hyphen (-). Therefore, you cannot filter these records by template code or serial number.
You can only filter these records by signature.
In the mobile number list, a One-click Test tag identifies records generated by a test.
All mobile numbers, whether they are your own or internal Alibaba Cloud numbers, are masked for privacy (for example, 139****1234).
For one-click tests, the delivery records show only successfully sent messages. Failed delivery records are not displayed.
FAQ
Querying one-click test details with API
The QuerySendDetails OpenAPI operation requires a mobile number. Because one-click tests can use internal, masked Alibaba Cloud mobile numbers, you cannot query their delivery details by using this API. However, you can query the details if you use your own mobile number for the test.
Mobile number display in one-click tests
All mobile numbers, whether they are your own or internal Alibaba Cloud numbers, are masked in the console and in delivery records to protect privacy (for example, 139****1234).
Filing status update after a failed test
A failed test does not immediately trigger re-filing. The system waits for the filing results (Filed, Filed for verification, or filing failed) from all carriers before re-submitting the signature for the one that failed the test.
Am I charged if a test fails?
You may be charged based on the number of SMS messages actually sent. During the test, the system sends real SMS messages to perform the test. Regardless of whether the test passes or fails, you are billed for the messages sent. Additionally, due to delays in delivery receipts, you might be billed for a successful delivery even after the test has been completed.
Split billing for one-click tests
No. The one-click test feature uses a default internal Alibaba Cloud template. Users cannot see the template name or template code. Therefore, you cannot use this template for split billing.