33
edits
Compatibility/Meetings/Sync w Honza: Difference between revisions
Jump to navigation
Jump to search
July 26 2022
OanaArbuzov (talk | contribs) (Minor changes (2) 14.06.2022) |
(July 26 2022) |
||
| Line 1: | Line 1: | ||
== July 26 2022== | |||
=== QA Documentation added to Mana page (SV) === | |||
https://mana.mozilla.org/wiki/display/QA/WebCompat+team+documents | |||
Honza: Cool, thanks for that. | |||
=== OKR Triage Trends (SV) === | |||
We've added some topics to the OKR | |||
https://github.com/mozilla/webcompat-team-okrs/issues/262 | |||
Raul: Observing duplicate issues that were not reproducible at the time, as per: https://github.com/webcompat/web-bugs/issues/106716, where we observed a pattern, helped us to reproduce an issue that affected numerous users following the Trend guideline. | |||
=== What is a Trend? (SV) === | |||
We summarized some ideas: | |||
- something that occurs on most used/popular sites | |||
- duplicate issues | |||
- unsupported features on Firefox | |||
- unable to sign in with FB/Google/Twitter with ETP - Strict enabled | |||
- embedded media content not displayed with ETP - Strict enabled | |||
Honza: yes, these points summarize the idea of the Trend, and what to look for when observing a Trend. I would also add a page not working in certain parts of the world. | |||
=== [FYI] Incompat ad-on (SV) === | |||
https://addons.mozilla.org/en-US/firefox/addon/incompat/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search | |||
This addon is a companion for https://webcompat.com. It helps track compatibility bugs for sites and shows you the number of already reported bugs on that domain. | |||
Honza: Does this add-on show Duplicate issues? | |||
Raul: Yes, it creates a list of all the issues signaled regarding the URL submited. All the reports are shown via a GitHub search query made by the-addon | |||
Honza: Does it help you in your daily triage? | |||
Raul: Very much. It helps identifing duplicates faster and easier, or other related issues with the reported issue. | |||
=== DevTool - Remote Debugging tablet (SV) === | |||
Unable to see Inspect panel on tablet device (empty screen shown), even if conection to the device was establishes. | |||
(USB debugging is enabled both in Firefox and in device system) | |||
https://prnt.sc/f4ubd-5H54QX | |||
Sometimes an error is shown https://prnt.sc/lwn7JAju04t9 | |||
Honza: Let's keep this topic for the next meeting. | |||
=== Priority vs severity labes (Honza) === | |||
Honza: I've seen that you use labels to set severity and priority. How does that work? | |||
Raul: Once an issue is reproducible, we move it to the Needsdiagnosis milestone, where we set the default label for priority to normal, and the severity label accordingly. | |||
Honza: How do you set the priority level via the label? | |||
Raul: Based on the impact the signaled issue has, we have 3 levels for the severity label: minor, important, critical. | |||
minor- for cosmetical issues on the page | |||
important- a non-core broken piece of functionality | |||
critical- the page or core functionality is unusable, or you would probably open another browser to use it. | |||
Honza: Who sets the labels? | |||
Raul: The priority is set during the diagnosis process, while the severity is set in the triage process. | |||
=== DevTools for QA guidelines document (SV): === | |||
https://docs.google.com/document/d/1LiRE6crZ4sSzzxvU3Xkjg410bQ6-5h2b7nivetMl4ek/edit | |||
Honza: Thanks for that, that is very helpful. | |||
== July 12 2022== | == July 12 2022== | ||