Dev test: Build-a-Molecule 0.0.0-dev.23

[Denz1994]

@ariel-phet and @arouinfar build-a-molecule/0.0.0-dev.23 is ready for dev testing. The sim is focused around users building molecules and dropping them into various collection boxes. Please note this version is still in development and is the first dev-test cycle. It should not be shared with clients. The purpose of this dev test is to focus on performance on an assortment of devices and platforms.

Additionally, performance concerns may help with deciding what to do regarding phetsims/build-a-molecule#109.

Document issues in https://github.com/phetsims/build-a-molecule/issues and link to this issue.

Assigning @ariel-phet for prioritization.

General Dev Test

What to Test

• Notice any outstanding delays in the startup time of the sim on multiple platforms and browsers. This may offer insight on How to mange molecule data set? build-a-molecule#109
• Note any performance lag when many molecules are on screen. This means dragging molecules and breaking bonds, while there are many molecules on-screen.
• Focus on multi-touch interactions where possible.
• Click every single button.
• If there is sound, make sure it works.
• Play with the sim normally.

Focus and Special Instructions

This testing cycle should be focused on performance and multi-touch interactions. Please note any concerns regarding sim load times and any laggy behavior when many molecules are present in the play area or separating. Additional, bugs found during testing should be reported as usual. Thanks in advance QA!

General Dev Test Platforms

• Latest macOS, Chrome and Safari
• Latest iOS, Safari
• Windows 10, all browsers
• Latest Chrome OS, Chrome

Link(s)

• Build-a-Molecule

---

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]

Typical graphical issues found in Edge. No action probably needed. However, instead of just pieces briefly disappearing, sometimes hidden buckets appear as well. @ariel-phet does this need more attention?

[KatieWoe]

QA is done

[Denz1994]

Closing this issue, since a new dev test has been opened. Thanks for the work QA.