Session
- Track: Standardization Decisions
- Topic: Standardizing QA best practices
Description
This session will be a short presentation of how QA processes are currently integrated into development workflows, and then, an open discussion.
- What makes software good - and why QA support is important
- Three practical concepts of a good software (understanding the problem, simple and intuitive design, seeing users' perspective)
- Context-specific testing approach
- Hands-on exploratory testing exercise (Special:RecentChanges page )
- Evaluate what should be tested
- Outline how the features may be tested
- Current practices
- what are QA processes?
- a team workflow support
- a daily track of QA work
- what are QA processes?
- how QA processes are integrated in development cycle (and why)
- Planning/Design
- Implementation
- Deployment
- Maintenance
Questions to answer and discuss
Question: How can we ensure QA processes are consistently and effectively integrated into development workflows?
Question: What are our current best practices?
Related Issues
- What is missing in team processes regarding QA support?
- Get feedback on the questions of what should've been discussed but wasn't.
Pre-reading for all Participants
- None
Notes document(s)
Slides: Exploratory testing
https://etherpad.wikimedia.org/p/WMTC19-T234653
Notes and Facilitation guidance
https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/NotesandFacilitation
Session Leader(s)
- Elena Tonkovidova (@Etonkovidova)
Session Scribes
- Brennen
Session Facilitator
- Aubrey
Session Style / Format
- Presentation/demo of QA practices and hands-on exercise
Session Leaders please:
- Add more details to this task description.
- Coordinate any pre-event discussions (here on Phab, IRC, email, hangout, etc).
- Outline the plan for discussing this topic at the event.
- Optionally, include what this session will not try to solve.
- Update this task with summaries of any pre-event discussions.
- Include ways for people not attending to be involved in discussions before the event and afterwards.
Post-event summary:
- Shared understanding on key issues related to current QA practices
- Should UI automation testing be part of exploratory testing?
Post-event action items:
- Continue discussion of QA practices in a broader context of Engineering productivity team
- Start a discussion of a specialized types of testing - e.g. Accessibility - how to make it a part of QA testing?
- Document what instrumentation/tools/skills/practices are critical for efficient exploratory testing