[Anas12091101]

Description

Related: https://github.com/mitodl/hq/issues/13163

When a course sets a proctoring escalation email, the proctored exam error page and the review result emails ask learners to contact that address. The onboarding pages don't: they show the provider's integration_specific_email, or the site-wide CONTACT_EMAIL when the provider has none. So a learner whose onboarding is missing, pending or rejected is sent to general site support instead of the course team that chose to handle proctoring questions.

This PR makes both places that build integration_specific_email use the course's escalation email when one is set, falling back to get_integration_specific_email(provider) as before:

• the proctoring settings API (/api/edx_proctoring/v1/proctored_exam/settings/exam_id/<id>/), used by frontend-lib-special-exams in the learning MFE
• the student view context used by the LMS onboarding templates

Each already looks up the escalation email for proctoring_escalation_email, so it is fetched once and reused.

Courses without an escalation email see no change. For a provider that requires one, such as Proctortrack, every course has one, so its onboarding pages will now show the course team's address instead of the provider or site address.

Testing

Automated: pytest src/edx_proctoring/tests/test_mfe_views.py src/edx_proctoring/tests/test_student_view.py -k "escalation_email or integration_specific_email"

Manual:

1. Set up a course with a proctored exam and an onboarding exam, using a provider with requires_escalation_email: True in PROCTORING_BACKENDS (for example Proctortrack).
2. In Studio, go to Pages & Resources → Proctoring, set Escalation email to course-team@example.com and click Save.
3. As a verified learner with no onboarding profile, open the proctored exam in the learning MFE.
   → "You must complete an onboarding exam before taking this proctored exam" now ends with "contact course-team@example.com". Before this change it showed the site's CONTACT_EMAIL (or the provider's integration_specific_email).
4. Open the onboarding exam.
   → "Please contact course-team@example.com if you have questions."
5. GET /api/edx_proctoring/v1/proctored_exam/settings/exam_id/<exam id>/
   → integration_specific_email is course-team@example.com.

Pre-Merge Checklist:

• Confirmed Github reports all automated tests/checks are passing
• Approved by at least one additional reviewer

[openedx-webhooks]

Thanks for the pull request, @Anas12091101!

This repository is currently maintained by @openedx/openedx-unmaintained.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.