search

phetsims / qa

Quality Assurance Task Tracking
MIT License
13 stars 8 forks source link

Dev Test: Projectile Data Lab 1.0.0-dev.22 #1060

Closed matthew-blackman closed 6 months ago

matthew-blackman commented 6 months ago

Projectile Data Lab - Dev Test 1

Mentions: @KatieWoe @Nancy-Salpepi @samreid

Simulation links

Test Matrix

Please include all (non-screen reader) feature testing in these records if applicable.

Light testing, or optionally skip if time crunch:

If PhET-iO is being tested:

Features included

Focus and Special Instructions

This is the first dev test for Projectile Data Lab. We'd like to go into RC testing right afterwards. Please make sure to exercise all sim-specific preferences, as well as the one sim-specific audio preference.

Query Parameters: autoGenerateData (boolean) projectileTypeAffectsSpeed (boolean) binStrategy (binWidth or totalBins) showStandardError (boolean) launchSoundStrategy (speed, angle, none)

Non-public Query Parameters: maxProjectilesVSMField (number) maxSamples (number)

PhET-IO Studio: Customization of the mystery launchers and launch mechanisms is achieved in the 'global' section of the studio tree. There, users can define the properties of the three built-in launch mechanisms, three additional custom launch mechanisms (not used in the default sim), as well as assign launch mechanism to the mystery launchers. These are global to ensure that the custom launcher on the Sources and Measures screens are consistent with the Mystery launchers. This enables students to solve for the inner workings of the mystery launchers.

Please test the code snippets in examples.md on at least one platform.

Issues to Verify

None

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. 4. Ask a developer. 5. Google it again. 6. Cry.

KatieWoe commented 6 months ago

I noticed that the Auto-Generate button could be slow when n=40 on the last screen. Is this acceptable, or would you like an issue?

matthew-blackman commented 6 months ago

I noticed that the Auto-Generate button could be slow when n=40 on the last screen. Is this acceptable, or would you like an issue?

@KatieWoe we have an issue for it here - https://github.com/phetsims/projectile-data-lab/issues/192

This was acknowledged as a performance-intensive action (it creates 8,000 landed projectiles all at once) but the designers (myself and @catherinecarter) felt it was reasonable to expect a short delay in this instance. Is there a platform on which this is problematic? If so, please reopen the issue @KatieWoe and we can work on further optimizations.

KatieWoe commented 6 months ago

QA is done

samreid commented 6 months ago

Thanks @KatieWoe and @Nancy-Salpepi. All remaining work tracked elsewhere. Closing.