governance/archived/2021-02-22/wg-qa

QA Working Group

Oversees stability, quality, and testing criteria within Electron.

Membership

Avatar	Name	Role	Time Zone
	Marcel Munro @SlackedMarcel	Chair	PT (San Francisco)
	Maria Beliaeva @MariaBeliaeva	Member	PT (San Francisco)
	Keeley Hammond @VerteDinde	Member	PT (Portland)
	David Cruz @cruzerld	Member	ET (New York City)
	Sofia Nguy @sofianguy	Member	PT (San Francisco)
	Andrea Crawford @andreacrawford	Member	PT (Spokane)
	Katia Moklokova @katiamoklokova	Member	PT (San Francisco)

Parent Group

• Releases WG

Current Objective and Key Results

Objective 1:

Major version issues between new Electron versions and current apps are detected before releasing a new major version.

Key Results:

• At least one app to integrate Sentinal
• Audit current automated API tests and document results

Objective 2:

Electron has the best QA documentation of any platform

Key Results:

• Document each app's QA structure and process
• Publish on electronjs.org a list of tooling needs for accurate and fast Electron application testing

Areas of Responsibility

• Strongly advises the stable release.
• Long-term would oversee test automation and greenlight the stable release.

Meeting Schedule

• Sync Meeting Every 4 weeks, Wed 9:30am-PST

Meeting notes may be viewed in meeting-notes.

Joining the QA Working Group

In order to become a formal member of the QA Working Group, a prospective member must:

1. Be actively contributing to the work of the WG
2. Contribute to accomplishing OKRs and initiatives
3. Attend monthly QA WG meeting
4. Request entry into QA Working Group by asking the current Chair
5. Be approved by 2/3rds majority of current WG members (rounded up)
   1. The prospective member shall leave the meeting during the deliberation and vote.
   2. The meeting notes shall contain only the outcome of the vote (approved/not approved), not the individual votes.
   3. Members not able to attend the meeting at which the vote occurs may submit their vote to the Chair prior to the meeting.

If you are interested in joining the QA Working Group, reach out to an existing member and ask to be invited to the monthly meeting and as a guest to the #wg-qa channel in Slack.

Actively Contributing

"Actively contributing" does not necessarily mean writing code. It does mean that you are in regular communication with the QA Working Group (including attending monthly sync meetings), and it does mean that you are participating in QA Working Group discussions. If you are not sure whether the work you are doing counts as "materially contributing", reach out to a member and ask. 🙂