KatieWoe
commented
1 year ago Calling QA here
Closed jonathanolson closed 1 year ago
KatieWoe
commented
1 year ago Calling QA here
KatieWoe
commented
1 year ago By the way, Jaron Droder should be added to the QA credits
jonathanolson
commented
1 year ago Thanks!
RC Test
Mentions: @arouinfar, @kathy-phet, @DianaTavares
Simulation links
Test Matrices
Features included
For QA...
General features
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](https://github.com/phetsims/QA/blob/master/documentation/qa-book.md) 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. - Test the Game Up harness on at least one platform. - Check [this](https://docs.google.com/spreadsheets/d/1umIAmhn89WN1nzcHKhYJcv-n3Oj6ps1wITc-CjWYytE/edit#gid=0) 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. - Try to include version numbers for browsers. - If there is a console available, check for errors and include them in the Problem Description. - As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem. - As the RC ends, please review the QA credits in the about dialog. If the QA credits are complete and correct, please add a comment in the RC test issue indicating so. If not, please open a new issue and specify what changes should be made.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. - Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root: ``` /wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER ``` Further instructions in QA Book - Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other random platform. - Conduct a memory test on the stand alone sim wrapper (rc.1). - Test one platform combination with `?phetioDebug=true` on the Studio and State wrapper. - If Pan/Zoom is supported, make sure that it works when set with PhET-iO State. - Test that the sim works offline: * Click the link to the phet-io zip file (at top of issue) to download the zip file. * Unzip it to a spot locally. * Open `index.html` by double clicking it on your desktop or in a Finder-view. * It should look like the standalone version of the sim in PhET-iO brand.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/master/documentation/qa-book.md). 2. Google it. 3. Ask Katie. 4. Ask a developer. 5. Google it again. 6. Cry.