Roman Zakharov: Robot Framework: A Perfect Tool to Get Rid Of
summary
Company moves its end-to-end tests from Robot Framework to pytest to gain native Python fixtures, easier debugging and access to Python libraries; transition takes about several months and preserves Robot keywords while rewriting test classes. Engineers build a C++ gameplay test tool and a custom backdoor into Unity to route audio and UI elements, run automation on 12 devices in soundproof boxes, cut playback latency compared to ad-hoc taps, and adopt Allure for richer reports.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:28Audio app testing challenges
- 3:15Audio testing setup
- 5:22Unity automation limits
- 7:31Demo: gameplay audio test tool
- 10:47Robot Framework advantages
- 13:35Robot Framework community
- 14:41Robot Framework limitations
- 17:51Robot Framework best practices
- 20:00Quiz: Robot Framework features
- 21:28iOS automation complexities
- 23:36Switching from Robot to pytest
- 25:27Robot vs pytest learning curve
- 26:53Transitioning to pytest
- 27:55Maintaining tests during switch
- 30:24Timing accuracy in audio tests
- 31:43AI tools in transition
- 32:50Key learnings from switch
- 33:32Summary
related talks
17mRobot Framework - Smarter Way to Automate Test
31mPytest vs Robot, A battle or Co existence
37mAutomated End-to-End Tests with Robot Framework
17mHUSTEF 2014 - Tamás Pályi
38mAutomation anywhere by customising Robot Framework
05mChallenges of building a test infrastructure around a cross-platform Desktop
23mRobot Framework: Semicolon-free testing
44mLevel Up Your Embedded Testing Game