testing as part of the team culture: actions taken and lessons learned

33
Claudia Badell [email protected] @claubs_uy TESTING AS PART OF THE TEAM CULTURE Actions Taken and Lessons Learned

Upload: claudia-badell

Post on 12-Apr-2017

141 views

Category:

Technology


2 download

TRANSCRIPT

Page 1: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

Claudia Badell [email protected]

@claubs_uy

TESTING AS PART OF THE TEAM CULTURE Actions Taken and Lessons Learned

Page 2: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

WORK EXPERIENCE • Senior Quality Engineer, Indigo Studio Team,

Infragistics, 2009 • TestingUy (www.testing.uy)

ABOUT ME

STUDIES • Computer Engineer • Scrum Master • Association for Software Testing courses

(Foundations & Bug Advocacy) • ISTQB Foundation • …

PAST WORK EXPERIENCE • Test Manager, Tester, Business Analyst • Teacher for Computing Science Department

within the School of Engineering at Universidad de la República

Page 3: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

INTRODUCTION 1

WHAT WE DID 2

3

AGENDA

CONCLUSIONS 4

WHAT WE HAVE LEARNED AS A TEAM

Page 4: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

AGENDA

INTRODUCTION 1

WHAT WE DID 2

3

CONCLUSIONS 4

WHAT WE HAVE LEARNED AS A TEAM

Page 5: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• UI-prototyping tool mainly for interaction designers and visual designers

THE PRODUCT BEING TESTED

Page 6: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• In the market since 2012

• Eight major releases, several intermediate updates and silent updates

THE PRODUCT BEING TESTED

Page 7: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• Developers (7) • Visual designers (1) • Interaction designers (1) • Technical writer (1) • Testers (1)

THE TEAM

Page 8: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• Mostly performed by all of us

TESTING IN THE TEAM

• UX is an important aspect to consider when testing

• Tester as evangelist

• Testing strategies are defined and applied together

• Mid and long-term testing strategies

• Big domain with many scenarios to cover

Page 9: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

AGENDA

INTRODUCTION 1

WHAT WE DID 2

WHAT WE HAVE LEARNED 3

CONCLUSIONS 4

Page 10: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

THINGS THAT WE DID

• Internal trainings

• Kick-off testing meetings

• Follow-up testing meetings

• Early Testing

Page 11: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

TEAM TESTING STRATEGIES

Page 12: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

Mind maps to support exploratory testing

TEAM TESTING STRATEGIES AN EXAMPLE

Page 13: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

WHAT IS MIND MAPPING?

Page 14: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• Organize ideas

• Visualize ideas

• Identify dependencies

• Discuss ideas

• Share knowledge

MIND MAPS HELP US TO

Page 15: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• We created a repository to store the mind maps

• We defined file naming conventions

• We design a mind map for each module being tested

MIND MAPS TO SUPPORT EXPLORATORY TESTING

Page 16: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

Mind maps include the testing variables to cover

Page 17: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

What is a testing variable?

Page 18: Testing as Part of the Team Culture: Actions Taken and Lessons Learned
Page 19: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

There is more than one way to model a feature

Page 20: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• We defined guidelines and structure conventions to take into consideration while elaborating a mind map

MIND MAPS TO SUPPORT EXPLORATORY TESTING

Page 21: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

Mind maps hands-on: Concepts Revision

Mind maps hands-on: Exercise 2

Mind maps hands-on: Exercise 1

INTERNAL WORKSHOPS TO EVANGELIZE THE APPROACH IN THE TEAM

Page 22: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

How do we use mind maps for a new release?

Page 23: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• Structure information

• Have the big picture of what we are modeling

• Share knowledge

• Have a common understanding of the features

MIND MAPS HELP US TO

Page 24: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• Generate and share test ideas with others

• Iterate over existing ideas

• Identify better test conditions

MIND MAPS HELP US TO

Page 25: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

AGENDA

INTRODUCTION 1

WHAT WE DID 2

WHAT WE HAVE LEARNED AS A TEAM 3

CONCLUSIONS 4

Page 26: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• All team members improved their knowledge of the features beyond their specific activities.

• We’ve learned to be flexible enough to adapt and wear other hats depending on the needs of the product and the team.

• We incorporated testing terminology as part of our team culture.

• We adopted and unified the domain terminology of the software being tested.

FROM THE TESTING PERSPECTIVE

Page 27: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• As everyone in the team tests and reports bugs, the bug tracker workflow has been improved.

• We improved the triage for bugs.

• We gained a deeper understanding of the testing effort required for a release and the impact that a fix has from this perspective.

FROM THE TESTING PERSPECTIVE

Page 28: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

Take ownership of your process

• Feature-oriented processes instead of sprint-oriented ones.

• Weekly meetings, instead of daily stand-up meetings.

• Frequency of Retrospectives.

• New meetings: design and technical.

BEYOND TESTING

Page 29: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

AGENDA

INTRODUCTION 1

WHAT WE DID 2

3

CONCLUSIONS 4

WHAT WE HAVE LEARNED AS A TEAM

Page 30: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

• The role of the tester in the team has become that of a facilitator.

• Importance of defining mid and long-term testing strategies when the product under test has a long lifecycle.

• Testing is a team responsibility.

CONCLUSIONS

Page 31: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

Promote activities to share knowledge across disciplines

Page 32: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

KEEP CALM AND

ENHANCE YOUR TEAM TESTING CULTURE

Page 33: Testing as Part of the Team Culture: Actions Taken and Lessons Learned

THANKS

Questions?

CONTACT:

Claudia Badell [email protected]

@claubs_uy