The "Do Nots" of Testing - Melissa Tondi

  • Locked
Melissa Tondi's profile
Melissa Tondi

Head of Technology Enablement

The "Do Nots" of Testing - Melissa Tondi image
A free account is required to view this content
Talk Description

Hear the five lessons learned in testing, address them, and take back valuable solutions on your journey of a modern tester! In the “Do Nots” of Testing, we explore five traditional approaches that we’ve introduced to QA over the years. Although these approaches have added value in the past, it’s time to revisit them and discuss new ways to show even more value and to support modern development approaches. These lessons learned in Software Testing – otherwise known as the “Do Nots” show how progress and innovation should always be at the forefront of any introduced process. Melissa will suggest different approaches and recommendations to help you either remove these pervasive activities completely from your existing Testing team or replace them with more meaningful and modern approaches.

Takeaways:

  • I'll present the top five “do nots” that testers have introduced in to the industry. 
  • We will discuss these items in detail 
    • why they were introduced 
    • some of the mis-perceptions they have propagated. 
  • We will then discuss what to replace those “do nots” with and how those suggestions allow for a more innovative approach to the industry.
What you’ll learn

By the end of this talk, you'll be able to:

  • TBA
Melissa Tondi's profile'

Melissa Tondi

Head of Technology Enablement

Melissa Tondi has spent most of her career working within software testing teams. She is a frequent speaker and writer at forums focusing on the Agile, QA/QE, and DevOps spaces and is in Enablement leadership at Campminder and a Principal Consultant at Disrupt Testing, where she assists companies to continuously improve the pursuit of quality software—from design to delivery and everything in between. In her software testing and quality engineering careers, Melissa has focused on building and organizing teams around three major tenets—efficiency, innovation, and culture – and uses the Greatest Common Denominator (GCD) approach for determining ways in which team members can assess, implement and report on day to day activities so the gap between need and value is as small as possible.
Suggested Content
A Really Useful List For Exploratory Testers
Testing an App That No-one Can See - BJ Aberle
Roadmap To Becoming A Test Automation Engineer
Why I Lost My Job As a Test Manager and What I Learnt As a Result
Why Attend A TestBash?
The Awesome Power Of Hosting Test.bash(); 2021
Reducing Waste In Scrum And Improving Team Efficiency
Getting Active! A Community Guide
The Art of Asking Questions – Karen Johnson
Explore MoT
Episode One: The Companion
A free monthly virtual software testing community gathering
MoT Foundation Certificate in Test Automation
Unlock the essential skills to transition into Test Automation through interactive, community-driven learning, backed by industry expertise

Tags

  • api-automation
  • automation
  • communication
  • continuous-learning
  • culture
  • developer-principles
  • developer-tools
  • exploratory-testing
  • influence
  • leadership
  • mental-health
  • roles
  • user-experience