Dev test: Build-a-Molecule 1.0.0-dev.75

[Denz1994]

@ariel-phet , @arouinfar , build-a-molecule/1.0.0-dev.75 is ready for dev testing. This is the final dev-test cycle after code review. There were many refactors in the codebase and a couple of additional features added. 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

• 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.

Focus and Special Instructions

Special instructions include:

• Inspect hydrogen and borane molecules for any oddities. Build-in both the collection boxes, within the playground area, and 3D representation.
• Inspect order dependent molecule building. Details are provided in unable to create 4-carbon chain build-a-molecule#148 (comment)
• Test dragging molecules in and out of the buckets by specifically, clicking on the buckets. The expected behavior should resemble grabbing an atom by clicking on its bucket.
• Attempt the same bucket grabbing behavior (directly above) using multi-touch.

General Dev Test Platforms

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

Issues to Verify

• Unable to create 4-carbon chain

These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for QA then close the issue if fixed. If ready for review then leave open and assign back to the developer.

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.

---

[ariel-phet]

Current high priority after #505 is complete

[liammulh]

I did some brief testing using the instructions outlined in phetsims/build-a-molecule#148 (comment) on macOS + Chrome and macOS + Safari. Haven't seen any issues thus far.

[KatieWoe]

QA is done

[Denz1994]

Thanks for the work QA. I'll address the remaining issues and reassign them for verification.

[Denz1994]

It looks like there is only one issue open for this dev-test and it is awaiting review. I'm going to close this one. Thanks a lot QA.