Willow release testing

Aperta
  • Qualcosa non va?
#609 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@mariajgrimaldi ci sta già lavorando.

Dal 6/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

willow

The Willow BTR test sheet needs to be brought in line with the current AuthZ work. Some existing descriptions are out of sync with changes that have landed, and Milestones 2 and 4 still need test coverage.

This issue groups the release testing work so the updates and missing coverage are tracked together. The detailed changes will be handled in the issues below.

Tracked work

  • #594, add test cases for Course Editor and Course Auditor in Milestone 2
  • #502, update the issue description to reflect the current Milestone 4 scope and add test cases for the Instructor Dashboard work
  • #608, review the existing BTR tests, including the Verawood cases, and update descriptions that are out of sync with the current status and recently landed changes

Acceptance criteria

  • Existing test descriptions match the AuthZ behavior included in Willow.
  • Changes flagged by E2E as needing updated descriptions are covered.
  • Milestone 2 has test cases for Course Editor and Course Auditor, including their allowed and restricted actions.
  • Milestone 4 has test cases for the Instructor Dashboard permissions and role boundaries included in the current scope.
  • Verawood test cases are reviewed against the current status, and cases that no longer apply are updated or removed.
  • Each test case includes clear preconditions, steps, and expected results.
  • Any product or implementation gap found while updating the tests is tracked in a separate issue.
Lingua principale
Python
Stelle
0
Fork
10
Merge medio
5g 9h
PR unite (30g)
24

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openedx/openedx-authz

Tutte le issue di openedx/openedx-authz

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.