Website Test: Professional Learning page

[amanda-phet]

Website Test

Mentions: @mattpen @zepumph @chrisklus

Website link

• Turn on the PL feature flag: https://ox-stage.colorado.edu/admin/feature-flags
• Add some resources: https://ox-stage.colorado.edu/admin/professional-learning-resources
• See the filter page: https://ox-stage.colorado.edu/_m/en/teaching-resources/professional-learning (note, if you refresh, you will need to type in the /_m manually again)

Focus and Special Instructions

This is a new user-facing page with a PhET team member page to add resources. Please test out adding and viewing resources, not always taking the happy path.

The filter page code should be functional, but still has some polishes coming. If you see strange things across browsers, please note them in a comment.

Please report bugs or strange behavior in the Slack #website-qa channel.

Test Matrices

• Windows 11 + Latest Chrome (Tester = KW) (Time = 3)
• macOS + Safari (Tester = KW) (Time = 1)
• macOS + Firefox (Tester = KW) (Time = 1)
• iOS + Safari (Tester = VP) (Time = 2.5 )
• Chrome OS + Chrome (Tester = VP ) (Time = 3.5 )
• Windows 11 + Latest Chrome + Latest JAWS (Tester = KW) (Time = .5)
• Windows 11 + Latest Firefox + Latest NVDA (Tester = VP) (Time = 1.5 )
• macOS + Safari + VoiceOver (Tester = NS) (Time = .75)
• iOS + Safari + VoiceOver (Tester = VP ) (Time =0.5 )

User Stories

(include shortcut story links if appropriate)

• As a PhET educator, I need to have access to all of PhET's course offerings so that I can find the right one for my needs and build my teaching practice.
• As a PhET team member working with teachers, I need to easily point teachers to PhET's course offerings so that they get more uptake.

Acceptance Criteria

• Professional Learning page link added to the Teaching menu in navbar This is not available yet
• New filter page (Professional Learning with PhET) displays visible resources from admin page
• New admin page allows PhET team members to add and edit resources to be displayed on the filter page

---

For QA...

General features

What to Test

TODO: Ask Katie and Nancy and Chris and Matt to expand here if needed!

Accessibility features

What to Test

• Test all keyboard navigation inputs (if applicable).
• Test all forms of input with a screen reader (if applicable).

TODO: Ask Katie and Nancy and Chris and Matt to expand here if needed!

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?

Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

Here's a template for making issues:

  <b>Test Device</b>

  blah

  <b>Operating System</b>

  blah

  <b>Browser</b>

  blah

  <b>Problem Description</b>

  blah

  <b>Steps to Reproduce</b>

  blah

  <b>Visuals</b>

  blah

  <details>
  <summary><b>Troubleshooting Information</b></summary>

  blah

  </details>

Who should I assign?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?

You should:

1. Consult the QA Book.
2. Google it.
3. Ask Katie.
4. Ask a developer.
5. Google it again.
6. Cry.

---

[KatieWoe]

QA is done.
Issues reported in the website-qa Slack channel.