Software Developer in Test: Who Is That?
summary
Defines a Software Developer in Test as a developer-for-tests who writes production-quality test code, owns the test pyramid, and pairs with application developers to maintain lower-level coverage. Demonstrates a small app with unit, integration and a single UI test using Selenium, Mockito and WireMock to isolate services, argues that misuse of end-to-end suites makes ~40% of tests obsolete, and recommends paired programming and double code review while organizing mixed test suites to make the approach work.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:06Testing career in outsourcing
- 2:10Traditional QA model
- 3:35Manual testing problems
- 4:37First Selenium tests
- 5:40Why abandon Selenium
- 6:47Positive automation changes
- 8:16Black-box to white-box
- 9:19Test pyramid principles
- 11:07Pairing with developers
- 12:31Test and code ownership
- 14:20Branching issues
- 15:46App architecture
- 19:08Demo: test layers
- 23:56TDD vs ATDD
- 26:30Who is SDET
- 28:19SDET vs QA Automation
- 29:42SDET candidate profile
- 31:08SDET in product company
- 32:03Q&A
- 35:52Q&A
- 37:44Q&A
- 38:47Q&A
- 39:08Q&A
- 41:40Summary
related talks
36mTesting: Where the Developer's Work Ends and the Tester's Begins
46mSoftware Devs in Test Automation - Dream or Reality in Agile Software Dev?
44mTest Automation as a Development Team
42mEffective Developer Testing: taking it to the next level
42mUse testing to Develop Better Software Faster
23mWhy testing is also a developer's problem
53mTest automation for developers
07mTest Camp