fosdem 2016 - community driven testing

14
Community Driven Testing: Lessons learned from the BuddyUp Pilot project Marcia Knous and Ioana Chiorean

Upload: ioana-chiorean

Post on 15-Apr-2017

262 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Fosdem 2016 - Community Driven Testing

Community Driven Testing: Lessons learned from the BuddyUp Pilot project

Marcia Knous and Ioana Chiorean

Page 2: Fosdem 2016 - Community Driven Testing

What is BuddyUp?

● Single support entry point for users - integrates support offered on hardware, software or service issues

● Web app that enables on-device notifications for an instant answer to any question you have

A Firefox OS support app

Page 3: Fosdem 2016 - Community Driven Testing

What is BuddyUp?A Firefox OS support app

Page 4: Fosdem 2016 - Community Driven Testing

Why BuddyUp?

● An opportunity to try something new!

● No dedicated QA resources available for the project

● App was planned to ship by default on the Firefox OS 2.5 release

The Mozilla mission in action: human collaboration across an open platform

Page 5: Fosdem 2016 - Community Driven Testing

Pilot Project Objectives

● Teach contributors skills that would span the mobile testing landscape

● Give contributors a sense of what is like to be part of a QA testing team

● Make it easy for any FxOS user interested to help to become and feel part of a larger community of helpers

● Develop community mentors

Page 6: Fosdem 2016 - Community Driven Testing

Who participated?

● Two mentors - Marcia Knous and Ioana Chiorean

● Three community members○ Christos○ Fredy○ Karthikeyan

● First team meeting held in Mozilla Paris space in February, 2015 (Developers, Project Management, UX)

Ioana, Karth and Fredy discussing the project

Page 7: Fosdem 2016 - Community Driven Testing

Meetup attendes

Page 8: Fosdem 2016 - Community Driven Testing

How we structured testing

● App divided into three parts○ Testing as someone asking a question○ Testing as someone answering a question○ Profile and Settings

● Owners created a short test plan and test cases for each area

Page 9: Fosdem 2016 - Community Driven Testing

How we structured testing

● Periodic smoketests run to catch regressions● Community dialed into project meetings and reported status

Page 10: Fosdem 2016 - Community Driven Testing

How did they benefit?

● Gained knowledge in mobile testing, which can help them get a job

● Gained knowledge of how to approach testing an app from a project perspective

● Worked equally with the staff, as an important member of the team - they attended team meetings, sent reports, smoketested

Page 11: Fosdem 2016 - Community Driven Testing

How did they benefit?

Page 12: Fosdem 2016 - Community Driven Testing

Challenges and Lessons

● Time zone challenges

● Time based requests are difficult

● Lead Developer left for some time, and the project lost momentum

● Resource balancing

● No automation infrastructure meant lots of repetitive manual testing

Page 13: Fosdem 2016 - Community Driven Testing

Going further

● Created two tiger teams for Firefox OS features (Pin the Web/Control Center)

● Provided better documentation that can be applied to other projects as well

● Realized that in-person training is way more efficient than online meetings so we will try to duplicate this

How BuddyUp experience can help us more

Page 14: Fosdem 2016 - Community Driven Testing

Questions?