83
edits
(July 26 2022) |
OanaArbuzov (talk | contribs) (Minor changes 26.07.2022) |
||
Line 14: | Line 14: | ||
=== What is a Trend? (SV) === | === What is a Trend? (SV) === | ||
We summarized some ideas: | We summarized some ideas: | ||
- something that occurs on most used/popular sites | |||
- duplicate issues | - something that occurs on most used/popular sites | ||
- unsupported features on Firefox | - duplicate issues | ||
- unable to sign in with FB/Google/Twitter with ETP - Strict enabled | - unsupported features on Firefox | ||
- embedded media content not displayed with ETP - Strict enabled | - 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. | 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) === | === [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 | 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. | 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? | Honza: Does this add-on show Duplicate issues? | ||
Raul: Yes, it creates a list of all the issues signaled regarding the URL | |||
Raul: Yes, it creates a list of all the issues signaled regarding the URL submitted. All the reports are shown via a GitHub search query made by the-addon | |||
Honza: Does it help you in your daily triage? | Honza: Does it help you in your daily triage? | ||
Raul: Very much. It helps | |||
Raul: Very much. It helps identify duplicates faster and easier, or other related issues with the reported issue. | |||
=== DevTool - Remote Debugging tablet (SV) === | === DevTool - Remote Debugging tablet (SV) === | ||
Unable to see Inspect panel on tablet device (empty screen shown), even if | Unable to see Inspect panel on a tablet device (empty screen shown), even if the connection to the device was established. | ||
(USB debugging is enabled both in Firefox and in device system) | (USB debugging is enabled both in Firefox and in the device system) | ||
https://prnt.sc/f4ubd-5H54QX | https://prnt.sc/f4ubd-5H54QX | ||
Sometimes an error is shown https://prnt.sc/lwn7JAju04t9 | Sometimes an error is shown https://prnt.sc/lwn7JAju04t9 | ||
Honza: Let's keep this topic for the next meeting. | Honza: Let's keep this topic for the next meeting. | ||
=== Priority vs severity labes (Honza) === | === Priority vs severity labes (Honza) === | ||
Line 52: | Line 53: | ||
Honza: How do you set the priority level via the label? | 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. | Raul: Based on the impact the signaled issue has, we have 3 levels for the severity label: minor, important, and critical. | ||
minor- for cosmetical issues on the page | |||
important- a non-core broken piece of functionality | - minor- for cosmetical issues on the page | ||
critical- the page or core functionality is unusable, or you would probably open another browser to use it. | - 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? | Honza: Who sets the labels? | ||
Raul: The priority is set during the diagnosis process, while the severity is set in the triage process. | Raul: The priority is set during the diagnosis process, while the severity is set in the triage process. | ||
=== DevTools for QA guidelines document (SV): === | === DevTools for QA guidelines document (SV): === | ||
Line 68: | Line 68: | ||
Honza: Thanks for that, that is very helpful. | Honza: Thanks for that, that is very helpful. | ||
edits