{"id":270,"date":"2014-09-24T16:44:03","date_gmt":"2014-09-24T16:44:03","guid":{"rendered":"http:\/\/blog.mozilla.org\/webqa\/?p=270"},"modified":"2014-09-24T16:44:03","modified_gmt":"2014-09-24T16:44:03","slug":"web-qa-team-and-project-changes-and-renewed-communitycollaboration-opportunities","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/fxtesteng\/2014\/09\/24\/web-qa-team-and-project-changes-and-renewed-communitycollaboration-opportunities\/","title":{"rendered":"Web QA team and project changes; and renewed community\/collaboration opportunities"},"content":{"rendered":"<p><strong>Fall Brings With It Some Changes<\/strong><\/p>\n<p>As <a href=\"https:\/\/mozillians.org\/en-US\/u\/ctalbert\/\">Clint<\/a>, our Director of Quality, wrote in his Getting Ready for Fall <a href=\"http:\/\/clinttalbert.com\/2014\/09\/16\/getting_ready_for_fall\/\">blogpost<\/a>, there are some process and project-coverage\/testing-approach changes underway to the <em>ways<\/em> the individual QA teams (and as a whole) work, and, also, <em>what<\/em> we work on; more on some of the Web QA-specific changes follow, below.<\/p>\n<p>Along with some of those changes, our <a href=\"https:\/\/quality.mozilla.org\/teams\/web-qa\/\">Web QA team<\/a> has undergone a few key personnel changes in the past few weeks, which I really intended to acknowledge and highlight much sooner than I am, now:<\/p>\n<ul>\n<li><a href=\"https:\/\/mozillians.org\/en-US\/u\/zac\/\">Zac<\/a> is now working on the Firefox OS QA Automation team<\/li>\n<li>Raymond is now pursuing other opportunities outside of Mozilla<\/li>\n<li>From our <a href=\"https:\/\/wiki.mozilla.org\/QA_SoftVision_Team#Test_Automation_Team\">Softvision side<\/a>, <a href=\"https:\/\/mozillians.org\/en-US\/u\/Bebe\/\">Florin<\/a>, Viorela, and Robert are now also working with Zac on the Firefox OS QA Automation team<\/li>\n<\/ul>\n<p><strong>Gratitude is in Order<\/strong><\/p>\n<p>It goes without saying, but bears repeating, loudly, that we wish everyone well, and will of course miss them all!\u00a0 Undoubtedly, we couldn&#8217;t have matured and grown our processes, collaboration, community, and project coverage &#8212; especially through automation, without each and every one of their efforts!<\/p>\n<p>Thankfully, as is the case with nearly all Mozillians, as the saying goes, &#8220;Once a Mozillians, always a Mozillian,&#8221; so we&#8217;ll surely see everyone around \ud83d\ude42<\/p>\n<p><strong>So, What&#8217;s Next for Us?<\/strong><\/p>\n<p>We&#8217;ve always been a team that&#8217;s looking to improve our processes, streamline our efforts, work more closely with our friendly <a href=\"https:\/\/wiki.mozilla.org\/Webdev\">Web developers<\/a> (<a href=\"https:\/\/blog.mozilla.org\/webdev\/\">webdev blog<\/a>) and <a href=\"https:\/\/wiki.mozilla.org\/Webdev\/Web_Production\">project\/product managers<\/a>, to help provide coverage where and when it&#8217;s needed, as long as we&#8217;re able, and, more importantly, help grow &#8212; and learn from &#8212; a vibrant testing community!<\/p>\n<p>As I mentioned in the beginning of this post, we&#8217;re looking to make some changes to both our processes and to some of our projects.\u00a0 A few key highlights of those efforts include:<\/p>\n<ul>\n<li>especially in our test automation, working with our developers to better scale and integrate testing, by prototyping and vetting JavaScript-integration tests against real browsers +real servers, run in a publicly-visible Continuous Integration environment (a la Travis and Jenkins, perhaps others)<\/li>\n<li>&#8230;and scaling\/paring down our <a href=\"https:\/\/quality.mozilla.org\/docs\/webqa\/running-webqa-automated-tests\/\">Python tests<\/a> where we find redundancies or inefficiencies, yet retaining key tests where our current stack gives us the most-complete or &#8220;best&#8221; coverage<\/li>\n<li>through our manual, exploratory testing + iterating on new methods for exposing and mitigating risk<\/li>\n<li>helping to refine and understand task metrics on <a href=\"https:\/\/oneanddone.mozilla.org\">One and Done<\/a>, so we can make more-effective tasks and user-flows<\/li>\n<li>working to expose, via collated metrics dashboards, key indicators of project health and quality, across QA, and inviting others at Mozilla to help us continue to make them ever-more meaningful<\/li>\n<\/ul>\n<p><strong>How You Can Get Involved<\/strong><\/p>\n<p>If any of the above interests you, or you&#8217;d like to learn more about what our team does, and be a part of that, we&#8217;d love to hear from you, and encourage you to:<\/p>\n<ul>\n<li>start with our <a href=\"https:\/\/quality.mozilla.org\/teams\/web-qa\/\">Quality.Mozilla.Org team page<\/a><\/li>\n<li>dive in with our <a href=\"https:\/\/oneanddone.mozilla.org\/en-US\/tasks\/available\/?team=6\">One and Done<\/a> tasks<\/li>\n<li><a href=\"https:\/\/wiki.mozilla.org\/QA\/Execution\/Web_Testing#Contact_Us\">reach out to<\/a> us via: <a href=\"irc:\/\/irc.mozilla.org\/#mozwebqa\">#mozwebqa on IRC<\/a> (<a href=\"http:\/\/widget.mibbit.com\/?settings=0a187437b06ca9bcb0cff2a717e985c5&amp;server=irc.mozilla.org&amp;channel=mozwebqa&amp;noServerTab=false&amp;autoConnect=true\">Mibbit link<\/a>), our <a href=\"mailto:mozwebqa@mozilla.org\">mozwebqa@mozilla.org<\/a> mailing list, and\/or our regular, Thursday-morning 9am PDT <a href=\"https:\/\/wiki.mozilla.org\/QA\/Execution\/Web_Testing#Meetings\">team meetings<\/a><\/li>\n<\/ul>\n<p>Thanks in advance &#8212; we&#8217;re looking forward to seeing and working with all of you!<\/p>\n<p><a href=\"https:\/\/mozillians.org\/en-US\/u\/stephend\/\">Stephen<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Fall Brings With It Some Changes As Clint, our Director of Quality, wrote in his Getting Ready for Fall blogpost, there are some process and project-coverage\/testing-approach changes underway to the &hellip; <a class=\"go\" href=\"https:\/\/blog.mozilla.org\/fxtesteng\/2014\/09\/24\/web-qa-team-and-project-changes-and-renewed-communitycollaboration-opportunities\/\">Read more<\/a><\/p>\n","protected":false},"author":512,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[53,614],"tags":[25209],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/posts\/270"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/users\/512"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/comments?post=270"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/posts\/270\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/media?parent=270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/categories?post=270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/fxtesteng\/wp-json\/wp\/v2\/tags?post=270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}