User:Etonkovidova (WMF)/GrowthExperiments
Growth team projects - GrowthExperiments aim to help new users to start editing. Other team's project include Mentorsship and CommunityConfiguration. For general info/documentation see Growth team projects summary.
General QA testing notes
[edit]For testing GrowthExperiments features by creating a new user account on a wiki where the testing will be run. Special:Homepage features (part of GrowthExperiments) are enabled on all wikis for new accounts. To enable (or disable) the features manually - Special:Preferences-User profile Newcomer editor features.
Not all wikis have Menotrship features available, and the types of Suggested edit tasks on Special:Homepage variy depending on a wiki. For Suggested edit tasks check Growth/Deployment table and ask the team where testing should be done.
Feature flag testing
[edit]Growth team explores new approaches to engage new users in editing. Often features deployed either as A/B testing (or testing of groups of users in differently proportional segments) or the features have a feature flag to test them in production environment before turning on for everyone (see Growth team page with the list of wikis where Growth experiments have been deployed). Using Javascript snippets (URL parameters) in the a browser Console might help to optimize testing. The following cases illustrate when either javascript snippets or URL parameters could be used :
- different variants of features (e.g. instead of creating new users every time you need to take a look at different UI layouts)
- re-test features that are presented only one one-time (or limited times) to new users (e.g. Welcome survey)
Please refer to Growth team projects page and to the Growth team for current projects testing needs.
Features testing
[edit]Community Configuration
[edit]Growth - Community Configuration
- see Special:CommunityConfiguration on testwiki
- to edit Special:CommunityConfiguration, you need an admin user account
- Special:CommunityConfiguration page has options to control (enable/disable) few of GrowthExperiments features
Welcome survey
[edit]Growth - Welcome survey documentation
- create a new account
- for an existing account, add Special:WelcomeSurvey?_group=exp2_target_specialpage to url to see the Welcome survey UI
Homepage
[edit]- new users should be redirected to automatically enabled Special:Homepage after Welcome Survey
- for existing accounts: enable Special:Homepage from Special:Preferences in User profile tab -> Newcomer homepage option
Check the presence and functionality of the following modules on Special:Homepage
- Intro module
- Mentorship module
- Help module
- Impact module
- Suggested Edits (SE) module
Help panel & Guidance panel
[edit]Help panel
[edit]New users accounts should see Help panel when they click on Edit; Help panel is present in reading mode in some namespaces.
- Visit User talk or “User page - the Help panel should be present
- Visit any article, click on Edit - the Help panel should be present
You can post test questions and check the whole functionality of Help panel on betalabs wikis and testwiki.
Guidance panel
[edit]Guidance panel appears for users who click on suggested article in Suggested edit module on Special:Homepage.
- Guidance panel is present in reading mode on suggested edit articles
- The post-edit dialog is displayed for users who publish edits .
Mentorship features
[edit]- to become a mentor - Special:EnrollAsMentor
- for all-mentor related activities Special:MentorDashboard (access only for mentors)
- to see list of mentors and their status - Special:ManageMentors
There are also couple of useful calls:
- to see a mentor for a user - {{#mentor:TestUser}}
- to see all mentees for a given mentor - TestMentor - https://test.wikipedia.org//w/api.php?action=query&format=xml&gemmmentor=TestMentor&list=growthmentormentee
Add link structured task
[edit]Growth - Personalized first day/Structured tasks/Add a link
Mockups: Desktop - [1], Mobile - [2]
Test environment: Presently the testing can be done on beta cluster - cswiki on beta cluster. In production the feature is displayed on testwiki.
For enabling the Homepage - refer to Homepage section.
Add an image to an article/an article section structured task
[edit]Regression/smoke testing
[edit]Pre-deployment testing
[edit]- the testing is done in betalabs; verify with the team which beta wiki should be used for testing.
- review QA column on Growth Team Current sprint workboard to finish QA verification before features would be deployed
Post-deployment testing
[edit]- check the GrowthExperiments features functionality on testwiki
- check Growth logstash dashboards for errors
Instrumentation testing
[edit]Several schemas are associated with Newcomer experience and Homepage features - HomepageModule, HelpPanel , EditorJourney, and EditAttemptStep. The following steps are applicable to all of the schemas checking (substitute the required schema's name). For a general QA practices for instrumentation testing, refer to Testing Instrumentation.
Before testing
[edit]- read about event logging and possible updates/changed access etc - Analytics/Systems/EventLogging/TestingOnBetaCluster
- read a schema description (e.g. Schema:HomepageModule) to understand what actions to perform to trigger eventlogging events
- create a test outline (several user workflows) to make sure that all events from a schema would be recorded
In a browser (client side testing)
[edit]The testing with the console snippets can be done in beta cluster and in production.
- enable your browser's devtools and enable "persistent log" in the Console
- use the following snippet (credit to User:KHarlan (WMF)
mw.trackSubscribe('event.HomepageModule', console.log);
- perform the actions that trigger eventlogging and compare with the info documented in the relevant schema description