Dev Test: Build a Nucleus 1.0.0-betaDecay.11

[Luisav1]

Dev Test

Mentions: @chrisklus @ariel-phet @arouinfar

Simulation links

• github repository for issues
• phet top level directory
• sim: all_phet.html

Test Matrix

Please include all (non-screen reader) feature testing in these records if applicable.

• Latest macOS, Safari (Time = 3.5 hrs)
• Windows 10, Chrome (Time = 3)
• Windows 10, Firefox (Time = 2.5 hrs)
• Latest iOS, Safari (Time = 1.5)
• Windows 11, Chrome (Time = 4)

Light testing, or optionally skip if time crunch:

• Latest macOS, Chrome (Time = )
• Latest Chrome OS, Chrome (Time = )

Features included

• PhET-iO
• Alternative Input
• UI Sound
• Sonification
• Description
• Voicing

Focus and Special Instructions

A nuclide is an atomic species defined by the number of protons and neutrons it has in its nucleus. Everything in the simulation, the Symbol, the half-life readout, and the available decays, depends on the nuclide built. Only unstable nuclides decay but there may be unstable nuclides with decays not represented in this simulation or with unknown decays.

The half-life of an unstable nuclide may also be unknown due to missing data.

Here is the nuclide data table of all nuclides represented in this simulation. A visual representation of the chart is here, although this version is a bit outdated as it doesn't have all the nuclides known of today.

It would be good to test a few random nuclide samples to make sure the half-life readout and the available decays are correct, and that the decays are functioning correctly.

When a nuclide that does not exist on Earth is built, the simulation is in a frozen state for one second, where all the spinners and the nucleon creator nodes are disabled but the nucleons (protons and neutrons) in the nucleus are still enabled, before returning to the usable state it came from. Please look out for getting stuck in a frozen state. For example, an alpha decay on Beryllium - 6 (4 protons and 2 neutrons) results in Helium - 2 (2 protons and 0 neutrons), a nuclide that does not exist, so we handled that case separately.

Thanks! Let me know if you have any questions.

---

For QA...

General features

What to Test

• Click every single button.
• If there is sound, make sure it works.
• Make sure you can't lose anything.
• Play with the sim normally.
• Try to break the sim.
• Try to include browser version numbers
• If there is a console available, check for errors and include them in the Problem Description.
• Run through the string tests on at least one platform, especially if it is about to go to rc.
• Check the Game Up harness on one platform.

---

PhET-iO features

What to Test

• Make sure that public files do not have password protection. Use a private browser for this.
• Make sure that private files do have password protection. Use a private browser for this.
• Make sure standalone sim is working properly.
• Make sure the wrapper index is working properly.
• Make sure each wrapper is working properly.
• Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
• For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
  sure the simulation loads without crashing or throwing errors.

---

Accessibility features

What to Test

• Specific instructions can be found above.

• Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
  a list of features that may be supported in this test:

  • Alternative Input
  • Interactive Description
  • Sound and Sonification
  • Pan and Zoom
  • Mobile Description
  • Voicing

• Test all possible forms of input.

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

Screen Readers

This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

• Windows 10 + Latest Chrome + Latest JAWS
• Windows 10 + Latest Firefox + Latest NVDA
• macOS + Safari + VoiceOver
• iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information

We are tracking known screen reader bugs in
this Google Document. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation

This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.

Magnification

This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.

---

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]

Calling QA here

[Luisav1]

Closing since I all issues were reviewed.