Test coverage:

This test will confirm your Alias mechanism is working as expected. The test will be divided into 2 tests:

Note: you will need to integrate the Alias mechanism into your app in order for you to use it.

Basic Test procedure:

Note: The majority of Alias mechanism implementation is using the application login process to initiate the 'set Alias' API call. If as a part of your SDK integration you are assigning an Alias automatically when the application is installed,

please make sure to follow the set Alias API call when you are launching your app for the first time.

Expected results:

The following requests and their respective responses should be successfully reported by Charles.

Each request should return a response code of 200 indicating the call was successful.


Example for Set Alias API Call:
Request:


Response:


Advanced Test procedure:

Expected results:



Logs

IOS

Setting new Alias

[Appoxee Debug] Starting Alias update operation...
[Appoxee Debug] Starting Alias fetch operation...
[Appoxee Debug] Alias fetch operation completed.
[Appoxee Debug] Alias update operation in progress... value is being updateded with Appoxee Servers.
[Appoxee Debug] Alias update operation completed.


Setting the same Alias

[Appoxee Debug] Starting Alias update operation...
[Appoxee Debug] Starting Alias fetch operation...
[Appoxee Debug] Alias fetch operation completed.
[Appoxee Debug] Alias value did not change, aborting update.


Android (logcat)

Setting new Alias

D/Appoxee SDK﹕ updateDeviceFields_SQS Params: {"set":{"alias":"testalias"}}


Setting the same Alias

I/Appoxee SDK﹕ setDeviceAlias() Called
D/Appoxee SDK﹕ setDeviceAlias Success