| A | B | C | D | E | F | G | L | M | Q | T | V | W | AF | AG | AH | AI | AJ | AK | AL | AP | AQ | AR | AS | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Timestamp | Email Address | What is your name? | Which type of request are you submitting? | What is the name of the job(s) to be run? | URL of a Google Doc with clear instructions on what the tester needs to do: | Please give a clear description of what your job does and why you want to test it. | (Optional) Anything else you'd like to tell us? | If the job run fails midway, what should we do (after cancelling the job) to revert the system back to how it was? | How do the job(s) or feature interact with the datastore? | Link to the PR which needs to be deployed to the backup server for testing: | Please confirm the following: | Is this just an audit job(s) run? | What is the name of the job to be run? | Which server(s) should this job be run on? | Why does the job need to be run? | What is your GitHub username? | (Optional) Anything else you'd like to tell us? | URL of a Google Doc with clear instructions on what the server admin needs to do. | I have confirmed that the new CUJs for this feature have been added to the overall CUJ list. | Has the job doc been fully approved? This must be marked "Yes" before any testing is done. | Responsible Server admin Once you assign yourself, please leave a review hold on the PR so that other reviewers can approve it without risking it getting merged prematurely. | Status Once this is marked "successful" and all 3 columns are green, you can transfer this row to the "Jobs that have passed testing" sheet. Alternatively, If the job doesn't need to be run in prod (see column U), transfer it to the "Rejected" sheet. | Notes | |
2 | 6/11/2025 0:53:17 | masterboy376@gmail.com | Sambhav Kaushik | Run a newly-implemented job on the backup server (the job is not in develop yet) | AuditGenerateContributorAdminStatsJob GenerateContributorAdminStatsJob | https://docs.google.com/document/d/1-L-HMw2Ob0dx-W4AemIQ42qwA3XM8gPf4DtvmZp5UDg/edit?usp=sharing | GenerateContributorAdminStatsJob generate total contribution stats for contributors/reviews using existing contribution stats models. AuditGenerateContributorAdminStatsJob is a audit job for GenerateContributorAdminStatsJob. | The actual changes are made to the datastore at one instance. Hence, don't need to any reverts if the job fails midway. | It creates, modifies and/or deletes datastore entities. | https://github.com/oppia/oppia/pull/22765 | I have tested the new job(s) manually by running it from the /release-coordinator page on my local dev server., In the "success" case, each job yields aggregate output (like the total number of files migrated)., In all possible "failure" cases, each job yields debug/error output (like the ID of an exploration that couldn't be migrated and the reason why)., The PR includes backend tests for both the success and failure cases., All CI checks pass on the PR that implements the job., The PR can be merged into develop immediately once the job has run successfully (to avoid skew arising from subsequent changes to develop). | No (run on both backup and production server) | masterboy376 | https://docs.google.com/document/d/1-L-HMw2Ob0dx-W4AemIQ42qwA3XM8gPf4DtvmZp5UDg/edit?usp=sharing | Yes | Sambhav | Run finished with errors | Waiting for a re-run | |||||||
3 | 6/13/2025 3:53:11 | ankitasonu24@gmail.com | Ankita Saxena | Test implementation of redishost as a storage model | ankita240796 | https://docs.google.com/document/d/19DeEzw7Ar_d3iF5_dcs-yAnrdOO1dL7ZpPupVwhl14E/edit?usp=sharing | Yes | Ankita | Waiting for run | Ankita will run this on 24 Sept (she is busy before that). | |||||||||||||||
4 | 10/4/2025 3:34:11 | nikhil.agarwal.2019@gmail.com | Nikhil | Test voiceover autogeneration functionality | Nik-09 | https://docs.google.com/document/d/1DH3IRZ8YNy9_tWar5fYmCbCj4HToFjE7kTZHTJ9A_xQ/edit?tab=t.0#heading=h.af4ah3j6d4cr | Yes | Nikhil | |||||||||||||||||
5 | 10/11/2025 5:39:24 | ayushrochlani0405@gmail.com | Ayush | Run a newly-implemented job on the backup server (the job is not in develop yet) | AuditStoryMigrationJob, MigrateStoryJob | https://docs.google.com/document/d/1Y3uNyNf-b027KDcEOD6i46EmiX4IsZOYQKPiMQ9pT-g/edit?tab=t.0#heading=h.gi56acy4r9be | This job fixes story node's destination_node_ids and relinks disconnected nodes. | This job makes changes to the datastore at the end. If the job fails midway, no changes will have been made to the system. This job is idempotent because it depends on story_contents_dict['nodes'] while we are only modifying node['destination_node_ids'], so it is safe to run multiple times. | It creates, modifies and/or deletes datastore entities. | https://github.com/oppia/oppia/pull/23382 | I have tested the new job(s) manually by running it from the /release-coordinator page on my local dev server., In the "success" case, each job yields aggregate output (like the total number of files migrated)., In all possible "failure" cases, each job yields debug/error output (like the ID of an exploration that couldn't be migrated and the reason why)., The PR includes backend tests for both the success and failure cases., All CI checks pass on the PR that implements the job., The PR can be merged into develop immediately once the job has run successfully (to avoid skew arising from subsequent changes to develop). | No (run on both backup and production server) | aroch17 | ||||||||||||
6 | |||||||||||||||||||||||||
7 | |||||||||||||||||||||||||
8 | |||||||||||||||||||||||||
9 | |||||||||||||||||||||||||
10 | |||||||||||||||||||||||||
11 | |||||||||||||||||||||||||
12 | |||||||||||||||||||||||||
13 | |||||||||||||||||||||||||
14 |