chromium-dashboard
chromium-dashboard copied to clipboard
OT Creation/Activation endpoints need to be started and tested
The cron jobs for trial creation and activation need to be formally added and tested on staging. Note that sending a trial creation request will only be sent to the Origin Trials API on staging (https://cr-status-staging.appspot.com/) and not locally, because the user sending the request must be the Chromestatus service account for staging or prod. Note: You may want to increase the frequency of the “activate origin trials” cron job in order to test it, which is set to run only once a day. In order to test, Follow these steps:
- Put a version of staging up on Chromestatus that has the cron jobs running. Create a new feature on staging (One that has an Origin Trial option, like “New Feature Incubation”)
- Mark all gates in the Origin Trial section as “Approved” or “N/A” (you should be able to do this by yourself as an admin).
- This should allow the “Request trial creation” button to become available, which will bring you to the OT creation form.
- Fill out the OT creation form entirely and submit. This will send the request to the Origin Trials API. If an error occurs, it should be caught by error monitoring and will send an email to webstatus-eng.
- Troubleshoot any issues with the request.
- When a creation request is successful, the trial should be flagged for creation. The cron job should run and pick up the flagged trial for creation.
- Troubleshoot the cron job with any issues.
- Create a feature and set the OT start milestone to be in the future. Proceed to submit the trial creation request. This should create the trial but not yet activate that trial. Check that the ot_activation_date field has been set properly in the database for the stage.
- If the activation date is set properly, manually update the value in the database to be at a date that is before the current date. This should trigger the trial to be activated during the next activation cron job run.
- Check the cr-status-staging-emails group to see if notifications about the process are being sent properly.