Making SDETs from ppl with 0 programming experience
summary
Describes Preply’s experiments turning non-programmers into SDETs by implementing practical automation solutions and workflows; discusses results, challenges and lessons learned, and shows ways QA engineers can collaborate with developers to raise product quality (including processes that keep quality improving even when individuals are unavailable). No specific programming languages or tools are named in the abstract.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:00Which problems solved
- 4:27Evolution process, how and why it changed
- 6:49Microsoft example
- 9:49Google example
- 12:04Testing in Preply
- 18:03Solutions we found
- 20:02SDET activities comparing to AQA
- 26:32Key learnings
- 33:22Educational process
related talks
50mBOF: SDET – yet another rattle title or separate engineering line
49mSDET: The Next Level in Test Automation
43mFrom Clickers to Coders: The SDET Evolution Story
13mHow to Become an SDET from Automation QA | Role of an SDET
38mThe New Skill Stack for SDETs in the Agentic Era
30mLessons Learned: A Developer's Perspective on Teaching & Learning
11mDeveloper Productivity Engineering
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development