Android - A/A Test
Description
Goal:
Setup a basic A/B test using Firebase A/B testing that we can use to validate downstream analysis. The first test I would like to run is an "A/A" test. In this test we will not change anything about the user experience, however, we will put in the skeleton of the test and emit data as if there was a real test running. We can then make sure our analysis pipeline is correctly configured to analyze the data from future tests.
Background:
I configured a basic experiment in Firebase. You can find it here.
Acceptance Criteria:
Build on the work done in the spike.
The default value for the parameter should be “Not set”.
Emit an event with different properties depending on the value of the remote parameter.
The above event should be emitted when the user views the course outline screen in the app.
We want these changes to be included in the 2.20 release.
Emit an event when the user successfully completes an enrollment in a course from the mobile app (after login etc)
Steps to Reproduce
Current Behavior
Expected Behavior
Reason for Variance
Release Notes
User Impact Summary
Activity
- thanks for calling out the duplicate. I think these tickets are very similar, would it be too disruptive to tackle this one instead of the other one?
Sure, lets consider this one
The above event should be emitted when the user views the course outline screen in the app.
As mention above event should be trigger on course outline screen, so there should be the course id in the event. Any thoughts?
Emit an event when the user successfully completes an enrollment in a course from the mobile app (after login etc)
We already trigger an event on successfully completes an enrollment in a course named “Course Enroll Success”.
We already trigger an event on successfully completes an enrollment in a course named “Course Enroll Success”.
Excellent!
As mention above event should be trigger on course outline screen, so there should be the course id in the event. Any thoughts?
Great, please add the course ID to the event in a field called “course_id”.
To be clear, no need to create a new enrollment event, we can use the existing one.
Assignee
Reporter
Labels
Reach
Impact
Platform Area
Customer
Partner Manager
URL
Contributor Name
Groups with Read-Only Access
Actual Points
Category of Work
Platform Map Area (Levels 1 & 2)
Platform Map Area (Levels 3 & 4)
Story Points
Sprint
Fix versions
Priority
