https://wiki.mozilla.org/api.php?action=feedcontributions&user=Ashughes&feedformat=atomMozillaWiki - User contributions [en]2024-03-29T06:29:18ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=Product_Integrity/Automation_QA/Iris_Project/Firefox&diff=1215668Product Integrity/Automation QA/Iris Project/Firefox2019-07-29T20:53:04Z<p>Ashughes: Created page with "This page tracks deployment of Iris automated tests for Firefox. == Roadmap == Beta Release Developer Edition Nightly ESR"</p>
<hr />
<div>This page tracks deployment of Iris automated tests for Firefox.<br />
<br />
== Roadmap ==<br />
Beta<br />
Release<br />
Developer Edition<br />
Nightly<br />
ESR</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1213758User:Ashughes/Iris Community Engagement Plan2019-06-13T18:27:27Z<p>Ashughes: /* Summary */</p>
<hr />
<div>= Summary =<br />
This page tracks planning for the development of a community around the Mozilla Iris test automation project.<br />
<br />
At present time, and since the creation of this wiki page, the following hurdles are known to exist within the project:<br />
* biggest hurdle is structure and workflow due to refactor work<br />
* logistical issue to on-board a new person<br />
* would be nice to have a goal and understanding of how you're going to measure it (eg. X number of people involved) and what impact we expect that will have / why we need it<br />
* need to think about impact of losing paid developers<br />
* people who stumble in will contribute in some minor ways and not a result of something we have deliberately done<br />
* we need to identify customers (mobile and other projects at Mozilla), invite you to a personal hack session to show you how to build a module and tests for your project. Rapid visual automation for your product.<br />
* Another idea is to get someone who tests products in an emulator (Focus, Fennec, etc) and get them to hack with us on it.<br />
* target people in the QA Org from phonebook - ask what they use for testing, how we could get them using Iris<br />
* for second half of the year, if you can travel in North America, could use somebody who could take a trip to a college, youth group, hacker space, conference, etc. Give a hands on workshop with a local group.<br />
* barrier to entry seems to be low, someone found us<br />
* need an entry survey<br />
* need to understand how people are discovering us<br />
* identify issues and nice to haves through conversations with customers, use these issues to direct community<br />
* blanket advertising won't work very well, needs to be focused on a specific area<br />
<br />
The goal is to foster a healthy community of developers and customers alike.<br />
<br />
= Possible Metrics =<br />
'''Activity''' provides a first view of how much the community is doing, and can be used to track different kinds of activity.<br />
* number of commits gives a first idea about the volume of the development effort. <br />
* number of tickets opened provides insight into how many bugs are reported or new features are proposed. <br />
* number of messages in mailing lists or posts in forums gives an idea of how much discussion is being held in public.<br />
<br />
'''Size''' of the community is the number of people participating in it, but, depending on the kind of participation, size numbers may vary. <br />
* number of active contributors (any and all people contributing code or otherwise to the project)<br />
* number of core contributors (fraction of people contributing large proportions of code to the project)<br />
* number of lead contributors (fraction of people contributing as leaders within the project)<br />
<br />
'''Performance''' analyzes how processes and people are performing, and whether or not the project has sufficient resources.<br />
* mean time to resolve or close tickets<br />
* mean time spent in code review<br />
* ratio of new to triaged to closed tickets<br />
<br />
'''Demographics''' measures how people enter and leave a community over time, and the tenure of the community. <br />
* number of new people joining during the corresponding period of time. <br />
* number of active people still in the community broken down by "generations" based on tenure<br />
* retention rate of contributors in each "generation" based on tenure<br />
<br />
'''Diversity''' measures the resiliency of the community in terms of people and organizations participating.<br />
* ratio of employee to volunteer contributors<br />
* ratio of employee to volunteer contributions<br />
* minimum number of developers performing 50% of the commits<br />
* minimum number of employees performing 50% of the commits<br />
<br />
Beyond the above, the Iris project should take a look at [https://github.com/chaoss/metrics CHAOSS Metrics] to evaluate which are relevant to the sustainable growth of the project. In addition the project needs to take a look at how it overlaps with other initiatives and communities within Mozilla so that we are supporting each other, not competing with each other; both in terms of users and contributors.<br />
<br />
= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization, see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
== Strengths and weaknesses ==<br />
Internal factors within an organization:<br />
* Human resources — staff, volunteers, board members, target population<br />
* Physical resources — your location, building, equipment<br />
* Financial — grants, funding agencies, other sources of income<br />
* Activities and processes — programs you run, systems you employ<br />
* Past experiences — building blocks for learning and success, your reputation in the community<br />
<br />
== Opportunities and threats ==<br />
External factors stemming from community or societal forces:<br />
* Future trends in your field or the culture<br />
* The economy — local, national, or international<br />
* Funding sources — foundations, donors, legislatures<br />
* Demographics — changes in the age, race, gender, culture of those you serve or in your area<br />
* The physical environment —is your building in a growing part of town? Is the bus company cutting routes?<br />
* Legislation — do new federal requirements make your job harder...or easier?<br />
* Local, national, or international events<br />
<br />
== Elements to consider ==<br />
Elements to consider in a SWOT analysis include understanding the community that a particular organization is working with. This can be done via public forums, listening campaigns, and informational interviews. Data collection will help inform the community members and workers when developing the SWOT analysis. A needs and assets assessment is tooling that can be used to identify the needs and existing resources of the community. When these assessments are done and data has been collected, an analysis of the community can be made that informs the SWOT analysis.<br />
<br />
== Steps for implementation ==<br />
A SWOT analysis is best developed in a group setting such as a work or community meeting. A facilitator can conduct the meeting by first explaining what a SWOT analysis is as well as identifying the meaning of each term. One way of facilitating the development of a SWOT analysis includes developing an example SWOT with the larger group then separating each group into smaller teams to present to the larger group after set amount of time. This allows for individuals, who may be silenced in a larger group setting, to contribute. Once the allotted time is up, the facilitator may record all the factors of each group onto a large document such as a poster board, and then the large group, as a collective, can go work through each of the threats and weaknesses to explore options that may be used to combat negative forces with the strengths and opportunities present within the organization and community. A SWOT meeting allows participants to creatively brainstorm, identify obstacles, and possibly strategize solutions/way forward to these limitations.<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =<br />
<br />
= Other Considerations =<br />
* Select a communication platform (Slack, Discourse, Github, etc)<br />
* Where possible, use bots for leaderboards, to welcome newcomers, to help people find tasks, and to enable people to engage<br />
* Ensure you have a code of conduct, create a safe space for people to work how they want to work and to make mistakes<br />
* Help your helpers: get them access to core Engineering resources, invite them to chats/calls to further their understanding and engagement, point them towards programs to collaborate with individuals. The more community members turn into experts, and the more experts turn into professionals on your platform, the better it is for everyone. <br />
* Create contests to spur rapid development of a specific deliverable<br />
* Blog about your project and community, encourage those in your community to do the same, and amplify those posts.<br />
* Periodically feature a member of the community<br />
* Send swag, stickers, etc of your community to your community<br />
* Think about how you're helping to build careers<br />
* Periodically reflect on the state of your community, identify areas for improvement and commit to solving one problem.<br />
* Set Goals and Measure Results. How will you benefit from this collection of potential advisors, critics, contributors, and customers? What are your critical metrics, and how can you measure them? Identify your main goal: Is it software downloads? Getting developers to contribute to your project? Adding names to your developer mailing list? For example, consider using the “Unique clones” number included in the Traffic Statistics section of the GitHub repo reports as it'll give you a good idea of your daily download activity. Also log all of the GitHub repository statistics on a regular basis: Stars, Forks, Issues, Pull Requests as these statistics give you usage “signals.”<br />
* Estimate future marketing activities and product evolution and put a straw-man plan in place, this will give you a way to measure progress against any plan.<br />
* Consider the tech you're using and how you can utilize external communities centred around that tech to bolster your project (eg. Hackernews)<br />
* Excellent documentation is the first step in making your software easy-to-use, make sure you have readmes, the API, and supporting technical documentation in place.<br />
* Code of conduct: In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.<br />
* Make it easy for developers to ask and answer questions. (IRC is one of the primary channels we use. There is usually one of our developers “lurking” around there somewhere.) <br />
* Identify issues for first-timers<br />
* Documentation edits are a great way to gain experience in an open source project. <br />
* Getting the opinions of your users reveals whether your code is meeting its big-picture goals.<br />
* In addition to user interviews, attend conferences and meetups to build awareness and find the right audience. Even when you aren’t presenting, attending these events and speaking to developers directly is a great way to get feedback. Face-to-face interactions often help us build a better understanding of the problems and challenges that developers face.<br />
* Listen to feedback</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212477User:Ashughes/Iris Community Engagement Plan2019-05-16T08:23:20Z<p>Ashughes: /* Phase 3: Profit */</p>
<hr />
<div>= Summary =<br />
This page tracks planning for the development of a community around the Mozilla Iris test automation project.<br />
<br />
At present time, and since the creation of this wiki page, the following hurdles are known to exist within the project:<br />
* biggest hurdle is structure and workflow due to refactor work<br />
* logistical issue to on-board a new person<br />
* would be nice to have a goal and understanding of how you're going to measure it (eg. X number of people involved) and what impact we expect that will have / why we need it<br />
* need to think about impact of losing paid developers<br />
* people who stumble in will contribute in some minor ways and not a result of something we have deliberately done<br />
* we need to identify customers (mobile and other projects at Mozilla), invite you to a personal hack session to show you how to build a module and tests for your project. Rapid visual automation for your product.<br />
* Another idea is to get someone who tests products in an emulator (Focus, Fennec, etc) and get them to hack with us on it.<br />
* target people in the QA Org from phonebook - ask what they use for testing, how we could get them using Iris<br />
* for second half of the year, if you can travel in North America, could use somebody who could take a trip to a college, youth group, hacker space, conference, etc. Give a hands on workshop with a local group.<br />
* barrier to entry seems to be low, someone found us<br />
* need an entry survey<br />
* need to understand how people are discovering us<br />
* identify issues and nice to haves through conversations with customers, use these issues to direct community<br />
* blanket advertising won't work very well, needs to be focused on a specific area<br />
<br />
The goal is to foster a healthy community of developers and customers alike.<br />
<br />
= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization, see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
== Strengths and weaknesses ==<br />
Internal factors within an organization:<br />
* Human resources — staff, volunteers, board members, target population<br />
* Physical resources — your location, building, equipment<br />
* Financial — grants, funding agencies, other sources of income<br />
* Activities and processes — programs you run, systems you employ<br />
* Past experiences — building blocks for learning and success, your reputation in the community<br />
<br />
== Opportunities and threats ==<br />
External factors stemming from community or societal forces:<br />
* Future trends in your field or the culture<br />
* The economy — local, national, or international<br />
* Funding sources — foundations, donors, legislatures<br />
* Demographics — changes in the age, race, gender, culture of those you serve or in your area<br />
* The physical environment —is your building in a growing part of town? Is the bus company cutting routes?<br />
* Legislation — do new federal requirements make your job harder...or easier?<br />
* Local, national, or international events<br />
<br />
== Elements to consider ==<br />
Elements to consider in a SWOT analysis include understanding the community that a particular organization is working with. This can be done via public forums, listening campaigns, and informational interviews. Data collection will help inform the community members and workers when developing the SWOT analysis. A needs and assets assessment is tooling that can be used to identify the needs and existing resources of the community. When these assessments are done and data has been collected, an analysis of the community can be made that informs the SWOT analysis.<br />
<br />
== Steps for implementation ==<br />
A SWOT analysis is best developed in a group setting such as a work or community meeting. A facilitator can conduct the meeting by first explaining what a SWOT analysis is as well as identifying the meaning of each term. One way of facilitating the development of a SWOT analysis includes developing an example SWOT with the larger group then separating each group into smaller teams to present to the larger group after set amount of time. This allows for individuals, who may be silenced in a larger group setting, to contribute. Once the allotted time is up, the facilitator may record all the factors of each group onto a large document such as a poster board, and then the large group, as a collective, can go work through each of the threats and weaknesses to explore options that may be used to combat negative forces with the strengths and opportunities present within the organization and community. A SWOT meeting allows participants to creatively brainstorm, identify obstacles, and possibly strategize solutions/way forward to these limitations.<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =<br />
<br />
= Other Considerations =<br />
* Select a communication platform (Slack, Discourse, Github, etc)<br />
* Where possible, use bots for leaderboards, to welcome newcomers, to help people find tasks, and to enable people to engage<br />
* Ensure you have a code of conduct, create a safe space for people to work how they want to work and to make mistakes<br />
* Help your helpers: get them access to core Engineering resources, invite them to chats/calls to further their understanding and engagement, point them towards programs to collaborate with individuals. The more community members turn into experts, and the more experts turn into professionals on your platform, the better it is for everyone. <br />
* Create contests to spur rapid development of a specific deliverable<br />
* Blog about your project and community, encourage those in your community to do the same, and amplify those posts.<br />
* Periodically feature a member of the community<br />
* Send swag, stickers, etc of your community to your community<br />
* Think about how you're helping to build careers<br />
* Periodically reflect on the state of your community, identify areas for improvement and commit to solving one problem.<br />
* Set Goals and Measure Results. How will you benefit from this collection of potential advisors, critics, contributors, and customers? What are your critical metrics, and how can you measure them? Identify your main goal: Is it software downloads? Getting developers to contribute to your project? Adding names to your developer mailing list? For example, consider using the “Unique clones” number included in the Traffic Statistics section of the GitHub repo reports as it'll give you a good idea of your daily download activity. Also log all of the GitHub repository statistics on a regular basis: Stars, Forks, Issues, Pull Requests as these statistics give you usage “signals.”<br />
* Estimate future marketing activities and product evolution and put a straw-man plan in place, this will give you a way to measure progress against any plan.<br />
* Consider the tech you're using and how you can utilize external communities centred around that tech to bolster your project (eg. Hackernews)<br />
* Excellent documentation is the first step in making your software easy-to-use, make sure you have readmes, the API, and supporting technical documentation in place.<br />
* Code of conduct: In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.<br />
* Make it easy for developers to ask and answer questions. (IRC is one of the primary channels we use. There is usually one of our developers “lurking” around there somewhere.) <br />
* Identify issues for first-timers<br />
* Documentation edits are a great way to gain experience in an open source project. <br />
* Getting the opinions of your users reveals whether your code is meeting its big-picture goals.<br />
* In addition to user interviews, attend conferences and meetups to build awareness and find the right audience. Even when you aren’t presenting, attending these events and speaking to developers directly is a great way to get feedback. Face-to-face interactions often help us build a better understanding of the problems and challenges that developers face.<br />
* Listen to feedback</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212476User:Ashughes/Iris Community Engagement Plan2019-05-16T07:58:25Z<p>Ashughes: /* Phase 1: SWOT Analysis */</p>
<hr />
<div>= Summary =<br />
This page tracks planning for the development of a community around the Mozilla Iris test automation project.<br />
<br />
At present time, and since the creation of this wiki page, the following hurdles are known to exist within the project:<br />
* biggest hurdle is structure and workflow due to refactor work<br />
* logistical issue to on-board a new person<br />
* would be nice to have a goal and understanding of how you're going to measure it (eg. X number of people involved) and what impact we expect that will have / why we need it<br />
* need to think about impact of losing paid developers<br />
* people who stumble in will contribute in some minor ways and not a result of something we have deliberately done<br />
* we need to identify customers (mobile and other projects at Mozilla), invite you to a personal hack session to show you how to build a module and tests for your project. Rapid visual automation for your product.<br />
* Another idea is to get someone who tests products in an emulator (Focus, Fennec, etc) and get them to hack with us on it.<br />
* target people in the QA Org from phonebook - ask what they use for testing, how we could get them using Iris<br />
* for second half of the year, if you can travel in North America, could use somebody who could take a trip to a college, youth group, hacker space, conference, etc. Give a hands on workshop with a local group.<br />
* barrier to entry seems to be low, someone found us<br />
* need an entry survey<br />
* need to understand how people are discovering us<br />
* identify issues and nice to haves through conversations with customers, use these issues to direct community<br />
* blanket advertising won't work very well, needs to be focused on a specific area<br />
<br />
The goal is to foster a healthy community of developers and customers alike.<br />
<br />
= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization, see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
== Strengths and weaknesses ==<br />
Internal factors within an organization:<br />
* Human resources — staff, volunteers, board members, target population<br />
* Physical resources — your location, building, equipment<br />
* Financial — grants, funding agencies, other sources of income<br />
* Activities and processes — programs you run, systems you employ<br />
* Past experiences — building blocks for learning and success, your reputation in the community<br />
<br />
== Opportunities and threats ==<br />
External factors stemming from community or societal forces:<br />
* Future trends in your field or the culture<br />
* The economy — local, national, or international<br />
* Funding sources — foundations, donors, legislatures<br />
* Demographics — changes in the age, race, gender, culture of those you serve or in your area<br />
* The physical environment —is your building in a growing part of town? Is the bus company cutting routes?<br />
* Legislation — do new federal requirements make your job harder...or easier?<br />
* Local, national, or international events<br />
<br />
== Elements to consider ==<br />
Elements to consider in a SWOT analysis include understanding the community that a particular organization is working with. This can be done via public forums, listening campaigns, and informational interviews. Data collection will help inform the community members and workers when developing the SWOT analysis. A needs and assets assessment is tooling that can be used to identify the needs and existing resources of the community. When these assessments are done and data has been collected, an analysis of the community can be made that informs the SWOT analysis.<br />
<br />
== Steps for implementation ==<br />
A SWOT analysis is best developed in a group setting such as a work or community meeting. A facilitator can conduct the meeting by first explaining what a SWOT analysis is as well as identifying the meaning of each term. One way of facilitating the development of a SWOT analysis includes developing an example SWOT with the larger group then separating each group into smaller teams to present to the larger group after set amount of time. This allows for individuals, who may be silenced in a larger group setting, to contribute. Once the allotted time is up, the facilitator may record all the factors of each group onto a large document such as a poster board, and then the large group, as a collective, can go work through each of the threats and weaknesses to explore options that may be used to combat negative forces with the strengths and opportunities present within the organization and community. A SWOT meeting allows participants to creatively brainstorm, identify obstacles, and possibly strategize solutions/way forward to these limitations.<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212475User:Ashughes/Iris Community Engagement Plan2019-05-16T07:57:53Z<p>Ashughes: /* Summary */</p>
<hr />
<div>= Summary =<br />
This page tracks planning for the development of a community around the Mozilla Iris test automation project.<br />
<br />
At present time, and since the creation of this wiki page, the following hurdles are known to exist within the project:<br />
* biggest hurdle is structure and workflow due to refactor work<br />
* logistical issue to on-board a new person<br />
* would be nice to have a goal and understanding of how you're going to measure it (eg. X number of people involved) and what impact we expect that will have / why we need it<br />
* need to think about impact of losing paid developers<br />
* people who stumble in will contribute in some minor ways and not a result of something we have deliberately done<br />
* we need to identify customers (mobile and other projects at Mozilla), invite you to a personal hack session to show you how to build a module and tests for your project. Rapid visual automation for your product.<br />
* Another idea is to get someone who tests products in an emulator (Focus, Fennec, etc) and get them to hack with us on it.<br />
* target people in the QA Org from phonebook - ask what they use for testing, how we could get them using Iris<br />
* for second half of the year, if you can travel in North America, could use somebody who could take a trip to a college, youth group, hacker space, conference, etc. Give a hands on workshop with a local group.<br />
* barrier to entry seems to be low, someone found us<br />
* need an entry survey<br />
* need to understand how people are discovering us<br />
* identify issues and nice to haves through conversations with customers, use these issues to direct community<br />
* blanket advertising won't work very well, needs to be focused on a specific area<br />
<br />
The goal is to foster a healthy community of developers and customers alike.<br />
<br />
= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
== Strengths and weaknesses ==<br />
Internal factors within an organization:<br />
* Human resources — staff, volunteers, board members, target population<br />
* Physical resources — your location, building, equipment<br />
* Financial — grants, funding agencies, other sources of income<br />
* Activities and processes — programs you run, systems you employ<br />
* Past experiences — building blocks for learning and success, your reputation in the community<br />
<br />
== Opportunities and threats ==<br />
External factors stemming from community or societal forces:<br />
* Future trends in your field or the culture<br />
* The economy — local, national, or international<br />
* Funding sources — foundations, donors, legislatures<br />
* Demographics — changes in the age, race, gender, culture of those you serve or in your area<br />
* The physical environment —is your building in a growing part of town? Is the bus company cutting routes?<br />
* Legislation — do new federal requirements make your job harder...or easier?<br />
* Local, national, or international events<br />
<br />
== Elements to consider ==<br />
Elements to consider in a SWOT analysis include understanding the community that a particular organization is working with. This can be done via public forums, listening campaigns, and informational interviews. Data collection will help inform the community members and workers when developing the SWOT analysis. A needs and assets assessment is tooling that can be used to identify the needs and existing resources of the community. When these assessments are done and data has been collected, an analysis of the community can be made that informs the SWOT analysis.<br />
<br />
== Steps for implementation ==<br />
A SWOT analysis is best developed in a group setting such as a work or community meeting. A facilitator can conduct the meeting by first explaining what a SWOT analysis is as well as identifying the meaning of each term. One way of facilitating the development of a SWOT analysis includes developing an example SWOT with the larger group then separating each group into smaller teams to present to the larger group after set amount of time. This allows for individuals, who may be silenced in a larger group setting, to contribute. Once the allotted time is up, the facilitator may record all the factors of each group onto a large document such as a poster board, and then the large group, as a collective, can go work through each of the threats and weaknesses to explore options that may be used to combat negative forces with the strengths and opportunities present within the organization and community. A SWOT meeting allows participants to creatively brainstorm, identify obstacles, and possibly strategize solutions/way forward to these limitations.<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212323User:Ashughes/Iris Community Engagement Plan2019-05-14T10:28:01Z<p>Ashughes: </p>
<hr />
<div>= Summary =<br />
This page tracks planning for the development of a community around the Mozilla Iris test automation project.<br />
<br />
At present time, the following hurdles are known to exist within the project:<br />
* biggest hurdle is structure and workflow due to refactor work<br />
* logistical issue to on-board a new person<br />
* would be nice to have a goal and understanding of how you're going to measure it (eg. X number of people involved) and what impact we expect that will have / why we need it<br />
* need to think about impact of losing paid developers<br />
* people who stumble in will contribute in some minor ways and not a result of something we have deliberately done<br />
* we need to identify customers (mobile and other projects at Mozilla), invite you to a personal hack session to show you how to build a module and tests for your project. Rapid visual automation for your product.<br />
* Another idea is to get someone who tests products in an emulator (Focus, Fennec, etc) and get them to hack with us on it.<br />
* target people in the QA Org from phonebook - ask what they use for testing, how we could get them using Iris<br />
* for second half of the year, if you can travel in North America, could use somebody who could take a trip to a college, youth group, hacker space, conference, etc. Give a hands on workshop with a local group.<br />
* barrier to entry seems to be low, someone found us<br />
* need an entry survey<br />
* need to understand how people are discovering us<br />
* identify issues and nice to haves through conversations with customers, use these issues to direct community<br />
* blanket advertising won't work very well, needs to be focused on a specific area<br />
<br />
= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
== Strengths and weaknesses ==<br />
Internal factors within an organization:<br />
* Human resources — staff, volunteers, board members, target population<br />
* Physical resources — your location, building, equipment<br />
* Financial — grants, funding agencies, other sources of income<br />
* Activities and processes — programs you run, systems you employ<br />
* Past experiences — building blocks for learning and success, your reputation in the community<br />
<br />
== Opportunities and threats ==<br />
External factors stemming from community or societal forces:<br />
* Future trends in your field or the culture<br />
* The economy — local, national, or international<br />
* Funding sources — foundations, donors, legislatures<br />
* Demographics — changes in the age, race, gender, culture of those you serve or in your area<br />
* The physical environment —is your building in a growing part of town? Is the bus company cutting routes?<br />
* Legislation — do new federal requirements make your job harder...or easier?<br />
* Local, national, or international events<br />
<br />
== Elements to consider ==<br />
Elements to consider in a SWOT analysis include understanding the community that a particular organization is working with. This can be done via public forums, listening campaigns, and informational interviews. Data collection will help inform the community members and workers when developing the SWOT analysis. A needs and assets assessment is tooling that can be used to identify the needs and existing resources of the community. When these assessments are done and data has been collected, an analysis of the community can be made that informs the SWOT analysis.<br />
<br />
== Steps for implementation ==<br />
A SWOT analysis is best developed in a group setting such as a work or community meeting. A facilitator can conduct the meeting by first explaining what a SWOT analysis is as well as identifying the meaning of each term. One way of facilitating the development of a SWOT analysis includes developing an example SWOT with the larger group then separating each group into smaller teams to present to the larger group after set amount of time. This allows for individuals, who may be silenced in a larger group setting, to contribute. Once the allotted time is up, the facilitator may record all the factors of each group onto a large document such as a poster board, and then the large group, as a collective, can go work through each of the threats and weaknesses to explore options that may be used to combat negative forces with the strengths and opportunities present within the organization and community. A SWOT meeting allows participants to creatively brainstorm, identify obstacles, and possibly strategize solutions/way forward to these limitations.<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212322User:Ashughes/Iris Community Engagement Plan2019-05-14T10:27:43Z<p>Ashughes: /* Phase 1: SWOT Analysis */</p>
<hr />
<div>This page tracks planning for the development of a community around the Mozilla Iris test automation project.<br />
<br />
At present time, the following hurdles are known to exist within the project:<br />
* biggest hurdle is structure and workflow due to refactor work<br />
* logistical issue to on-board a new person<br />
* would be nice to have a goal and understanding of how you're going to measure it (eg. X number of people involved) and what impact we expect that will have / why we need it<br />
* need to think about impact of losing paid developers<br />
* people who stumble in will contribute in some minor ways and not a result of something we have deliberately done<br />
* we need to identify customers (mobile and other projects at Mozilla), invite you to a personal hack session to show you how to build a module and tests for your project. Rapid visual automation for your product.<br />
* Another idea is to get someone who tests products in an emulator (Focus, Fennec, etc) and get them to hack with us on it.<br />
* target people in the QA Org from phonebook - ask what they use for testing, how we could get them using Iris<br />
* for second half of the year, if you can travel in North America, could use somebody who could take a trip to a college, youth group, hacker space, conference, etc. Give a hands on workshop with a local group.<br />
* barrier to entry seems to be low, someone found us<br />
* need an entry survey<br />
* need to understand how people are discovering us<br />
* identify issues and nice to haves through conversations with customers, use these issues to direct community<br />
* blanket advertising won't work very well, needs to be focused on a specific area<br />
<br />
= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
== Strengths and weaknesses ==<br />
Internal factors within an organization:<br />
* Human resources — staff, volunteers, board members, target population<br />
* Physical resources — your location, building, equipment<br />
* Financial — grants, funding agencies, other sources of income<br />
* Activities and processes — programs you run, systems you employ<br />
* Past experiences — building blocks for learning and success, your reputation in the community<br />
<br />
== Opportunities and threats ==<br />
External factors stemming from community or societal forces:<br />
* Future trends in your field or the culture<br />
* The economy — local, national, or international<br />
* Funding sources — foundations, donors, legislatures<br />
* Demographics — changes in the age, race, gender, culture of those you serve or in your area<br />
* The physical environment —is your building in a growing part of town? Is the bus company cutting routes?<br />
* Legislation — do new federal requirements make your job harder...or easier?<br />
* Local, national, or international events<br />
<br />
== Elements to consider ==<br />
Elements to consider in a SWOT analysis include understanding the community that a particular organization is working with. This can be done via public forums, listening campaigns, and informational interviews. Data collection will help inform the community members and workers when developing the SWOT analysis. A needs and assets assessment is tooling that can be used to identify the needs and existing resources of the community. When these assessments are done and data has been collected, an analysis of the community can be made that informs the SWOT analysis.<br />
<br />
== Steps for implementation ==<br />
A SWOT analysis is best developed in a group setting such as a work or community meeting. A facilitator can conduct the meeting by first explaining what a SWOT analysis is as well as identifying the meaning of each term. One way of facilitating the development of a SWOT analysis includes developing an example SWOT with the larger group then separating each group into smaller teams to present to the larger group after set amount of time. This allows for individuals, who may be silenced in a larger group setting, to contribute. Once the allotted time is up, the facilitator may record all the factors of each group onto a large document such as a poster board, and then the large group, as a collective, can go work through each of the threats and weaknesses to explore options that may be used to combat negative forces with the strengths and opportunities present within the organization and community. A SWOT meeting allows participants to creatively brainstorm, identify obstacles, and possibly strategize solutions/way forward to these limitations.<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212321User:Ashughes/Iris Community Engagement Plan2019-05-14T10:25:42Z<p>Ashughes: /* Phase 1: SWOT Analysis */</p>
<hr />
<div>= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
== Strengths and weaknesses ==<br />
Internal factors within an organization:<br />
* Human resources — staff, volunteers, board members, target population<br />
* Physical resources — your location, building, equipment<br />
* Financial — grants, funding agencies, other sources of income<br />
* Activities and processes — programs you run, systems you employ<br />
* Past experiences — building blocks for learning and success, your reputation in the community<br />
<br />
== Opportunities and threats ==<br />
External factors stemming from community or societal forces:<br />
* Future trends in your field or the culture<br />
* The economy — local, national, or international<br />
* Funding sources — foundations, donors, legislatures<br />
* Demographics — changes in the age, race, gender, culture of those you serve or in your area<br />
* The physical environment —is your building in a growing part of town? Is the bus company cutting routes?<br />
* Legislation — do new federal requirements make your job harder...or easier?<br />
* Local, national, or international events<br />
<br />
== Elements to consider ==<br />
Elements to consider in a SWOT analysis include understanding the community that a particular organization is working with. This can be done via public forums, listening campaigns, and informational interviews. Data collection will help inform the community members and workers when developing the SWOT analysis. A needs and assets assessment is tooling that can be used to identify the needs and existing resources of the community. When these assessments are done and data has been collected, an analysis of the community can be made that informs the SWOT analysis.<br />
<br />
== Steps for implementation ==<br />
A SWOT analysis is best developed in a group setting such as a work or community meeting. A facilitator can conduct the meeting by first explaining what a SWOT analysis is as well as identifying the meaning of each term. One way of facilitating the development of a SWOT analysis includes developing an example SWOT with the larger group then separating each group into smaller teams to present to the larger group after set amount of time. This allows for individuals, who may be silenced in a larger group setting, to contribute. Once the allotted time is up, the facilitator may record all the factors of each group onto a large document such as a poster board, and then the large group, as a collective, can go work through each of the threats and weaknesses to explore options that may be used to combat negative forces with the strengths and opportunities present within the organization and community. A SWOT meeting allows participants to creatively brainstorm, identify obstacles, and possibly strategize solutions/way forward to these limitations.<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212320User:Ashughes/Iris Community Engagement Plan2019-05-14T10:20:38Z<p>Ashughes: /* Phase 1: SWOT Analysis */</p>
<hr />
<div>= Phase 1: SWOT Analysis =<br />
For more background on SWOT Analysis as it pertains to Community Organization see [https://en.wikipedia.org/wiki/SWOT_analysis#In_community_organization Wikipedia].<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris_Community_Engagement_Plan&diff=1212319User:Ashughes/Iris Community Engagement Plan2019-05-14T10:19:20Z<p>Ashughes: Created page with "= Phase 1: SWOT Analysis = = Phase 2: ??? = = Phase 3: Profit ="</p>
<hr />
<div>= Phase 1: SWOT Analysis =<br />
<br />
= Phase 2: ??? =<br />
<br />
= Phase 3: Profit =</div>Ashugheshttps://wiki.mozilla.org/index.php?title=Product_Integrity/Mozilla_Iris&diff=1206277Product Integrity/Mozilla Iris2019-01-16T15:21:30Z<p>Ashughes: /* More Details */</p>
<hr />
<div>== Overview ==<br />
The Mozilla Iris team was borne out of an idea to create a visual test suite for Firefox. The team oversees the development, maintenance, and deployment of the Mozilla Iris test suite. <br />
<br />
== Mission ==<br />
The Mozilla Iris team mission is to provide tools to democratize test automation and positively impact the quality of Mozilla products. <br />
<br />
== The Team ==<br />
The Mozilla Iris team is broken into three technical groups: Core (responsible for development of the Iris framework), Test (responsible for the creation of new testcases), and Deploy (responsible for deployment of Iris throughout the Mozilla Project).<br />
<br />
=== Core ===<br />
* Matt Wobensmith (Lead)<br />
<br />
=== Test ===<br />
* Tracy Walker (Lead)<br />
<br />
=== Deploy ===<br />
* Anthony Hughes (Lead)<br />
<br />
== More Details ==<br />
For code and more information on the project see https://github.com/mozilla/iris.<br />
<br />
You can join us on Slack at https://mozilla.slack.com/messages/C8U8VBWTU.<br />
<br />
We can be reached via email at iris@mozilla.com.<br />
<br />
== Project Status Updates ==<br />
* [https://blog.ashughes.com/2019/01/10/mozilla-iris-report-december-2018 December 2018]<br />
* [https://blog.ashughes.com/2018/12/03/mozilla-iris-report-november-2018 November 2018]</div>Ashugheshttps://wiki.mozilla.org/index.php?title=Product_Integrity/Mozilla_Iris&diff=1206276Product Integrity/Mozilla Iris2019-01-16T15:21:09Z<p>Ashughes: /* More Details */</p>
<hr />
<div>== Overview ==<br />
The Mozilla Iris team was borne out of an idea to create a visual test suite for Firefox. The team oversees the development, maintenance, and deployment of the Mozilla Iris test suite. <br />
<br />
== Mission ==<br />
The Mozilla Iris team mission is to provide tools to democratize test automation and positively impact the quality of Mozilla products. <br />
<br />
== The Team ==<br />
The Mozilla Iris team is broken into three technical groups: Core (responsible for development of the Iris framework), Test (responsible for the creation of new testcases), and Deploy (responsible for deployment of Iris throughout the Mozilla Project).<br />
<br />
=== Core ===<br />
* Matt Wobensmith (Lead)<br />
<br />
=== Test ===<br />
* Tracy Walker (Lead)<br />
<br />
=== Deploy ===<br />
* Anthony Hughes (Lead)<br />
<br />
== More Details ==<br />
For code and more information on the project see https://github.com/mozilla/iris.<br />
<br />
You can join us on Slack at https://mozilla.slack.com/messages/C8U8VBWTU.<br />
<br />
We can be reached via email at iris@mozilla.com.<br />
<br />
; Project Status Updates<br />
* [https://blog.ashughes.com/2019/01/10/mozilla-iris-report-december-2018 December 2018]<br />
* [https://blog.ashughes.com/2018/12/03/mozilla-iris-report-november-2018 November 2018]</div>Ashugheshttps://wiki.mozilla.org/index.php?title=Product_Integrity/Mozilla_Iris&diff=1206066Product Integrity/Mozilla Iris2019-01-10T21:32:48Z<p>Ashughes: Created page with "== Overview == The Mozilla Iris team was borne out of an idea to create a visual test suite for Firefox. The team oversees the development, maintenance, and deployment of the..."</p>
<hr />
<div>== Overview ==<br />
The Mozilla Iris team was borne out of an idea to create a visual test suite for Firefox. The team oversees the development, maintenance, and deployment of the Mozilla Iris test suite. <br />
<br />
== Mission ==<br />
The Mozilla Iris team mission is to provide tools to democratize test automation and positively impact the quality of Mozilla products. <br />
<br />
== The Team ==<br />
The Mozilla Iris team is broken into three technical groups: Core (responsible for development of the Iris framework), Test (responsible for the creation of new testcases), and Deploy (responsible for deployment of Iris throughout the Mozilla Project).<br />
<br />
=== Core ===<br />
* Matt Wobensmith (Lead)<br />
<br />
=== Test ===<br />
* Tracy Walker (Lead)<br />
<br />
=== Deploy ===<br />
* Anthony Hughes (Lead)<br />
<br />
== More Details ==<br />
For code and more information on the project see https://github.com/mozilla/iris.<br />
<br />
You can join us on Slack at https://mozilla.slack.com/messages/C8U8VBWTU.<br />
<br />
We can be reached via email at iris@mozilla.com.</div>Ashugheshttps://wiki.mozilla.org/index.php?title=QA&diff=1206065QA2019-01-10T21:18:07Z<p>Ashughes: /* Teams */</p>
<hr />
<div>[[File:Qa-badge.jpg|250px|left]]<br />
<br />
<br><br><br />
<br />
Welcome to the Mozilla QA wiki home page. <br />
<br />
We are a guild of individuals united by a common passion to make the quality of the products Mozilla creates the best it can possibly be. There are a plethora of ways to get involved and be a part of the Mozilla Quality Project to help ensure, empower, extend, and enjoy the open web. We're excited you're here to join us.<br />
<br clear=all><br />
<br />
= Quality Assurance Principles =<br />
These are the foundational elements that we evaluate to judge quality for each of our projects. These are all interdependent and interrelated and the list is probably not exhaustive, but it will give you an idea of what we are passionate about.<br />
* Dependability - Every product should be stable and dependable<br />
* Delight - Doing "what it should do" is not enough. The product must delight the user with its functionality.<br />
* Security & Privacy - Mozilla believes very strongly that our products must put our users in control of their data and must take every step we can to ensure your security while on the web.<br />
* Performance - The products must meet or exceed the performance requirements we and our users demand.<br />
* Web Platform - Our mission is to extend, empower, and keep the web platform open for all. We do that by releasing great products that people love, which push the boundaries and capabilities of the open web ever farther.<br />
<br />
= Get In Touch! =<br />
We'd love to hear from you. We hang out on Mozilla IRC (irc.mozilla.org) in the #qa channel. We use the [https://groups.google.com/forum/#!forum/mozilla.dev.quality dev-quality] mailing list for communication and discussion. Our blog is at [https://quality.mozilla.org quality.mozilla.org (also known as QMO)].<br />
<br />
While you're at it, please register as a Mozillian and [https://mozillians.org/en-US/group/qa/ join us]!<br />
<br />
= Teams =<br />
We are organized into product focused areas. You can find our teams and team leads' IRC nicknames below.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 15%" | QMO Team Page<br />
| style="font-weight: bold; background: #DDD; width: 15%" | Team Lead<br />
| style="font-weight: bold; background: #DDD; width: 20%" | Team Wiki<br />
| style="font-weight: bold; background: #DDD; width: 30%" | Primary Focus Areas<br />
| style="font-weight: bold; background: #DDD; width: 20%" | Primary Team IRC Channels<br />
|-<br />
| [https://quality.mozilla.org/teams/firefoxqe/ Firefox QE]<br />
| None at this time. Team members are embedded in Engineering Teams<br />
| [[QA/Firefox|QA/Firefox]]<br />
| Firefox browser (Desktop and Android)<br />
| #qa<br />
|-<br />
| [https://quality.mozilla.org/teams/test-engineering/ Firefox Test Engineering]<br />
| sphilp<br />
| [https://wiki.mozilla.org/TestEngineering https://wiki.mozilla.org/TestEngineering]<br />
| Firefox Test Engineering<br />
| #qa, #fx-test<br />
|-<br />
| [https://quality.mozilla.org/teams/web-qa/ Web and QA Services]<br />
| Stephend<br />
| [[QA/Execution/Web_Testing|QA/Execution/Web_Testing]]<br />
| Mozilla websites, Marketplace, QA specific sites<br />
| #qa, #mozwebqa<br />
|-<br />
| [https://quality.mozilla.org/teams/services/ Cloud Services QA]<br />
| sphilp<br />
| [[QA/Services|QA/Services]]<br />
| Mozilla Cloud Services (sync, simplepush, OAuth, Firefox Accounts etc)<br />
| #qa, #services-qa<br />
|-<br />
| [https://github.com/mozilla/iris Mozilla Iris]<br />
| Matt Wobensmith (Core)<br />Tracy Walker (Test)<br />Anthony Hughes (Deploy)<br />
| [[QA/Product_Integrity/Mozilla_Iris]]<br />
| Test automation<br />
| #qa-automation<br />
|}<br />
<br />
[[File:Mozilla_QA_2014_team.jpg|border|600px|2014 QA Workweek in Mountain View]]<br />
<br />
<small> The old version of this [https://wiki.mozilla.org/QA_Archived_Home_Page page is archived here]</small></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1204216User:Ashughes2018-11-21T15:05:40Z<p>Ashughes: /* Work Plan */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Work Plan =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>KEY DELIVERABLES</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
; Mozilla IRIS<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
: ☑ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
: ☐ Develop and execute a deployment strategy<br />
: ☐ Develop and execute a communications strategy<br />
: ☐ Develop and execute a community participation strategy<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☐ Set up a mini deployment at the YVR office<br />
; Carry Over<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}<br />
<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>NOV 19 - NOV 23, 2018</big><br />
|-<br />
|<br />
: ☑ Create a communications page in the github wiki - [https://github.com/mozilla/iris/wiki/Communicating-with-the-Iris-team]<br />
: ☐ Develop a Mozilla Iris test case - [https://github.com/mozilla/iris/issues/106 #106]<br />
: ☑ Set up a MacOS machine to run Iris tests and vet deployment process<br />
: ☐ Work with the Release QA SV team to deploy Iris for update testing Beta builds<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1204142User:Ashughes2018-11-19T22:08:47Z<p>Ashughes: /* Work Plan */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Work Plan =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>KEY DELIVERABLES</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
; Mozilla IRIS<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
: ☑ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
: ☐ Develop and execute a deployment strategy<br />
: ☐ Develop and execute a communications strategy<br />
: ☐ Develop and execute a community participation strategy<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☐ Set up a mini deployment at the YVR office<br />
; Carry Over<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}<br />
<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>NOV 19 - NOV 23, 2018</big><br />
|-<br />
|<br />
: ☑ Create a communications page in the github wiki - [https://github.com/mozilla/iris/wiki/Communicating-with-the-Iris-team]<br />
: ☐ Develop a Mozilla Iris test case - [https://github.com/mozilla/iris/issues/106 #106]<br />
: ☑ Set up a MacOS machine to run Iris tests and vet deployment process<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1204141User:Ashughes2018-11-19T22:07:42Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Work Plan =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>KEY DELIVERABLES</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
; Mozilla IRIS<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
: ☑ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
: ☐ Develop and execute a deployment strategy<br />
: ☐ Develop and execute a communications strategy<br />
: ☐ Develop and execute a community participation strategy<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
; Carry Over<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}<br />
<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>NOV 19 - NOV 23, 2018</big><br />
|-<br />
|<br />
: ☑ Create a communications page in the github wiki - [https://github.com/mozilla/iris/wiki/Communicating-with-the-Iris-team]<br />
: ☐ Develop a Mozilla Iris test case - [https://github.com/mozilla/iris/issues/106 #106]<br />
: ☑ Set up a MacOS machine to run Iris tests and vet deployment process<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203535User:Ashughes/Iris2018-11-07T17:49:04Z<p>Ashughes: /* Deployment */</p>
<hr />
<div>== Monthly Progress Reports ==<br />
* [[User:Ashughes/Iris/MPR_template|Template]]<br />
* [[User:Ashughes/Iris/MPR_2018.11|November 2018]] (''coming early December 2018'')<br />
<br />
== Post 1.0 Strategy and Planning ==<br />
==== Deployment ====<br />
* Long-term strategy<br />
* Short-term goals<br />
* Protocol and process<br />
* Engagement and outreach<br />
* Features vs bugs<br />
* Delineation of responsibility<br />
<br />
==== Community ====<br />
* Community Participation Guidelines - see also [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla CPG]<br />
* Pathways to participation<br />
* Mentors and mentorship<br />
* Communication channels<br />
<br />
==== Communications ====<br />
* Internal / Non-public<br />
* External / Public<br />
* Tools and their uses</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203534User:Ashughes/Iris2018-11-07T17:45:52Z<p>Ashughes: /* Communications */</p>
<hr />
<div>== Monthly Progress Reports ==<br />
* [[User:Ashughes/Iris/MPR_template|Template]]<br />
* [[User:Ashughes/Iris/MPR_2018.11|November 2018]] (''coming early December 2018'')<br />
<br />
== Post 1.0 Strategy and Planning ==<br />
==== Deployment ====<br />
<br />
==== Community ====<br />
* Community Participation Guidelines - see also [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla CPG]<br />
* Pathways to participation<br />
* Mentors and mentorship<br />
* Communication channels<br />
<br />
==== Communications ====<br />
* Internal / Non-public<br />
* External / Public<br />
* Tools and their uses</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203533User:Ashughes/Iris2018-11-07T17:41:49Z<p>Ashughes: /* Community */</p>
<hr />
<div>== Monthly Progress Reports ==<br />
* [[User:Ashughes/Iris/MPR_template|Template]]<br />
* [[User:Ashughes/Iris/MPR_2018.11|November 2018]] (''coming early December 2018'')<br />
<br />
== Post 1.0 Strategy and Planning ==<br />
==== Deployment ====<br />
<br />
==== Community ====<br />
* Community Participation Guidelines - see also [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla CPG]<br />
* Pathways to participation<br />
* Mentors and mentorship<br />
* Communication channels<br />
<br />
==== Communications ====</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203532User:Ashughes/Iris2018-11-07T17:39:54Z<p>Ashughes: /* Community */</p>
<hr />
<div>== Monthly Progress Reports ==<br />
* [[User:Ashughes/Iris/MPR_template|Template]]<br />
* [[User:Ashughes/Iris/MPR_2018.11|November 2018]] (''coming early December 2018'')<br />
<br />
== Post 1.0 Strategy and Planning ==<br />
==== Deployment ====<br />
<br />
==== Community ====<br />
* Community Participation Guidelines<br />
* Pathways to participation<br />
* Mentors and mentorship<br />
* Communication channels<br />
<br />
==== Communications ====</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203531User:Ashughes/Iris2018-11-07T17:36:52Z<p>Ashughes: /* Post 1.0 Strategy and Planning */</p>
<hr />
<div>== Monthly Progress Reports ==<br />
* [[User:Ashughes/Iris/MPR_template|Template]]<br />
* [[User:Ashughes/Iris/MPR_2018.11|November 2018]] (''coming early December 2018'')<br />
<br />
== Post 1.0 Strategy and Planning ==<br />
==== Deployment ====<br />
<br />
==== Community ====<br />
<br />
==== Communications ====</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203530User:Ashughes/Iris2018-11-07T17:36:30Z<p>Ashughes: </p>
<hr />
<div>== Monthly Progress Reports ==<br />
* [[User:Ashughes/Iris/MPR_template|Template]]<br />
* [[User:Ashughes/Iris/MPR_2018.11|November 2018]] (''coming early December 2018'')<br />
<br />
== Post 1.0 Strategy and Planning ==<br />
=== Deployment ===<br />
<br />
=== Community ===<br />
<br />
=== Communications ===</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203522User:Ashughes2018-11-07T16:55:32Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS ([[User:Ashughes/Iris|planning page]])<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☑ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a communications strategy for Mozilla Iris<br />
:: ☑ Set up an email for the Iris project (iris@mozilla.com)<br />
:: ☐ Set up a monthly report including work done, new deployments, and bugs found in product<br />
:: ☐ Public and non-public communications channels (IRC, Slack, Email, Mailing lists, Github, etc)<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203521User:Ashughes2018-11-07T16:50:18Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☑ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a communications strategy for Mozilla Iris<br />
:: ☑ Set up an email for the Iris project (iris@mozilla.com)<br />
:: ☐ Set up a monthly report including work done, new deployments, and bugs found in product<br />
:: ☐ Public and non-public communications channels (IRC, Slack, Email, Mailing lists, Github, etc)<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203520User:Ashughes2018-11-07T16:49:07Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☑ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a communications strategy for Mozilla Iris<br />
:: ☑ Set up an email for the Iris project (iris@mozilla.com)<br />
:: ☐ Set up a monthly report on the Iris project including work done, new deployments, and bugs found in product<br />
:: ☐ Public and non-public communications channels (IRC, Slack, Email, Mailing lists, Github, etc)<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris/MPR_template&diff=1203519User:Ashughes/Iris/MPR template2018-11-07T16:44:31Z<p>Ashughes: Created page with "= Mozilla Iris Monthly Progress Report: <MONTH> <YEAR> = The following highlights progress made, new contributors, success stories, and challenges across the Mozilla Iris proj..."</p>
<hr />
<div>= Mozilla Iris Monthly Progress Report: <MONTH> <YEAR> =<br />
The following highlights progress made, new contributors, success stories, and challenges across the Mozilla Iris project for the month of '''<MONTH> <YEAR>'''.<br />
<br />
== Core ==<br />
<br />
== Tests ==<br />
<br />
== Deployment ==<br />
<br />
== Bugs Found ==<br />
<br />
== Other ==</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203518User:Ashughes/Iris2018-11-07T16:38:58Z<p>Ashughes: /* Monthly Progress Reports */</p>
<hr />
<div>== Monthly Progress Reports ==<br />
* [[User:Ashughes/Iris/MPR_template|Template]]<br />
* [[User:Ashughes/Iris/MPR_2018.11|November 2018]] (''coming early December 2018'')</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/Iris&diff=1203517User:Ashughes/Iris2018-11-07T16:36:58Z<p>Ashughes: Created page with "= Monthly Progress Reports = * Template"</p>
<hr />
<div>= Monthly Progress Reports =<br />
* [[User:Ashughes/Iris/MPR_template|Template]]</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203515User:Ashughes2018-11-07T15:48:11Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a communications strategy for Mozilla Iris<br />
:: ☑ Set up an email for the Iris project (iris@mozilla.com)<br />
:: ☐ Set up a monthly report on the Iris project including work done, new deployments, and bugs found in product<br />
:: ☐ Public and non-public communications channels (IRC, Slack, Email, Mailing lists, Github, etc)<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203513User:Ashughes2018-11-07T15:29:16Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a communications strategy for Mozilla Iris<br />
:: ☑ Set up an email for the Iris project (iris@mozilla.com)<br />
:: ☐ Set up a monthly report on the Iris project including work done, new deployments, and bugs found in product<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203512User:Ashughes2018-11-07T15:28:50Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a communications strategy for Mozilla Iris<br />
:: ☑ Set up an email for the Iris project (iris@mozilla.com)<br />
:: ☐ Set up a monthly report on the Iris project, including work done, new deployments, and bugs found in product<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203445User:Ashughes2018-11-06T19:32:52Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a communications strategy for Mozilla Iris<br />
:: ☑ Set up an email for the Iris project (iris@mozilla.com)<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203300User:Ashughes2018-11-02T22:45:33Z<p>Ashughes: /* About */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not working on Firefox I volunteer with the Green Party of Canada, Green Party of British Columbia, and Green Party of Vancouver. <br />
<br />
In my spare time I'm usually hiking up some mountain or just traveling somewhere new with my partner.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203299User:Ashughes2018-11-02T22:43:27Z<p>Ashughes: /* About */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203298User:Ashughes2018-11-02T22:42:51Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
{| class="wikitable mw-collapsible" style="overflow:auto; width:800px"<br />
! style="text-align:left" | <big>2018 H2</big><br />
|-<br />
|<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
|}</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203297User:Ashughes2018-11-02T22:24:16Z<p>Ashughes: /* Contributions */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 H2 ==<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
<br />
== 2018 H1 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Develop clear requirements for the ideal PI Request system<br />
:: ☑ Conduct user interviews<br />
:: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Develop a workflow design of the PI Request system<br />
:: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
:: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
:: ☑ Revise MVP workflow design based on feedback<br />
: ⇒ Conduct a feasibility study of Service Now as a drop-in replacement of the PI Request system<br />
:: ☑ Review implementation requirements of MVP workflow design in Service Now<br />
:: ☐ Engage Service Now team in development of MVP system for testing<br />
:: ☐ Test implementation of Service Now based MVP for compliance to workflow<br />
:: ☐ Test implementation of Service Now based MVP with a PI test group<br />
: ⇒ Conduct a feasibility study of JIRA Service Desk<br />
::<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203296User:Ashughes2018-11-02T22:23:43Z<p>Ashughes: /* 2018 Q3 */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 Q3 ==<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
<br />
; Professional Development<br />
: ☐ Read ''Peopleware''<br />
: ☐ Read ''Managing Humans''<br />
<br />
; Mozilla IRIS Deployment Management<br />
: ☑ Vet the installation process for Mozilla IRIS<br />
:: ☑ Follow the setup steps on Windows 10 and document any issues ([https://github.com/mozilla/iris/issues/1395 <strike>1395</strike>])<br />
:: ☑ Follow the setup steps on Ubuntu 16.04 and document any issues ([https://github.com/mozilla/iris/issues/1397 <strike>1397</strike>])<br />
:: ☑ Follow the setup steps on MacOS Mojave and document any issues<br />
: ☐ Assist in recruiting an Outreachy intern to improve the control panel UI<br />
:: ☐ Review Outreachy intern proposals<br />
:: ☐ Narrow down a preferred candidate and discuss with the team<br />
: ☐ Develop a strategy to increase awareness of Mozilla IRIS across the organization<br />
: ☐ Develop a strategy to increase community participation in Mozilla IRIS<br />
: ☐ Develop a plan to deploy Mozilla IRIS to at least one team outside the Product Integrity group<br />
: ☑ Transition Alin Rus from WebRender benchmarking to IRIS test development<br />
: ☑ Transition Roxana Robotin from WebRTC test maintenance to IRIS test development<br />
<br />
== 2018 Q2 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Develop clear requirements for the ideal PI Request system<br />
:: ☑ Conduct user interviews<br />
:: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Develop a workflow design of the PI Request system<br />
:: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
:: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
:: ☑ Revise MVP workflow design based on feedback<br />
: ⇒ Conduct a feasibility study of Service Now as a drop-in replacement of the PI Request system<br />
:: ☑ Review implementation requirements of MVP workflow design in Service Now<br />
:: ☐ Engage Service Now team in development of MVP system for testing<br />
:: ☐ Test implementation of Service Now based MVP for compliance to workflow<br />
:: ☐ Test implementation of Service Now based MVP with a PI test group<br />
: ⇒ Conduct a feasibility study of JIRA Service Desk<br />
::<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203196User:Ashughes2018-10-31T23:57:36Z<p>Ashughes: /* 2018 Q3 */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 Q3 ==<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
<br />
'''Mozilla IRIS'''<br />
: ☐ Vet the installation process for Mozilla IRIS<br />
:: ☐ Follow the setup steps on Windows 10 and document any issues: [https://github.com/mozilla/iris/issues/1395 1395]<br />
:: ☐ Follow the setup steps on Ubuntu 16.04 and document any issues: [https://github.com/mozilla/iris/issues/1397 1397]<br />
:: ☐ Follow the setup steps on MacOS Mojave and document any issues<br />
<br />
== 2018 Q2 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Develop clear requirements for the ideal PI Request system<br />
:: ☑ Conduct user interviews<br />
:: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Develop a workflow design of the PI Request system<br />
:: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
:: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
:: ☑ Revise MVP workflow design based on feedback<br />
: ⇒ Conduct a feasibility study of Service Now as a drop-in replacement of the PI Request system<br />
:: ☑ Review implementation requirements of MVP workflow design in Service Now<br />
:: ☐ Engage Service Now team in development of MVP system for testing<br />
:: ☐ Test implementation of Service Now based MVP for compliance to workflow<br />
:: ☐ Test implementation of Service Now based MVP with a PI test group<br />
: ⇒ Conduct a feasibility study of JIRA Service Desk<br />
::<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203195User:Ashughes2018-10-31T23:29:14Z<p>Ashughes: /* 2018 Q3 */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 Q3 ==<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
<br />
'''Mozilla IRIS'''<br />
: ☐ Vet the installation process for Mozilla IRIS<br />
:: ☐ Follow the setup steps on Windows 10 and document any issues - [https://github.com/mozilla/iris/issues/1395 1395]<br />
:: ☐ Follow the setup steps on Ubuntu 16.04 and document any issues<br />
:: ☐ Follow the setup steps on MacOS Mojave and document any issues<br />
<br />
== 2018 Q2 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Develop clear requirements for the ideal PI Request system<br />
:: ☑ Conduct user interviews<br />
:: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Develop a workflow design of the PI Request system<br />
:: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
:: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
:: ☑ Revise MVP workflow design based on feedback<br />
: ⇒ Conduct a feasibility study of Service Now as a drop-in replacement of the PI Request system<br />
:: ☑ Review implementation requirements of MVP workflow design in Service Now<br />
:: ☐ Engage Service Now team in development of MVP system for testing<br />
:: ☐ Test implementation of Service Now based MVP for compliance to workflow<br />
:: ☐ Test implementation of Service Now based MVP with a PI test group<br />
: ⇒ Conduct a feasibility study of JIRA Service Desk<br />
::<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203194User:Ashughes2018-10-31T23:27:53Z<p>Ashughes: /* 2018 Q3 */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 Q3 ==<br />
'''Legend''': ☑ Completed task | ☐ Upcoming task<br />
<br />
'''Mozilla IRIS'''<br />
: ☐ Vet the installation process for Mozilla IRIS<br />
:: ☐ Follow the setup steps on Windows 10 and document any issues<br />
:: ☐ Follow the setup steps on Ubuntu 16.04 and document any issues<br />
:: ☐ Follow the setup steps on MacOS Mojave and document any issues<br />
<br />
== 2018 Q2 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Develop clear requirements for the ideal PI Request system<br />
:: ☑ Conduct user interviews<br />
:: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Develop a workflow design of the PI Request system<br />
:: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
:: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
:: ☑ Revise MVP workflow design based on feedback<br />
: ⇒ Conduct a feasibility study of Service Now as a drop-in replacement of the PI Request system<br />
:: ☑ Review implementation requirements of MVP workflow design in Service Now<br />
:: ☐ Engage Service Now team in development of MVP system for testing<br />
:: ☐ Test implementation of Service Now based MVP for compliance to workflow<br />
:: ☐ Test implementation of Service Now based MVP with a PI test group<br />
: ⇒ Conduct a feasibility study of JIRA Service Desk<br />
::<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1203193User:Ashughes2018-10-31T23:23:29Z<p>Ashughes: </p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 Q3 ==<br />
: ☑ Completed task<br />
: ☐ Upcoming task<br />
<br />
== 2018 Q2 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Develop clear requirements for the ideal PI Request system<br />
:: ☑ Conduct user interviews<br />
:: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Develop a workflow design of the PI Request system<br />
:: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
:: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
:: ☑ Revise MVP workflow design based on feedback<br />
: ⇒ Conduct a feasibility study of Service Now as a drop-in replacement of the PI Request system<br />
:: ☑ Review implementation requirements of MVP workflow design in Service Now<br />
:: ☐ Engage Service Now team in development of MVP system for testing<br />
:: ☐ Test implementation of Service Now based MVP for compliance to workflow<br />
:: ☐ Test implementation of Service Now based MVP with a PI test group<br />
: ⇒ Conduct a feasibility study of JIRA Service Desk<br />
::<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1192680User:Ashughes2018-04-23T15:10:09Z<p>Ashughes: /* PI Requests v2 */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Develop clear requirements for the ideal PI Request system<br />
:: ☑ Conduct user interviews<br />
:: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Develop a workflow design of the PI Request system<br />
:: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
:: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
:: ☑ Revise MVP workflow design based on feedback<br />
: ⇒ Conduct a feasibility study of Service Now as a drop-in replacement of the PI Request system<br />
:: ☑ Review implementation requirements of MVP workflow design in Service Now<br />
:: ☐ Engage Service Now team in development of MVP system for testing<br />
:: ☐ Test implementation of Service Now based MVP for compliance to workflow<br />
:: ☐ Test implementation of Service Now based MVP with a PI test group<br />
: ⇒ Conduct a feasibility study of JIRA Service Desk<br />
::<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1192648User:Ashughes2018-04-23T07:30:58Z<p>Ashughes: /* WebRTC Test Automation */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Conduct user interviews<br />
: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
: ☑ Revise MVP workflow design<br />
: ⇒ Discuss implementation of MVP workflow design in Service Now ''-- Pending return of Sean Rich from PTO (2018-04-03)''<br />
: ☐ Review implementation of MVP workflow design in Service Now<br />
: ☐ Test implementation of MVP workflow design in Service Now with real users<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* '''Tasks''':<br />
** Update and Run WebRTC mochitests via {{bug|1454644}} - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1192647User:Ashughes2018-04-23T07:25:29Z<p>Ashughes: /* WebRTC Test Automation */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Conduct user interviews<br />
: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
: ☑ Revise MVP workflow design<br />
: ⇒ Discuss implementation of MVP workflow design in Service Now ''-- Pending return of Sean Rich from PTO (2018-04-03)''<br />
: ☐ Review implementation of MVP workflow design in Service Now<br />
: ☐ Test implementation of MVP workflow design in Service Now with real users<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
* {{bug|1454644}} - Update and Run WebRTC mochitests - [https://docs.google.com/spreadsheets/d/17rWf-eAI42Bv6_c2IvhHYhck8IOZeFbK0uXcaB6kncg/edit#gid=1527710909 doc]<br />
<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes/PI_Requests_v2&diff=1192128User:Ashughes/PI Requests v22018-04-10T22:56:29Z<p>Ashughes: /* Requested Features */</p>
<hr />
<div>= Service Model SLA =<br />
'''''<big style="background:#FFC">Update: SLA has been revised (26-JAN-2018)</big>'''''<br />
<br />
Our commitment is that <strike>90% of requests get a response within 48 hours</strike> 80% of requests get a response within 48 hours and 100% of requests get a response within one week. That doesn't mean that we have to work on every request but we at least need to triage, prioritize, and respond to the request within the SLA. If the request has been deemed a high priority it will be assigned and followed up by the assignee. If the request has been deemed a low priority a response should be given which explains the reason and when the requestor can expect work to begin.<br />
<br />
= How it Works =<br />
# Email is sent to pi-request at mozilla dot com<br />
# Request details are added to the [https://docs.google.com/spreadsheets/d/1EzOQrVsPOZUW2m98B3yxiF48rFdkisV5fnn96Wdo8Bw/edit#gid=0 spreadsheet]<br />
# Someone responds to the request in accordance with SLA<br />
# Request is completed in due course, spreadsheet is updated along the way (ideally)<br />
<br />
= Roadmap =<br />
{| <br />
|-<br />
| [[#Phase_1:_Stakeholder_Engagement|Phase 1: Stakeholder Engagement]]<br />
| {{done|}}<br />
|-<br />
| style="padding-left:20px" | [[#Gathering_Feedback|Phase 1a: Gather Feedback]]<br />
| {{done|}}<br />
|-<br />
| style="padding-left:20px" | [[#Interviews|Phase 1b: Interviews]]<br />
| {{done|}}<br />
|-<br />
| Phase 2: Documenting Requirements<br />
| {{ok|}}: Due mid-Feb 2018<br />
|-<br />
| Phase 3: Implementing a Prototype<br />
| {{ok|}}: Due early-Mar 2018<br />
|-<br />
| Phase 4: Stakeholder Review<br />
| Due 1H'2018<br />
|-<br />
| Phase 5: Iteration<br />
| Due 2H'2018<br />
|-<br />
|}<br />
<br />
= Phase I: Stakeholder Engagement =<br />
== Gathering Feedback ==<br />
In this first part of Phase 1, I will gather feedback from stakeholders (anyone who's interacted PIRv1.0) via survey and document any key findings.<br />
<br />
=== Survey Results ===<br />
; Responses<br />
* 32 / 108 responded (30% return rate)<br />
* 59% from Firefox/Platform developers<br />
* 22% from QA<br />
* 19% from other groups<br />
<br />
; Key Findings<br />
{| class="wikitable sortable"<br />
! <br />
! style="width:10%" | Overall<br />
! style="width:10%" | Engineers<br />
! style="width:10%" | QA<br />
! style="width:10%" | Others<br />
|-<br />
| Satisfaction<br />
| 3.3<br />
| 3.4<br />
| 3.0<br />
| 3.2<br />
|}<br />
<br />
{| class="wikitable sortable"<br />
! rowspan="2" | <br />
! colspan="4" | Agree<br />
! colspan="4" | Disagree<br />
! rowspan="2" | Score<br />
|-<br />
! style="width:10%" | Overall<br />
! style="width:10%" | Engineers<br />
! style="width:10%" | QA<br />
! style="width:10%" | Others<br />
! style="width:10%" | Overall<br />
! style="width:10%" | Engineers<br />
! style="width:10%" | QA<br />
! style="width:10%" | Others<br />
|-<br />
| Better than Bugzilla?<br />
| 19%<br />
| 10%<br />
| 43%<br />
| 20%<br />
| 41%<br />
| 52%<br />
| 14%<br />
| 40%<br />
| -22%<br />
|-<br />
| Better than Github?<br />
| 19%<br />
| 16%<br />
| 14%<br />
| 40%<br />
| 34%<br />
| 37%<br />
| 43%<br />
| 20%<br />
| -21%<br />
|-<br />
| Better than Trello?<br />
| 31%<br />
| 19%<br />
| 29%<br />
| 40%<br />
| 31%<br />
| 26%<br />
| 57%<br />
| 20%<br />
| 0%<br />
|-<br />
| Better than Wiki?<br />
| 31%<br />
| 26%<br />
| 29%<br />
| 60%<br />
| 13%<br />
| 21%<br />
| 0%<br />
| 0%<br />
| +18%<br />
|-<br />
|}<br />
<br />
{| class="wikitable sortable"<br />
! rowspan="2" | The PI Request system...<br />
! colspan="4" | Agree<br />
! colspan="4" | Disagree<br />
! style="width:5%" rowspan="2" | Score<br />
|-<br />
! style="width:5%" | Overall<br />
! style="width:5%" | Engineers<br />
! style="width:5" | QA<br />
! style="width:5%" | Others<br />
! style="width:5%" | Overall<br />
! style="width:5%" | Engineers<br />
! style="width:5%" | QA<br />
! style="width:5%" | Others<br />
|-<br />
| provides clear lines of communication<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | +7<br />
|-<br />
| makes it easier to plan resources<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | +5<br />
|-<br />
| provides a clear status of work<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | -3<br />
|-<br />
| provides a clear scope of work<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | +3<br />
|-<br />
| provides a clear understanding of the process<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
|-<br />
| reveals artifacts/history of a request<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | -4<br />
|-<br />
| has data that is current and accurate<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | -1<br />
|-<br />
| provides a single, consolidated source of truth<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | +1<br />
|-<br />
| makes it easy to find a specific request<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0 <br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | -2<br />
|-<br />
| makes it easy to report a request<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 0 <br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | +5<br />
|-<br />
| provides rapid response to testing needs<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0 <br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | +2<br />
|}<br />
<br />
== Interviews ==<br />
'''''<big style="background:#FFC">Update: This phase has been completed (26-JAN-2018)</big>'''''<br />
<br />
In this second part of Phase 1, I will conduct interviews with survey respondents to clarify and do a deeper dive into the feedback they submitted, and their requirements. While these interviews are happening the survey should be sent again to those who did not respond, including any stakeholder who may have been left out.<br />
<br />
To respect the privacy and anonymity of participants individual responses will not be revealed. Key findings will be documented as part of the next phase.<br />
<br />
= Phase II: Requirements Documentation =<br />
<span style="background:#FFC"><br />
<big style="font-weight:bold">Update: This phase has begun in tandem with Phase III (26-JAN-2018)</big><br /><br />
After consultation with peers, Service Now has emerged as the best possible candidate on the surface. The next step is to develop a workflow design document together for the Service Now team. This document will be reviewed and the workflows implemented in the current Service Now instance for experimentation. The design document should be completed by mid-February with the Service Now setup implemented by early-March.</span><br />
<br />
This phase will be completed in a couple stages. First I will summarize the feedback I received through interviews into criteria that can be used to evaluate other tools and pain points that can be addressed in the current tool in the short-term. Second I will document the most common workflows so that those can be implemented in the initial version of the new tool. Anything that does not fit in to either of these stages will be documented for implementation in future iterations.<br />
<br />
Anticipated Areas of Concern:<br />
* Metrics<br />
* Alerting<br />
* Linking to other tools (bugzilla, github, trello, etc)<br />
* Easy to make a request<br />
* Easy to discover request status<br />
* Clear task assignment<br />
* Clear task scope<br />
* Clear indication/definition of "done"<br />
<br />
== Documenting Key Criteria ==<br />
=== Requested Features ===<br />
* Be able to trigger sign-off emails in a predefined format either by clicking a button or automatically when certain criteria are met.<br />
* Templatize the requestor interface to enforce high-quality standards for incoming requests and to eliminate the guess work of what information is needed.<br />
* Send periodic status updates to the requestor, particularly if the task is large in scope.<br />
* Be able to set feedback intervals (realtime, weekly, on completion, etc)<br />
* Be able to see overall progress at a team level<br />
* Work should be tagged by target milestone<br />
* Be able to search for a specific request or a bucket of requests more easily<br />
* Be able to see which features come in / ship late<br />
* Be able to hide some requests by default particularly in case when security is a concern<br />
* If we use an existing tool make sure the branding clearly differentiates PI so that requests doing inadvertently go into the wrong pipeline (eg. we don't want SD requests in PI, nor PI requests in SD)<br />
* Be able to archive old requests so they don't add noise to existing/incoming work but searchable for historical/metrics purposes<br />
* Ensure we maintain the improved communication between QA and Dev, reduce the need for QA to hunt down work they should be doing<br />
* Be able to trigger one-to-one follow up conversations either automatically or manually once a task has been assigned (often times these conversations inform testing needs and eliminates guess work)<br />
* Be able to request features and do sentiment analysis of the tool<br />
* Be able to estimate scope accurately<br />
* Be able to request specific skills to streamline assignment of qualified testers<br />
* Facilitate a kickoff meeting and have video/transcript as an artifact of the request<br />
* Have a list of commonly requested follow up info (build, steps, screenshots, etc)<br />
* Make sure everything is clearly documented and that there are clear examples of a "good" request<br />
* Be able to have a clear indication of turnaround time on when a request will be acknowledged, assigned, and completed<br />
* Important to have continuity of tester, have them participate in meetings, etc. The system should track a testers previous work so requests can be assigned according to not just skills but developed experience/relationships.<br />
* Testers need to be able to ask questions and make suggestions of things the requestor may not anticipate<br />
* Need to provide a value proposition over simply need-info flagging a tester on a bug, the key is to have someone assigned quickly<br />
* Be able to submit a request by sending an email based on a predefined template<br />
* Requestor should be able to update the task if scope/timelines change<br />
* Be able to track various stages of sign-off (eg. Trello supports a checklist -- Mid-Nightly, Pre-Beta, Pre-Release)<br />
* Request should show its own history including comments<br />
* Users should be able to subscribe to a request or categories of requests<br />
* Users should be able to get notifications of changes<br />
* Integrate into existing workflows (EPMs use Trello, Developers use Bugzilla/Github)<br />
* Requests should hold requestors hand in terms of testing needs, platforms, devices, necessary reference documents, skills needs, timelines, etc<br />
* Enable UX with tester to develop clear sense of testing needs and complexity<br />
* If a feature is dependent on a PI request and that feature moves milestones in Trello the PI Request should be updated and stakeholders notified<br />
* Develop a workflow for requests that come in really early, on schedule, late, and adhoc<br />
* Request status should include external dependencies (eg. under review, under UX, ready for QA, QA complete, ready for release)<br />
* Periodically survey users of the system to gauge satisfaction<br />
* Be able to report on various metrics including ability to scope accurately, ability to complete work, ability to resource according to incoming demands, ability to meet SLA, plan for future, etc<br />
* Alerting to mitigate requests slipping through the cracks or slipping deadlines<br />
* Autocompletion of similar requests to prevent submitting duplicates but also to assist with cloning a similar task<br />
* Be able to set up and schedule recurring requests<br />
* Be able to identify if a request is necessary or not (sometimes people file requests just to be safe) and have a workflow to deal with unnecessary requests or prevent unnecessary requests from being filed altogether<br />
* Have clear definitions of jargon, terminology, status, etc<br />
* Not everything belongs in PI, need a way to weed these out before submission and suggest more appropriate tools (eg, Bugzilla)<br />
* When conversations happen on Slack/IRC or elsewhere have a way to include that as an artifact of the request<br />
* Automatic translation would be useful for ESL users<br />
* Think about community participation in PI as a usecase<br />
* Be able to resurrect cold requests<br />
* Be able to track PI resource allocation and availability<br />
* Not everything has feature release criteria -- feature release criteria should be baked in to the system but be smarter about when/why users are prompted for it<br />
* Suggest types of testing and needs based on similar requests<br />
* Mapping to other tracking docs (eg. Feature release tracking GDocs, Trello, Bugzilla, etc) would be useful and perhaps could be made redundant if the new system provides these features<br />
* Be able to prioritize work at large in the same place we track individual request status<br />
* Be able to provide more transparency around prioritization decisions<br />
* Be able to deprioritize tasks<br />
* Be able to query for specific tasks or terms<br />
* For services it would be useful to call out client vs server-side testing<br />
* Be able to delegate sub-requests and roll out the workload for a project<br />
* Be able to request multiple people to work on a task or different aspects of a task<br />
* Provide regular feedback on the progress of a request<br />
* Provide regular feedback on interacting with PI to identify opportunities for tools / process improvements<br />
* Need to be able to have a relationship between Trello, Bugzilla, and PI for security reviews (all features should be triaged for Security Assurance)<br />
* Support tracking work by due date<br />
* Dashboard of work in progress, work in queue, work completed and metrics to support resourcing decisions<br />
<br />
The PI Request system should...<br />
*<br />
<br />
=== Pain Points ===<br />
* Submitting a PI Request seems redundant if PI resources will not be assigned; particularly true in cases where a <u><b>team has dedicated QA</b></u> or when the work involved is strictly <b><u>landing code via Bugzilla</u></b> (eg. updates to Talos, infrastructure configuration changes, etc).<br />
** Perhaps for teams with a dedicated QA what makes the most sense is A) no requests come through PI unless additional help is required (ie. not enough cycles) or B) QA person is technically part of PI although permanently assigned to their team and *all* their requests come through PI but are automatically assigned to them without prioritizaiton -- in this case handing it off for prioritization by SV is at their discretion. (Should run this past teams that have this Mobile and Services)<br />
* It's very difficult to know the current status of a request, both in terms of requests in backlog and active requests. Some people send an email to the person assigned to the work others try to navigate the spreadsheet.<br />
* PMs use Trello or Github cards to track on-going and upcoming feature work. These systems need to work together and integrate more easily. There needs to be a single source of truth for the entire life-cycle of a feature and that easily visualizes the entire scope of completed/active/incoming work.<br />
* Automated testing is done, for the most part, in our CI systems. There needs to be a way to integrate these results.<br />
* It's difficult to know when (timing and what projects) a PI Request is needed. Not all work needs a PI Request.<br />
* It's difficult to know if a Trello card has a matching PI Request and vice versa due to a discrepancy in naming convention and a lack of automatic or forced-manual linkage.<br />
* Request process we go though every release (ie. get your requests in by X) requires a lot of prodding of developers. If I know it’s going to ship in a later milestone it would be nice to be able to get that in early and tag it so I don’t have to worry about it.<br />
* Not all requests coming in to PI need testing but it would still be useful from a backlog Management perspective<br />
* It's difficult to see a high-level overview of the status of work (eg. With Trello it's easy to see where the overall work is at -- which cards are in each bucket)<br />
* While past requests can be filtered out it adds to the overhead of the spreadsheet<br />
* Cannot view testcases for other, similar requests<br />
* Cannot view other requests to use as an example<br />
* Disparate systems for tracking (BZ, PI) and comms (ML, BZ, Email, Vidyo)<br />
* Some testers need mentorship when it comes to a request of a highly technical nature, eg. writing scripts to test/debug an issue. <br />
* There is a lot of back and forth before a request is ready to be worked on<br />
* Not all requests are features; some are requests for automation, regression testing, A/B testing, etc; asking for information not relevant to the request wastes time<br />
* "Timeline"/"Duration" is really confusing and poorly defined <br />
* Testplans are not immediately discoverable unless requested<br />
* Need to improve clarity and transparency around where my request is in queue, priority and prioritization process, and current status<br />
* Its unclear who is consuming the information added/revised in spreadsheet, comments in particular<br />
* API testing is usually covered well by automation and we just need help edge-case hunting, this use case isn't covered well by the current system.<br />
* Scope needs to be locked in to prevent creeping demands on resources<br />
* It is unclear sometimes if/when/who should respond to a request<br />
* People are not proactive enough about filing security review requests<br />
* There is not a good way to track when something is due apart from Firefox milestones or ambiguous priority numbers<br />
<br />
=== Roles ===<br />
* Customer: a person submitting a request<br />
* Manager: a person managing the incoming requests<br />
* Handler: a person working on a request<br />
<br />
=== Workflows ===<br />
QA PMs:<br />
* Check Trello 2x/week<br />
* Add any new features to a tracking spreadsheet<br />
* Cross reference feature tracking spreadsheet to PI spreadsheet<br />
* Other team leads will triage bugzilla for fix verifications<br />
<br />
Developers:<br />
* <br />
<br />
EPMs:<br />
* <br />
<br />
Release Managers:<br />
* <br />
<br />
QA Engineers:<br />
* <br />
<br />
Automation Engineers:<br />
* <br />
<br />
Security Engineers:<br />
* Current workflow: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=66653753<br />
* Proposed workflow:<br />
** Requests continue to be made via PI<br />
** Follow-up work to be tracked in Bugzilla<br />
** Trello to be used to triage for work needing a security review<br />
<br />
=== Suggested V1 Tweaks ===<br />
* Track milestones<br />
* Track scope estimations and actuals<br />
* Separate spreadsheets per milestone with a single repository (could be a wiki page)<br />
* Enforce manual linkage between Trello and PI Requests via template<br />
<br />
== Workflow Designs ==<br />
* [https://docs.google.com/drawings/d/1g2iNfSAhrEOcRBULNJY7ovbiH2Yvy8n5FukOjKTtHWo/edit Workflow Design v1]<br />
* [https://docs.google.com/document/d/1dalIhgKAgsce66tuiI20mhpCpkp9wPT9-_cnCIqFgz4/edit Feedback from Rares and Andrei]<br />
<br />
= Phase III: Implementing a Prototype =<br />
<span style="background:#FFC"><br />
<big style="font-weight:bold">Update: This phase has begun in tandem with Phase II (26-JAN-2018)</big><br /><br />
After consultation with peers, Service Now has emerged as the best possible candidate on the surface. The next step is to develop a workflow design document together for the Service Now team. This document will be reviewed and the workflows implemented in the current Service Now instance for experimentation. The design document should be completed by mid-February with the Service Now setup implemented by early-March.</span><br />
<br />
In this phase, I will take the criteria identified in Phase II and use that to evaluate the best candidate tool to use as a foundation for v2.<br />
<br />
Possible Tools<br />
* Trello<br />
* Bugzilla<br />
* Service-Now (aka HUB)<br />
* Google Doc<br />
* Wiki<br />
* ...</div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1191942User:Ashughes2018-04-06T22:23:27Z<p>Ashughes: /* PI Automation */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Conduct user interviews<br />
: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
: ☑ Revise MVP workflow design<br />
: ⇒ Discuss implementation of MVP workflow design in Service Now ''-- Pending return of Sean Rich from PTO (2018-04-03)''<br />
: ☐ Review implementation of MVP workflow design in Service Now<br />
: ☐ Test implementation of MVP workflow design in Service Now with real users<br />
<br />
=== Benchmarking ===<br />
; <big>''OKR: Lead development and maintenance of automated tests for Quantum benchmarking''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
=== WebRTC Test Automation ===<br />
; <big>''OKR: Lead development and maintenance of automated tests''</big><br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
=== Firefox UI Tests ===<br />
; <big>''OKR: Determine path forward for so-called deprecated Firefox UI tests''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
=== Metrics-Graphics-GFX ===<br />
; <big>''OKR: Determine path forward for metrics-graphics-gfx dashboard''</big><br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1191938User:Ashughes2018-04-06T22:19:23Z<p>Ashughes: /* Bookmarks */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Conduct user interviews<br />
: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
: ☑ Revise MVP workflow design<br />
: ⇒ Discuss implementation of MVP workflow design in Service Now ''-- Pending return of Sean Rich from PTO (2018-04-03)''<br />
: ☐ Review implementation of MVP workflow design in Service Now<br />
: ☐ Test implementation of MVP workflow design in Service Now with real users<br />
<br />
=== PI Automation ===<br />
; <big>''OKR: Lead project teams in developing and maintaining automated tests''</big><br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
===== WebRTC =====<br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
===== Firefox UI Tests =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
===== Benchmarking =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
===== Metrics-Graphics-GFX =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1191937User:Ashughes2018-04-06T22:19:12Z<p>Ashughes: /* Activity Stream */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Conduct user interviews<br />
: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
: ☑ Revise MVP workflow design<br />
: ⇒ Discuss implementation of MVP workflow design in Service Now ''-- Pending return of Sean Rich from PTO (2018-04-03)''<br />
: ☐ Review implementation of MVP workflow design in Service Now<br />
: ☐ Test implementation of MVP workflow design in Service Now with real users<br />
<br />
=== PI Automation ===<br />
; <big>''OKR: Lead project teams in developing and maintaining automated tests''</big><br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
===== Bookmarks =====<br />
* '''Owners''': George Echim, Ioana Crisan, Paul Silaghi<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1aux1g-iUnsESFLd9tzmQp1ZskPTNbmt0uo1GdM7ZpRs/edit#gid=1146575934 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 14 Resolved, 30% Complete<br />
<br />
<bugzilla>{"blocks":"1419383"}</bugzilla><br />
<br />
===== WebRTC =====<br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
===== Firefox UI Tests =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
===== Benchmarking =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
===== Metrics-Graphics-GFX =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashugheshttps://wiki.mozilla.org/index.php?title=User:Ashughes&diff=1191717User:Ashughes2018-04-03T21:32:53Z<p>Ashughes: /* PI Requests v2 */</p>
<hr />
<div>= About =<br />
[[File:ashughes-avatar.png|120px|thumb|right]]<br />
<br />
My name is Anthony Hughes (typically go by ''ashughes'') and I work as a quality engineer on Mozilla's DOM team from Mozilla's office in Vancouver, Canada. <br />
<br />
I was introduced to open source (and Mozilla) in 2006 by David Humphrey, a professor at Seneca College in Toronto, Ontario, Canada. After volunteering for a few years, I transitioned to being a paid contributor in 2010. Starting out as an add-on reviewer I became involved with QA (quality assurance), testing Firefox features, driving Firefox releases, developing strategies, and running test events for the community. I lead a QA strategy to ship the first version of Firefox Hello (WebRTC based calling in the browser) and developed experiments to test GPU Process (a foundational piece of the Quantum architecture). <br />
<br />
I am currently a member of the Product Integrity group working on improvements in automation coverage and transitioning to a more robust tool for managing incoming requests.<br />
<br />
When I'm not trying to make Firefox better, I'm usually hiking up some mountain or just traveling somewhere new, always with my camera in tow.<br />
<br />
= Contact Info =<br />
* IRC: ashughes (usually in #content, #qa, and #vancouver on [irc://irc.mozilla.org/ irc.mozilla.org])<br />
* Blog: https://ashughes.com/<br />
* E-mail: [mailto:ahughes@mozilla.com ahughes@mozilla.com]<br />
* Twitter: [https://twitter.com/ashughes @ashughes]<br />
* Availability: I'm typically online between 09:00 and 17:00 PDT/PST (UTC-8/UTC-9)<br />
<br />
= Contributions =<br />
== 2018 ==<br />
=== PI Requests v2 ===<br />
; OKR: Drive creation of a proof-of-concept tool to replace the mailing list / spreadsheet ([https://wiki.mozilla.org/User:Ashughes/PI_Requests_v2 wiki])<br />
<br />
; Tasks<br />
: ☑ Conduct user interviews<br />
: ☑ Document requirements of the ideal system based on user feedback<br />
: ☑ Fix low-hanging fruit within the current system<br />
: ☑ Draft a workflow design encompassing the minimum viable end-to-end workflow<br />
: ☑ Get feedback on workflow design from key stakeholders (Softvision, PI Management, Service Now)<br />
: ☑ Revise MVP workflow design<br />
: ⇒ Discuss implementation of MVP workflow design in Service Now ''-- Pending return of Sean Rich from PTO (2018-04-03)''<br />
: ☐ Review implementation of MVP workflow design in Service Now<br />
: ☐ Test implementation of MVP workflow design in Service Now with real users<br />
<br />
=== PI Automation ===<br />
; <big>''OKR: Lead project teams in developing and maintaining automated tests''</big><br />
<br />
What are the metrics for this project?<br />
* number of defects found by automation?<br />
* time spent on implementation of a specific test?<br />
* time spent on maintenance of a specific test?<br />
* time saved vs manual testing?<br />
* key deliverable such as a dashboard or audit?<br />
<br />
===== Activity Stream =====<br />
* '''Owners''': George Echim, Ioana Crisan, Paul Silaghi<br />
* '''Code''': [https://github.com/mozilla/activity-stream github] (merged to [https://dxr.mozilla.org/mozilla-central/source/browser/extensions/activity-stream/test mozilla-central] weekly)<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1aux1g-iUnsESFLd9tzmQp1ZskPTNbmt0uo1GdM7ZpRs/edit#gid=931456630 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 31 Open , 13 Resolved, 29% Complete<br />
<bugzilla>{"blocks":"1410333"}</bugzilla><br />
<br />
===== Bookmarks =====<br />
* '''Owners''': George Echim, Ioana Crisan, Paul Silaghi<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1aux1g-iUnsESFLd9tzmQp1ZskPTNbmt0uo1GdM7ZpRs/edit#gid=1146575934 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 14 Resolved, 30% Complete<br />
<br />
<bugzilla>{"blocks":"1419383"}</bugzilla><br />
<br />
===== WebRTC =====<br />
* '''Owners''': Roxana Robotin (reporting to Jan-Yvar)<br />
* '''Code''': [https://hg.mozilla.org/mozilla-central mozilla-central]<br />
* '''Tracking''': [https://docs.google.com/spreadsheets/d/1bi89fKZ8rGkHxi_4aZwz1ZnxfUYQa7oODsTR_WmC61s/edit#gid=1282602213 spreadsheet]<br />
* '''Dashboard''': ?<br />
* '''Status''':<br />
** '''2018-04-03''': 6 Open, 0 Resolved, 0% Complete<br />
<br />
<bugzilla>{"blocks":"1405876"}</bugzilla><br />
<br />
===== Firefox UI Tests =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| ?<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| ''<link to results dashboard>''<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| Matt Howell [https://docs.google.com/document/d/1KFtZgd2zbolo7G_7lq8Nle8gnOoUr21l4r-vdwiS-G0/edit?ts=5aa2df6b explains the reason] the Update tests are disabled. Functional and Puppeteer tests need to be audited.<br /><br />
<u>Local Testrun - Linux x86_64 - 2018-03-21</u>:<br />
<pre><br />
SUMMARY<br />
-------<br />
7:22.40 INFO passed: 86<br />
7:22.40 INFO failed: 1<br />
7:22.40 INFO todo: 3 (skipped: 1)<br />
7:22.40 INFO <br />
FAILED TESTS<br />
-------<br />
7:22.40 INFO test_initial_download.py test_initial_download.TestSafeBrowsingInitialDownload.test_safe_browsing_initial_download<br />
7:22.40 SUITE_END<br />
</pre><br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Set up a local environment to run the tests locally and see what happens<br />☐ Analyze the result of the tests<br />
|}<br />
<br />
===== Benchmarking =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| Alin Rus (reporting to Milan)<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| https://github.com/Top5Softvision/Top5_Benchmark<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| https://docs.google.com/spreadsheets/d/1LxEcm8Fz1tRU9s9HhIOlHdktO_a5UEEtw6bemfjq0h4/edit?usp=sharing<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| https://docs.google.com/document/d/1UT8GTcVUQDYqCySNNhSoRBnIOiJa7TjN0GAkDyFLEFA/edit<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Finish writing tests against Youtube<br />☐ Begin work on automated dashboard<br />
|}<br />
<br />
===== Metrics-Graphics-GFX =====<br />
{|<br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Owners</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Code</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Dashboard</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Documentation</u>:<br />
| <br />
|-<br />
| style="text-align:right; vertical-align:top" | <u>Next Steps</u>:<br />
| ☐ Anthony to review project status with Milan<br /><br />
|}<br />
<br />
== 2017 ==<br />
=== 2017 Q1 ===<br />
* ☐ something to do<br />
* ☑ something done<br />
* ✓ something done<br />
* ✔ something done<br />
<br />
☐ something to do <br/><br />
☑ something done <br/><br />
✓ something done <br/><br />
✔ something done <br/><br />
<br />
== 2016 ==<br />
=== 2016 Q4 ===<br />
{|<br />
|-<br />
| '''1. Prototype a dashboard of long-term Graphics stability trends'''<br />
* {{done|}} architect a system to automate updating chart data periodically beyond the 6-month Socorro API limit<br />
** {{done|}} create a python script to clone crash data from Socorro<br />
** {{done|}} set up python script on a 24-hour cron job<br />
* {{done|}} prototype a series of long-term charts to track:<br />
** {{done|}} WebGL success rate - rpi3/#psd-webgl<br />
** {{done|}} WebGL crash rate - rpi3/#psd-webgl-rate<br />
** {{done|}} Shutdown crashes - rpi3/#psd-shutdown<br />
** {{done|}} Startup crashes - rpi3/#psd-startup<br />
** {{done|}} Driver crashes - rpi3/#psd-driver-rate<br />
** {{prev|}} High-volume crashes<br />
** {{done|}} Overall Graphics crash rate - rpi3/#psd-gfx-rate<br />
* {{done|}} prototype a dashboard to display all long-term graphs - See <server>/index.htm#psd-dashboard<br />
* {{done|}} [add'l] Move infrastructure to a Mac Mini behind VPN<br />
* {{prev|}} host the dashboard on metrics.mozilla.com/gfx (if possible)<br />
<br />
|-<br />
| '''2. Prototype a small-scale, automated emunittest lab to improve discoverability of WebGL regressions in Nightly'''<br />
* {{done|}} set up a machine to be used for testing on a daily basis<br />
* {{done|}} get a script from Jukka Jylänki's to automate publishing test results to his local server in Finland<br />
* {{done|}} test the script on a dummy rig at my desk in Vancouver<br />
* {{done|}} let the machine run for several days to capture long-term results - See [http://clbri.com:6932/results?uuid=9f09167b-a166-4402-a20d-7536574b5d06 clbri.com]<br />
* {{prev|}} optionally, get Jukka to create a mobile version of his test site that we can point to WebQA's Saucelabs instance<br />
<br />
|-<br />
| '''3. Utilize the Graphics test plan framework to validate shipping SKIA Content on Windows to Aurora in Firefox 52'''<br />
* document the test plan framework and telemetry experiment lessons learned<br />
* work with Mason to document milestones and release criteria<br />
* ensure these criteria are measured and met along the way<br />
|-<br />
| '''4. Maintenance tasks to ensure GFX quality does not slip<br />
* Daily bug triage via http://ashughes1.github.io/graphicstriage/<br />
* Find a new home for One & Done tasks (testrail?)<br />
* Execute testing via Betabreakers for new features in Aurora<br />
|}<br />
<br />
==== GPU Process ====<br />
* Develop a test plan to qualify MVP<br />
* Deploy a Telemetry Experiment in Nightly to A/B test stability (blocked by {{bug|1323304}})<br />
<br />
=== 2016 Q3 ===<br />
; Tasks <br />
* ...<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-07-01",<br />
"chfieldto":"2016-09-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q2 ===<br />
; Tasks<br />
* Prototyped a crash-stats dashboard with auto-updating charts<br />
* Conducted a talk at London all-hands ([https://docs.google.com/presentation/d/17CFTU_WWu0tWd_kHfSghaMbtsgPrcvavEytcat4O5MI/edit#slide=id.g14538819fd_2_263 presentation])<br />
* Conducted Animometer benchmarking ([https://drive.google.com/open?id=1xo6Yfds1YFn8FAtFdQeb5R_JKMWej-g9cVZWgfK8Rso Mac OS], [https://drive.google.com/open?id=1vCkgNv_EGncd-naj_89s-2Ep9iL7I2tuzTYYhAOV0WA Windows 7])<br />
* Created an add-on to integrate crash-stats visualization with Bugzilla ([https://addons.mozilla.org/en-US/firefox/addon/bugzilla-socorro-lens/ v0.1])<br />
* Executed Firefox 46 testing to support {{bug|1255281}} ([[QA/Platform/Graphics/Betabreakers/Firefox_46|testplan]])<br />
* Executed Firefox 48 testing to support {{bug|1260507}} ([[QA/Platform/Graphics/Betabreakers/Firefox_48|testplan]])<br />
* Set up weekly triage of Top Crashes, Cold Crashes, Cold Trackers, Untriaged, and Help Wanted bugs with a dashboard to track progress<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-04-01",<br />
"chfieldto":"2016-06-30",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2016 Q1 ===<br />
* Filed a bug to enable special character searches on Socorro ({{bug|1239402}})<br />
* Prototyped a dashboard of Socorro data<br />
* Prototyped a dashboard of Bugzilla data<br />
* Executed a testrun to vet Developer Edition 45 for WinXP + D3D9 + E10S re bug 1237769<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2016-01-01",<br />
"chfieldto":"2016-03-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
== 2015 ==<br />
=== 2015 Q4 ===<br />
* Drafted documentation on graphics device/driver blocklisting ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Graphics_Blocklisting]''<br />
* Executed testruns to sanity check [[QA/Platform/Graphics/Firefox_43|Firefox 43]] and [[QA/Platform/Graphics/Firefox_44|Firefox 44]] in Aurora<br />
* Organized Android sanity [[QA/Platform/Graphics/Android|testing]] for SKIA update (due Dec 7, 2015)<br />
* Proposed inclusion of GPU chipset information in Socorro, tracked via {{bug|1192351}}<br />
* Prototyped a graphics quality [https://metrics.mozilla.com/gfx/ dashboard]<br />
* Prototyped a periodic triage workflow to close old bugs and escalate lost issues<br />
* Prototyped a [http://ashughes1.github.io/testday-metrics/charts/index.htm dashboard] to measure engagement during testdays<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"emailreporter1":"1",<br />
"emaillongdesc1":"1",<br />
"emailtype1":"exact",<br />
"email1":"anthony.s.hughes@gmail.com",<br />
"chfield":"[Bug creation]",<br />
"chfieldfrom":"2015-10-01",<br />
"chfieldto":"2015-12-31",<br />
"include_fields":"id,summary,status"<br />
}<br />
</bugzilla><br />
<br />
=== 2015 Q3 ===<br />
* Developed a process to create a mission statement of and for the community ([[QA/Future|result]])<br />
* Conducted one-to-one meetings with peers and collect feedback to inform the mission statement<br />
* Drafted a recommendation for Hossain Al Ikram to participate in 2015 Global Gatherings<br />
* Provided advice to Jamie Charlton about planning Firefox OS testing events<br />
* Dogfooded Windows 10 to report blocker bugs ahead of release<br />
* Created a process for [http://bit.ly/1JZqzMc daily sanity checks] via the lab in Toronto<br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_41|Firefox Aurora 41]] <br />
* Executed outsourced sanity checking for [[QA/Platform/Graphics/Firefox_42|Firefox Aurora 42]]<br />
* Extended the sanity checking to volunteers via One & Done ([https://docs.google.com/a/mozilla.com/forms/d/1AoaAU6__rebVxOwjb8ZOM_fgZkdqk-DK1hITr5QDzFo/edit# results form])<br />
* Documented best practices on MDN ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_Graphics_Team artifact])<br />
* Developed a catalog of graphics hardware to facilitate device-specific testing ([[QA/Platform/Graphics/Inventory|artifact]])<br />
* Created an [https://docs.google.com/spreadsheets/d/12jNc8rlZP4MDk5xOHyOWlcO2W5J39KKofzvcVZxVFJk/edit#gid=0 internal hardware catalog] as a proof-of-concept<br />
* Migrated the internal catalog to a <br />
* Improved readability of the inventory based on peer review<br />
<br />
; Bugs<br />
<bugzilla display="list"><br />
{<br />
"id":"1112371,1130195,1145143,1173579,1176147,1180561,1187464,1187466,1189266,1189940,1191060,1194933,1198765,1201679,1201960,1202696,1202700,1202748,1202786,1204337,1206626,1207326,1208579,1209617"<br />
}<br />
</bugzilla></div>Ashughes