10 min

Community Test Plan

 Dean Jay Mathew

•  How do we manage failed tests as they are getting fixed?

  • Add an “Issue link” column

  • Each failed test should have at least one open issue against it

• How can people suggest tests to add?

  • Create an open tab in the sheet where anyone can make suggestions of tests to add.

• DevOps tests are missing and Dean will need some help from the people in this group

• How do we manage tests that are not run on the “official” test instance?

  • Testing should happen on the official instance

  • Changes to the instance configuration can be made as PRs here

What to do for discussions, authentication, and other MFEs?

Peter Pinch

• What’s the process to add those MFEs

• https://github.com/openedx/build-test-release-wg/issues/141

  • Only appropriate as an optional

  • Should not be enabled by default but it could be an opportunity for people in the community to familiarise themselves with it.

• https://github.com/openedx/build-test-release-wg/issues/142

  • Ready to be added to the release.

  • May be worth adding to the Tutor MFE plugin for this release, not sure.

  • Kyle will follow up.

• https://github.com/openedx/build-test-release-wg/issues/145

  • Adolfo said in the previous meeting that course authoring MFE

• All the officially supported MFEs support node 16.

Is there a way to diff the settings and flags in maple and nutmeg

Peter Pinch

I’d like to have a section in the release notes on new settings and flags

The settings on the Zoom meeting: attendees can’t screenshare

Ned Batchelder (Deactivated)

Can we take a look a the list of repos for Nutmeg?

Kyle McCormick

I know of at least 2 that could probably be excluded: testeng-ci and edx-e2e-tests.