We're updating the issue view to help you get more done. 

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.

1 2 3 4 5 6 String aaExperimentGroup = mFirebaseRemoteConfig.getString("aa_experiment"); Analytics.with(context).track("Mobile Experiment Evaluated", new Properties().putValue("experiment", "aa_experiment") .putValue("group", aaExperimentGroup) .putValue("user_id", PUT_EDX_USER_ID_HERE) );
  • 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)

1 2 3 4 Analytics.with(context).track("Mobile Enrollment Completed", new Properties().putValue("course_id", PUT_COURSE_ID_HERE) .putValue("user_id", PUT_EDX_USER_ID_HERE) );

 

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Status

Assignee

Farhan Arshad

Reporter

Gabe Mulley

Labels

None

Reach

None

Impact

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Stakeholders

None

Story Points

2

Fix versions

Priority

Unset