2026-06-29 BTR Meeting notes

Test completion

As of today:

• Main test sheet: 95.6% (up from 83.1% on June 22)

• RBAC tests: 100%

• Frontend-base tests: 51.4% - @Adolfo Brandes mention in slack that we can ignore in this release.

Critical tests not yet executed (Core Product alignment: yes):

• TC-00113: Verifiable Credentials Setup & Integration

• TC-00173: "Learn more" help links in Studio pointing to Verawood docs

• TC-00203: Python Graders (Blocked) - was blocked because codejail was missing

• TC-00297: Custom Certificate (In progress)

For the critical tests not yet executed, @María de los Ángeles Aguilar will try to complete them herself if they're not too technical, and offered that the group can help if needed.

Failed tests to review (High priority, new for Verawood):

• TC-00517: Course Enrollment - Bulk Registration & Email Notification the related issue is already closed; María will update the status in the spreadsheet, with Jenna agreeing as long as it was actually tested.

• TC-00522: Course Grading - Single Learner Adjustments María was able to reproduce the issue correctly with @Maria Grimaldi help, documented each action, and Eddie responded. It's pending confirmation from Jenna or Chelsea to close it; Jenna committed to reviewing it today and closing it if it looks okay.

• TC-00539: Cohort-Based Content Visibility (related to blocker #600)

• TC-00556: Course Analytics - Course Tag Visibility and Filtering

• TC-00559: Course Analytics - Drill-Down Navigation to Course Dashboard

Failed tests (RBAC tab, related to blocker #603):

• TC-00569: Roles and Permissions tab

• TC-00575: Toggle public reuse of library content

• TC-00576: Course Staff permissions in Studio (assign button visible to users without permissions)

Release blockers

Current status per blocker:

• https://github.com/openedx/wg-build-test-release/issues/587: Missing backport to release/verawood. Asked Kevyn for support. Waiting on the frontend backport. Jenna was waiting to test it on the sandbox before closing, since it was deployed but not yet live there. She asked when the next sandbox deployment is happening (usually Mondays); Farhaan mentioned María had already pinged Ahmed for a push, so it might get updated today.

• https://github.com/openedx/wg-build-test-release/issues/588: Likely a missing configuration. Asked Ahmed for a re-deploy. Majo was able to reproduce it; waiting on her latest update. Jenna suspects it's a configuration issue that may already be fixed, but hasn't reviewed Majo's most recent response yet.

• https://github.com/openedx/wg-build-test-release/issues/600): PR opened. May not be a blocker since the cache eventually updates (~1h). Worth confirming.

• https://github.com/openedx/wg-build-test-release/issues/603: Draft PRs opened. WIP.

• https://github.com/openedx/openedx-authz/issues/34: Status update pending. Comment left on the issue. Resolution is on the frontend side; Majo assigned it to Diana, expected to close in the coming days.

• https://github.com/openedx/frontend-app-admin-console/issues/162: WIP. Deploying a solution for product to review. Assigned to @Maria Grimaldi

• https://github.com/openedx/frontend-app-admin-console/issues/163: WIP. Assigned to @Maria Grimaldi .

• https://github.com/openedx/frontend-app-instructor-dashboard/issues/212: Likely not a blocker - related to a listing improvement, not a core regression. Need to confirm with Chelsea and Jesse.
  
  

Go / No go

The release is not happening this week.

Here’s a proposal: async check-in on Wednesday morning to review the blockers, reclassify anything that no longer qualifies, and offer support where needed.

E2E!

Last update:

The E2E testing repository is being set up. There is a PR open with an initial ADR. Maintainers have been added (Ty Hob, Max Sokolski, Jesse Stewart, Peter Pinch).

How is this progressing? Is there anything the group can do to help move it forward?

The initial ADR is ready to be merged; he'll then coordinate with Max and Jesse on next steps. He suggested giving up part of this recurring meeting's time to discuss E2E once there are fewer release blockers to review, and will try to bring Ty, Max, or Jesse into next week's meeting (Monday), considering it a "quorum" if at least one of them joins. He noted that the Cypress tests are already organized with the same test IDs as the spreadsheet (which will help when migrating them to Playwright — the big piece of remaining work), though they haven't been updated in the last 2-3 releases. He also raised, as a future discussion topic, whether to automate the spreadsheet (e.g., having a failed test automatically open an issue or flag it on the sheet).