Meta Guide (PDF)

META How to guide Version 06/23 Table of Content Click on hyperlink to access content • 1. Client • Who is Meta? • 2. Testing tools • • • • Testrail VRC Guidelines (2 slides) VRC Security .2 (2 Slides) VRC Performance .1 (2 Slides) • 3. How to write a bug report for Meta • Jira • Bug Summary...

META How to guide Version 06/23 Table of Content Click on hyperlink to access content • 1. Client • Who is Meta? • 2. Testing tools • • • • Testrail VRC Guidelines (2 slides) VRC Security .2 (2 Slides) VRC Performance .1 (2 Slides) • 3. How to write a bug report for Meta • Jira • Bug Summary • Bug description • 4. Regression • Comments to use Who is Meta? Meta is one of the most well known companies, you'll know them for applications such as Facebook and Instagram. We work with Meta to make sure that any VR titles that release on their VR hardware (Quest 2, Quest Pro, Rift-S) complies with their Virtual Reality Checklist (VRC) The specific projects we run with Meta last for 7 weeks, of which we will get builds weekly. With each build we'll run a full pass of the VRC cases, as well as a functionality pass of the build to find any issues that is present. Testrail Testrail is used to create Testing Rails for each project and to complete VRC Rails for all Meta projects on the Oculus Quest 2. Below is a login and link to access testrail: Training - TestRail Email: [email protected] Password: Universally2017 Check the Testrail How to guide to learn how to use this software. VRC GUIDELINES • VRCs are standardized requirements that a VR Game needs to follow so it can be released for the Oculus Quest 2 on the Oculus store. • These test rails can be found in every project and are always the same unless updated in the manifest by Meta. • Below is a link to the VRC guidelines. Try familiarize yourself with each test case and what is required for each case to be passed or failed: VRC Guide .docx (sharepoint.com) • VRC Rails are always the first task to check when starting a new project and should always be checked whenever a new build is received for a project after completing regressions. VRC GUIDELINE EXAMPLE A VRC guideline looks like the following: VRC.Quest.Performance.3: The app must either display head-tracked graphics in the headset within 4 seconds of launch or provide a loading indicator in VR. If the game did not meet the requirement then you would log a critical bug into whichever database is being used to highlight that this VRC is failed. The tester would then fail this VRC case on the VRC Rail for the respective project. VRC SECURITY.2 PROCESS WITHIN THE VRC RAIL, THERE IS A CHECK THAT NEEDS TO BE COMPLETED WITH ADB COMMAND PROMPTS. IN THE APP MANIFEST THERE ARE CERTAIN RESTRICTIONS THAT TITLES MAY NOT GAIN ACCESS TO WHICH FALL UNDER THE SECURITY.2 GUIDELINE. OPEN CMD UNDER: C:…….\PLATFORMTOOLS_R33.0.2WINDOWS\PLATFORMTOOLS> CMD COMMANDS: ADB DEVICES > ADB SHELL PM LIST PACKAGES (THIS WILL LIST ALL KNOWN PACKAGES IN THE HMD) > ADB SHELL DUMPSYS PACKAGE *NAME OF GAME* (E.G. COM.BEATGAMES.BEATSABER) DON’T FORGET TO HIT ENTER AFTER EACH COMMAND. YOU CAN ALSO FIND THE VERSION AND CODE NUMBER IN THIS LIST AS WELL VRC.SECURITY.2 VIDEO Placeholder for video VRC PERFORMANCE.1 PROCESS There is also a process for the VRC Performance.1 test case which requires a user to make an fps graph showing the performance drops within a title. From your Oculus folder on your PC > Oculus > Metrics folder > Open the latest csv file Download the Avg FPS Graph Template Copy the column for “Average_FPS” from the csv file on the Oculus Quest and paste it into the graph templates AVG FPS column Copy the column for “Time_Stamp” from the csv file on the Oculus Quest and paste it into the graph templates Time Stamp column From here, you will gain a graph displaying the drops during gameplay. You will then adjust the labels and calculate the fps using the =AVERAGE(C2:C797) formula in a cell FPS always drops during loading screens and pause menus, so be aware of when drops occur to correctly label the graph VRC.PERFORMANCE.1 VIDEO Placeholder for video Bug reports Most projects used Jira – please check Jira’s How to guide for further info. Always check with your Lead if this template is relevant to your project! See the Bug Template here: BugWritingGuideline.docx (sharepoint.com) Remember that each project will have slight tweaks to their guidelines & Jira terminology! Training Jira : universallyspeaking.atlassian.net/jira Training account: [email protected] Password: UniTrain1! Bug Summary Summaries are one of the things that change most from project to project. Remember to ask your Senior or Lead for a bug guide for your project. General VR Bug Summary Example: [Quest][Quest2] – Cracks in glass briefly disappear when reloading checkpoint after T-Rex/Triceratops scene VRC - failing Bug Summary Example: [Quest][Quest2][VRC.Quest.Functional.3] – Player can get stuck behind a trash can by the Monorail Platform • Usually starts with tags in [brackets] • Followed by the bug’s location tag. • Finished by the summary sentence. • Short but detailed, explaining what the bug is, which action makes it happen and where it happens • Same guidelines, but add a tag for which VRC guideline has been failed. Bug Description • Explanation of the bug: 2-3 sentences explaining the bug • (if applicable) VRC Failed: • Reproduction Rate: How often does the bug happen? 10/10, 5/5 or percentage such as 60%. • Test Case Failed: • Actual Result: One sentence describing what happens • (if applicable) Additional Information: • Expected Result: • • Describe what should happen in-game once the bug has been fixed. Always begin your sentence with “Please ensure…”. • Attached: Regression comment template Fix Status: Fix Verified by QA Devices: Quest/Quest2 Build: r34651 Fix Status: Unable to be reproduced by QA Devices: Quest/Quest2 Build: 1123 We were unable to reproduce this bug so are closing this ticket as a result Fix Status: Fix Failed by QA Devices: Quest/Quest2 Build: v1.2 code 564 Description: The user still clips out of bounds when crawling through the vent. Attached Media: “VentOOB_Build1.2code564.mp4” Fix Status: Blocked by QA Devices: Quest/Quest2 Build: 1.3347 This issue is blocked by issue #JWA-456 – The user consistently crashes when loading into Level 6. Remember to attach media evidence to a Fix Failed comment!