Closed
Bug 1426264
Opened 8 years ago
Closed 8 years ago
Check Leanplum's User Attribute Focus is Installed Logic is Valid
Categories
(Firefox for iOS :: General, enhancement)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
fxios | ? | --- |
People
(Reporter: jcollings, Assigned: SimonB)
Details
Farhan,
We have been using the user attribute "Focus Installed is Not True" to make sure we're sending campaigns to users who do not have Focus installed.
We've tested this in the past but can you re-test and validate that this logic is still working?
Thanks,
Jean
Reporter | ||
Comment 1•8 years ago
|
||
Hi Simon,
Can you include this in your QA test for 10.5 release? It's also not just Focus Installed, if you can verify these other attributes as well:
Klar Installed
Mailto preference
Signed In Sync
Telemetry Opt In
App version
Pocket Installed
Assignee: fpatel → simion.basca
Assignee | ||
Comment 2•8 years ago
|
||
Hi Jean,
I did a test run for the User Attributes logic. Found and logged only one issue Bug 1431438 related to MailTo preference, other than that everything seems to be ok.
In regards to the "Telemetry Opt In" I was not exactly sure what to look for, so I tested only the functionality of the "Send anonymous data" button with two scenarios:
1. Enabling the button should send telemetry data to the Leanplum dashboard (This can be observed by closing and restarting the app and looking that the "Number of sessions" is increased or by looking in the Leanplum Debugger)
2. Disabling the button should not send telemetry data to the Leanplum dashboard (This can be observed by closing and restarting the app and looking that the "Number of sessions" is not increased or by looking in the Leanplum Debugger)
You can find the link to the test here: https://testrail.stage.mozaws.net/index.php?/runs/view/7929&group_by=cases:section_id&group_order=asc
Reporter | ||
Comment 3•8 years ago
|
||
Thank you Simon! I will go ahead and close this bug.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•