Dev-Lite Test: Isotopes and Atomic Mass 1.2.0-dev.2

[jbphet]

Dev-Lite Test

Mentions: @Nancy-Salpepi, @AgustinVallejo

Simulation links

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

Test Matrix

• Tester 1 Tester = VP , Platform = Chromebook , Time = 1.5
• Tester 2 (Tester = NS, Platform = Mac + safari , Time = 1

Features included

• Dynamic Locale
• UI Sound
• Pan and Zoom

Focus and Special Instructions

This is the 2nd dev test for the 1.2 release of Isotopes and Atomic Mass. The first found several bugs and was also
built about a month ago, so the common code has changed a non-trivial amount since then. This test should be focused
on verifying that the bugs found in the first dev test have been fixed and that no new bugs have been introduced.

• Please check the QA credits and open a new issue if anything needs to be updated.

Issues to Verify

These issues should have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.

• Isotope buckets have too many isotopes and float in buckets isotopes-and-atomic-mass#136
• Isotopes reappear after switching elements isotopes-and-atomic-mass#135
• Slow loading when switching elements in Nature’s Mix (Mixtures screen) Chromebook isotopes-and-atomic-mass#131

(The other logged issues were verified by testing the main branch.)

---

For QA...

General features

What to Test

• Click every single button.
• Test all possible forms of input.
  • Test all mouse/trackpad inputs.
  • Test all touchscreen inputs.
• 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.
• Test all query parameters on all platforms. (
  See QA Book for a list of query parameters.)
• Download HTML on Chrome and iOS.
• Make sure the iFrame version of the simulation is working as intended on all platforms.
• Make sure the XHTML version of the simulation is working as intended on all platforms.
• Complete the test matrix.
• Don't forget to make sure the sim works with Legends of Learning.
• Test the Game Up harness on at least one platform.
• Check this LoL
  spreadsheet and notify AR or AM if it not there.
• If this is rc.1 please do a memory test.
• When making an issue, check to see if it was in a previously published version.
• Try to include version numbers for browsers.
• If there is a console available, check for errors and include them in the Problem Description.
• As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there
  is a problem.
• As the RC ends, please review the QA credits in the about dialog. If the QA credits are complete and correct, please
  add a comment in the RC test issue indicating so. If not, please open a new issue and specify what changes should be
  made.

---

Pan and Zoom

This sim supports pan and zoom with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test pan and zoom 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, pan and zoom 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.

---

[Nancy-Salpepi]

Memory Leak Test looks good!

[Nancy-Salpepi]

QA is done.

[jbphet]

Thanks QA team. I'll start the RC. Closing.