14
edits
Compatibility/Meetings/Sync w Honza: Difference between revisions
Jump to navigation
Jump to search
16 may meeting minutes
(2nd of May - Meeting minutes) |
(16 may meeting minutes) |
||
| Line 1: | Line 1: | ||
== May 16 2023 == | |||
=== WebRTC issues (SV) === | |||
Since WebRTC is getting more visibility lately, is there a way to see when using Firefox (maybe in about:webrtc) if a website is using it? Would it be useful to add a Trend Label for specific WebRTC issues, to use for future refrences, if we can differentiate issues specific for WebRTC? | |||
We have documented around it and it seems to be used when using web apps for voice/video chatting that use your webcam, headphones and microphone, or for P2P file transfer. We have an ideea of how issues related should look like, but maybe there's a better way to find out if WebRTC is used. | |||
Paul: The mobile and desktop team are doing dedicated tests for webrtc. | |||
Paul: We have an idea what is WebRTC and what to look for but we were wondering if there's a way to check exactly if an issue is webrtc or not? | |||
Honza: I don't have an immediate input regarding WebRTC but lets put a topic in the meeting we have later on with the team. | |||
=== Top 100 testing (SV) === | |||
Paul: QA Desktop wants to reduce their workload regarding this topic. They will go down from their current number of sites tested. | |||
Paul: We will allocate 1h per day for testing the top 100 sites because the main task is to triage bugs and that's more important. | |||
Honza: I am understanding that you would spent roughly around 1h per day for testing this OKR, meaning that in one month, you will cover a batch. | |||
Paul: Testing is organized by us, since we took over this OKR from oher teams, to ensure that the available time for testing is used to its maximum. | |||
Honza: Some things to take into consideration if the triage process time will increase. | |||
Paul: As previously discussed we will test mainly on Android, Desktop-Windows and if the time allows it we will test on Mac as well. | |||
Honza: Every month we should be able to do one subset from the document. | |||
Paul: Initially it was planned to test this twice a year. | |||
Honza: So that means roughly one site per working day. | |||
Paul: We are aiming to verify one website in one hour per day. | |||
Honza: Is that do-able. | |||
Raul/Calin: It looks do-able. We will concetrate our efforts first on mobile and desktop- Windows. If time permits, we will extend the desktop enviroments for testing. | |||
Honza: I have seen that m.youtube.com is not included, just youtube.com in the list. | |||
Paul: We have a list for both desktop and mobile, and if the site has the mobile version, when testing in mobile, we will cover the mobile version as well. | |||
Honza: What are the next steps? | |||
Paul: We will test the list accordingly, to avoid overlapping. It would be better to have one pause between lists, to ensure avoiding overlappin. | |||
== May 2 2023 == | == May 2 2023 == | ||