83
edits
Compatibility/Meetings/Sync w Honza: Difference between revisions
Minor changes 14.06.2022
(July 12 2022) |
OanaArbuzov (talk | contribs) (Minor changes 14.06.2022) |
||
| Line 2: | Line 2: | ||
=== Q3 Planning done (SV) === | === Q3 Planning done (SV) === | ||
We've created the tasks and added them to 2022H2 dashboard. | We've created the tasks and added them to 2022H2 dashboard. | ||
https://github.com/mozilla/webcompat-team-okrs/projects/16 | https://github.com/mozilla/webcompat-team-okrs/projects/16 | ||
Oana: If you consider | Oana: If you consider adding other tasks, please let us know. | ||
Honza: How does Site | Honza: How does Site Interventions Release work? Is it like testing every Release intervention? | ||
Oana: Yes, that is correct. | Oana: Yes, that is correct. | ||
=== Issue reported with features unsupported on Firefox (SV) === | |||
We get issues where some features are not supported on Firefox but are supported on other browsers. There are many times where we can't create a test account or the STR are not clearly provided, so we are unable to verify them. Based on the info/description/screenshot provided by the user, should we move them to Needsdiagnosis or maybe directly to Needscontact, so the | We get issues where some features are not supported on Firefox but are supported on other browsers. | ||
There are many times where we can't create a test account or the STR are not clearly provided, so we are unable to verify them. | |||
Based on the info/description/screenshot provided by the user, should we move them to Needsdiagnosis or maybe directly to Needscontact, so the team would contact the site owner to understand why those features are not supported in Firefox? | |||
e.g https://github.com/webcompat/web-bugs/issues/107210 | e.g https://github.com/webcompat/web-bugs/issues/107210 | ||
Honza: If it's the second case, we can move it to NeedsContact, if we do not have an account, we should move it to NeedsDiagnosis, because we can ask around if we can get an account to test. | Honza: If it's the second case, we can move it to NeedsContact, and if we do not have an account, we should move it to NeedsDiagnosis, because we can ask around if we can get an account to test. | ||
=== Interventions/UA Overrides QA verification guidelines manual+automation (SV) === | === Interventions/UA Overrides QA verification guidelines manual+automation (SV) === | ||
| Line 31: | Line 35: | ||
Honza: Can you quickly summarize this document for me? | Honza: Can you quickly summarize this document for me? | ||
Oana: | Oana: ofc, there is a bit of info about Interventions/UA Overrides, how we can see it based on different devices, how to enable or disable them, and a section about manual and automation testing. | ||
Oana: If one of the Webcompat issue is reproducible, the Intervention/UA Override is still needed. If not, we create a Bugzilla task to remove the Intervention/UA Override. | |||
Honza: When you test if an Intervention is needed, do you go through a list? | Honza: When you test if an Intervention/UA Override is needed, do you go through a list? | ||
Oana: Yes, Dennis created a dashboard where we have the necessary data. | Oana: Yes, Dennis created a dashboard where we have the necessary data. | ||
| Line 39: | Line 45: | ||
Honza: I see you build the gecko driver as well. Is that needed? | Honza: I see you build the gecko driver as well. Is that needed? | ||
Oana: Yes, that is needed for the automation set-up | Oana: Yes, that is needed for the automation set-up in order to run the tests in Firefox | ||
Honza: Sounds cool, please share this document in the next Webcompat meeting. | Honza: Sounds cool, please share this document in the next Webcompat meeting. | ||
Oana: We run them one by one. For the moment, the automation tests are just for desktop. | Honza: What happens if there are too many failed automation tests? | ||
Oana: We run them one by one. | |||
Oana: For the moment, the automation tests are just for the desktop issues. | |||
=== Trends/patterns (Honza) === | |||
One of our goals is to spot trends in WebCompat landscape. | |||
Honza: We have a list of tasks to be completed. This should help us recommend to the team what are the top of the webcompat issues, which are important, which are not. | |||
There are different perspectives regarding this (how many users are using the page, etc). | |||
We have recommendations to the platform team, so that they can focus on them. | |||
The second part is trends, and about spotting them. So, what is a trend? | |||
A trend might be that a page does not work in Firefox, in some parts of the world (unknown issues). Or other browsers are implementing APIs, except for Firefox (doing something without us- future issues). | |||
Oana: The second example of the trend can be observed in Interventions/Overrides | Oana: The second example of the trend can be observed in Interventions/Overrides | ||
Honza | Honza: Exactly. The third case of a trend is known webcompat issues. | ||
So as you are doing triage, you might be able to spot trends. Maybe you can see some patterns. Is that something you can help us? | So as you are doing triage, you might be able to spot trends. Maybe you can see some patterns. Is that something you can help us? | ||
Raul: Should | Raul: Should we focus on reproducible issues reported by users, or Worksforme issues? | ||
Oana: Usually we move issues that we can not reproduce to Worksforme. | |||
Honza: Writing them down, regardless of their status, as long as the issues present a pattern/trend, we can write them down. | |||
Is this possible to summarize this kind of issue? | |||
Oana: We can make a document to summarize this. | Oana: We can make a document to summarize this. | ||
Honza: Great, | Honza: Great, let's try this. | ||
Raul: Here we have an issue that might be classed as a trend. Should we mention future issues inside related issues, like we did here? | |||
https://github.com/webcompat/web-bugs/issues/106716 | |||
Honza: Sure. | Honza: Sure. | ||
Oana: Can we make an OKR task out of this? | Oana: Can we make an OKR task out of this, eg. Triage Trends? | ||
Honza: Sure. | Honza: Sure. | ||
=== DevTools (Honza) === | === DevTools (Honza) === | ||
How much DevTools is useful/needed for triage? | |||
How much DevTools | |||
Oana: We use the Inspector to pin-point the affected area of the code, or we play around with the CSS where possible to see if a possible fix can be applied, and we also use it for RDM. | Oana: We use the Inspector to pin-point the affected area of the code, or we play around with the CSS where possible to see if a possible fix can be applied, and we also use it for RDM. | ||
| Line 95: | Line 111: | ||
Honza: This is a suggestion, we have not agreed on yet. | Honza: This is a suggestion, we have not agreed on yet. | ||
Oana: | Oana: We also use Remote Debugging for Android? We have some ideas there for improvements, as we guide users sometimes to use this, and we also use them. | ||
Honza: Sure, we can talk about what we can improve here as well. | Honza: Sure, we can talk about what we can improve here as well. | ||
| Line 101: | Line 117: | ||
Oana: Also, we use the performance tab of the DevTools, and the Network tab. | Oana: Also, we use the performance tab of the DevTools, and the Network tab. | ||
Honza: Cool, highlight this in a document regarding how, what and why you use DevTools in your | Honza: Cool, highlight this in a document regarding how, what and why you use DevTools in your triage process. | ||