RC test: Vector Addition 1.0.0-rc.1
Closed this issue · 9 comments
@KatieWoe, @arouinfar, vector-addition/1.0.0-rc.1 is ready for RC testing.
This release does not include PhET-iO or a11y.
Document issues in https://github.com/phetsims/vector-addition/issues and link to this issue.
Assigning to @ariel-phet for prioritization.
General RC Test
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.
- 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
- If there is a console available, check for errors and include them in the Problem Description.
Issues to Verify
There are no specific issues to verify; all known issues have been addressed.
Link(s)
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:
- Consult the QA Book.
- Google it.
- Ask Katie.
- Ask a developer.
- Google it again.
- Cry.
1 minute.
Snapshot one is at the very start, snapshot two is one minute in, etc.
Moving to current top priority
QA is done here. Hoping to finish equations sim tomorrow.
Issues to be verified, to be copy-pasted into the next QA RC issue.
- credits
- Toolbox arrow icons should have rectangular or more expanded pointer areas
- 0 vector has larger pointer area
- Upside-down f vector when d vector and e vector cancel
- Assertion failed: Not handling arcs with start/end angles that show differences in-between browser handling
- labels overlap for vector <-x,0>
- incorrect (solid) leader lines when sum vector is made visible
- missing leader line when sum vector component is zero
- grabbing the origin manipulator clears the selected vector