Episode 24: QA, Automation, and everything in between

Techpoint Charlie

Content provided by Raz, Yael, Noa and Alaa. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Raz, Yael, Noa and Alaa or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

5+ y ago 49:53

MP3•Episode home

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on October 30, 2025 15:28 (1M ago)

What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

Noa Tamir and Alaa Sarhan speak with Rony Lahav about the role of QA and Automation, Why do we need QA people (or why developers shouldn’t be the only testers), Different Test - Component, Integration, System, E2E, Is Manual QA dead?
We also touched on:

Automation is a software project
when should testing/QA stop? / what kind of bugs/edges cases are fine to be ignored or not covered?
QA vs. Product Acceptance. How much do they conflict, and do they complement each other?
what areas QA covers on top of "functional": performance, accessibility, usability, fault tolerance/recoverability, etc.
In presence of QA team/role, what should Software Engineers test?
Tracking data quality: tracking QA, and Functional QA (OSS tool from King https://github.com/king/tratt-api)
Phases of QA: development, build, release, on-call
What QA and TE gets that devs, PMs, and DS don’t get and what do we get when there are better collaboration and comms
Team testing

Music credits: Dan Lebowitz: Come and Get It! Licensed under Creative Commons: By Attribution 3.0 License

28 episodes

#Tech #Engineering #Design #Culture #Techpoint #Charlie #Raz, Yael, Noa and Alaa #Careers #Business #Productivity #Data Science #User Experience