Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Meetup TestingUY 2016: Adopting testing in a cross-functional team

373 views

Published on

Meetup TestingUy | Uruguay, Montevideo | 13th December 2016

Abstract
In this talk Claudia will tell us some of the actions that have been applied to incorporate testing as a team strategy, in the context of a cross-functional team fully dedicated to developing a product. Claudia will also share some lessons learned during this process.

Duration: 45 minutes

Published in: Technology
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1lite.top/aaWH4 ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Meetup TestingUY 2016: Adopting testing in a cross-functional team

  1. 1. INCORPORANDO EL TESTING
  2. 2. WORK EXPERIENCE • Senior Quality Engineer, Indigo Studio Team, Infragistics, 2009 • TestingUy (www.testing.uy) ABOUT ME  STUDIES • Computer Engineer • Association for Software Testing courses (Foundations & Bug Advocacy) • Scrum Master • ISTQB Foundation PAST WORK EXPERIENCE • Test Manager, Tester and Business Analyst • Teacher for Computing Science Department within the School of Engineering at Universidad de la República
  3. 3. INTRODUCTION1 WHAT WE DID2 CONCLUSIONS3 AGENDA
  4. 4. AGENDA INTRODUCTION1 WHAT WE DID2 CONCLUSIONS3
  5. 5. Why do we test?
  6. 6. Testing is always a search for information BBST: Foundations course by the Association for Software Testing
  7. 7. Identifying what to test
  8. 8. • supported by test cases design techniques • test design and test execution activities are separated in time • each activity can be performed by different people SCRIPTED TESTING • test design and test execution activities are performed simultaneously EXPLORATORY TESTING
  9. 9. Heuristics provide ideas to test
  10. 10. TESTING HEURISTICS CEM KANER Consistent with: • the product • history • comparable products • our image • regulations • purpose http://testingeducation.org/BBST/foundations/
  11. 11. JAKOB NIELSEN 1. Visibility of system status 2. Match between system and the real world 3. User control and freedom 4. Consistency and standards 5. Error prevention 6. Recognition rather than recall 7. Flexibility and efficiency of use 8. Aesthetic and minimalist design 9. Help users recognize, diagnose, and recover from errors 10.Help and documentation www.useit.com/papers/heuristic/heuristic_list.html USABILITY HEURISTICS
  12. 12. At what level?
  13. 13. • Test cases design techniques • Exploratory testing • Heuristics • Bug history • Business domain • Behavior, visual design & interaction design for similar features • The source code of the feature • … HOW DO WE IDENTIFY THE SCENARIOS TO COVER?
  14. 14. TIME RISK FROM THE BUSINESS PERSPECTIVE PRIORITY RISK FROM THE IMPLEMENTATION PERSPECTIVE FEATURE COMPLEXITY CONSIDERING
  15. 15. How do we share a common understanding of previous concepts in a cross-functional team?
  16. 16. And also, how do we apply them?
  17. 17. AGENDA INTRODUCTION1 WHAT WE DID2 CONCLUSIONS3
  18. 18. THE PRODUCT
  19. 19. • In the market since 2012 • Eight major releases, several intermediate updates and silent updates THE PRODUCT
  20. 20. • Developers (7) • Visual designers (1) • Interaction designers (1) • Technical writer (1) • Testers (1) THE TEAM
  21. 21. • 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 • Testing strategies for the mid/long term • Big domain with many scenarios to cover
  22. 22. THINGS THAT WE DID • Internal trainings • Kick-off testing meetings • Follow-up testing meetings • Early Testing
  23. 23. • Testing variables checklists • Testbeds • Mind maps to guide exploratory testing TEAM TESTING STRATEGIES
  24. 24. • 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 according to 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 under test. WHAT WE’VE LEARNED AS A TEAM
  25. 25. • As all the team tests and reports bugs, the bug tracker workflow has been improved. • We improved bugs’ triage. • We gained understanding of the required testing effort for a release and the impact that a fix has from this perspective. WHAT WE’VE LEARNED AS A TEAM
  26. 26. • Allocate time and resources. Otherwise, it's just wishful thinking. • Automation is not an individual effort, it is a team effort. WHAT WE’VE LEARNED AS A TEAM
  27. 27. Automated testing complements manual testing, but it does not substitute it.
  28. 28. AGENDA INTRODUCTION1 WHAT WE DID2 CONCLUSIONS3
  29. 29. • The role of the tester in the team has become that of a facilitator. • Importance of defining testing strategies for the mid/long term when the product under test has a long life. • Testing is a team responsibility. CONCLUSIONS
  30. 30. THANKS Questions? CONTACT: Claudia Badell cbadell@infragistics.com @claubs_uy

×