Using Selenium in the Verification and Validation Process for Medical Device Software
summary
Automated verification for FDA-style medical device software produces a 100+ page V&V with change control and hundreds of iterations, where 25–30 automated V&V tests run in about 30 minutes and let builds be smoke-tested every commit. Tests must be UI-level, can’t rely on simulators because simulators have no BLE, and physical-device matrices forced carrying five iPhones; tool choices include Calabash (used) and Appium (preferred), and Swift 2→3 broke the entire suite until rewritten.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:34Lydias background
- 0:59Orthogonal Gait
- 1:27Medical Device Classes
- 2:39Verification and Validation
- 4:55Benefits of Automated VMV
- 6:12Writing Automated VMV
- 9:50Cucumber
- 14:37Frameworks
- 15:34Testing on Physical Devices
- 19:17Conclusion
related talks
29mUsing Selenium and Cucumber to test a healthcare information system
34mUsing Selenium to Improve a Team's Development Cycle
18m2024-Emerging-Wolf-Macielinski
24mAutomated Mobile E2E Testing
56mThe End Game
29mEnd to End Test Automation for Both Horizontal and Vertical Scale
55mShifting the Testing Role Pendulum
39mModel Based Testing Shifting Right into the Real World