Collecting data for each of the available variables across different launchers/sample sizes
Checking and unchecking variables in the sidebar menu attached to the sim
Deleting variables by right-clicking the column on the CODAP table
Various combinations of 2 and 3 listed above
Checking/unchecking variables after some data has already been collected - Data should not be collected for a variable unless its box is checked when the projectile lands
Confirm that clicking save/export/make a copy in the CODAP menu will save the entire combined state of the sim + CODAP integration
Issues to Verify
There are no known issues to verify.
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](https://github.com/phetsims/QA/blob/main/documentation/qa-book.md), 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
[here](https://github.com/phetsims/qa/blob/main/documentation/accessibility-bugs.md). 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:
Test Device
blah
Operating System
blah
Browser
blah
Problem Description
blah
Steps to Reproduce
blah
Visuals
blah
Troubleshooting Information
blah
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](https://github.com/phetsims/QA/blob/main/documentation/qa-book.md).
2. Google it.
3. Ask Katie.
8. Ask a developer.
9. Google it again.
10. Cry.
KatieWoe
commented
2 months ago
Dev-Lite Test
Mentions: @samreid @catherinecarter
Simulation links
Test Matrix
Features included
Focus and Special Instructions
Please test the following:
Issues to Verify
There are no known issues to verify.
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](https://github.com/phetsims/QA/blob/main/documentation/qa-book.md), 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 [here](https://github.com/phetsims/qa/blob/main/documentation/accessibility-bugs.md). 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: Test Device blah Operating System blah Browser blah Problem Description blah Steps to Reproduce blah Visuals blahTroubleshooting Information
blahWho 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](https://github.com/phetsims/QA/blob/main/documentation/qa-book.md). 2. Google it. 3. Ask Katie. 8. Ask a developer. 9. Google it again. 10. Cry.