TestEngineering/Services/Contribute: Difference between revisions

m
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=== manual testing ===


* core contributor tasks:
== [[/Manual Testing|Manual Testing]] ==


    sync 2 prfiles on nightly
=== onboarding prerequisites ===


    sync between android and desktop
* Internet access, Nightly, email, maybe IRC.


    FxOS - find my device testing
=== casual ===


    verify legacy sync
* show up to a test day


* active contributor tasks
* do a task in One and Done


    one pull request (3x/qtr)
=== active ===


    one testing contribution per release
* member of services-qa and nightly-testers mailing lists


=== automated test writing ===
* documentation pull request or wiki updates (3x/qtr)


    onboarding: Nightly, Mercurial, Git, irc client, mozillians profile,
* one testing contribution per release (i.e. every six weeks)


    casual: one pull request(github) or one code contribution(hg) per quarter (which repos?)
=== core ===


    active: three times a quarter PR or code contributed
* sync 2 profiles on nightly


    core contributor tasks:
* sync between android and desktop


    write tests for major sync flows
* FxOS - find my device testing


    develop/run load tests
* verify legacy sync


=== evangelize Mozilla Services ===
== Automated Test Development ==


    onboarding: Mozilla shirt, Blogging account, IRC/email account
=== onboarding prerequisites ===
* Nightly, Mercurial, Git, IRC client, Mozillians profile.


    casual: blog post 1/qtr, retweet/link 2/qtr, attend event in Moz shirt 1/qtr
=== casual ===
* one pull request(github) or one code contribution(hg) per quarter (which repos?)


    active: write blog post empasizing open web and Services ecosystem 1/qtr, blog on planet 2/qtr, reblog/retweet 5/qtr, speak @ meetup 1/qtr
=== active ===
* three times a quarter PR or code contributed


    core: give talks on privacy/security 2/qtr, talk to allied communities about decentralized services.
=== core ===
 
* write tests for major sync flows
 
* develop/run load tests
 
* Cloud Services QA Automation core contributor, someone who regularly makes pull requests and comments on one or many of our GitHub project repos.
* Cloud Services QA Automation mentor, someone who comments on new contributor commits helping them learn the styleguide and encouraging them to participate.
 
 
== Evangelizing Mozilla Services ==
 
=== onboarding prerequisites ===
* Mozilla shirt, Blogging account, IRC/email account
 
=== casual ===
* blog post 1/qtr, retweet/link 2/qtr, attend event in Moz shirt 1/qtr
 
=== active ===
* write blog post emphasizing open web and Services ecosystem 1/qtr, blog on planet 2/qtr, reblog/retweet 5/qtr, speak @ meetup 1/qtr
 
=== core ===
* give talks on privacy/security 2/qtr, talk to allied communities about decentralized services.
* Cloud Services QA community builder, someone who rallies our community and actively works with new contributors.
 
== "Sorting hat" questions ==
* Questions for potential general QA contributors
* Motivation: new/refresh skills, open source/giving back, a particular product/project, etc.
  * Skills: automation/coding, testing
  * Giving Back: community work, diversity, training
  * Product: Firefox, Fennec, FxOS, WebQA, Cloud Services
 
* Sorting of potential Cloud Services QA contributors
* Python, JavaScript, both, neither, or other? PYTHON
  * Loads, mozilla-services repo.
* Python, javaScript, both, neither, or other? JS
  * Persona, FxA, etc.
* Python, javaScript, both, neither, or other? BOTH
  * Specific parts of Sync, etc.  Maybe A-Team?
* Python, JavaScript, both, neither, or other? OTHER
  * Want to learn JS or Python? YES
    + Various 101 classes.
  * Want to learn JS or Python? NO
    + Write us a proposal.
* Python, javaScript, both, neither, or other? NEITHER
  * Testing experience? NO
  * Volunteer/community leader experience? YES
    + QA Community Call, office hours, etc.
  * Volunteer/community leader experience? NO
    + QA 101 or general community pool, as appropriate.
  * Testing experience? YES
  * Using Nightly already? NO
    + Download (or build!) Nightly.
    + Skip to YES below.
  * Using Nightly already? YES
    + Drive it hard, find a bug.
    + List of Nightly bugs to be verified in Bugzilla.
    + Introduce to webQA or client teams.
81

edits