Robot Framework Test Automation: Automate Web, Desktop, Mobile, and Embedded Systems
Categories: Podcasts , Test Guild
Robot Framework remains highly flexible because it relies on external libraries rather than built-in technologies, allowing users to automate complex systems like medical devices and embedded robotics. The community emphasizes collaboration and practical application, with AI tools assisting in test creation while human expertise ensures accuracy and debugging.
Test Guild
Test Guild - hosted by Joe Colantonio has main topic focus on Testing or Automating. Each episode has a different guest. Show notes have comprehensive links and usually a full transcript. Released as audio and video.
- https://testguild.com/
- https://testguild.com/podcasts/automation/
- https://www.youtube.com/playlist?list=PL9AgRtJkydU1jqvx46esyr56BXtm1QEds
- https://www.youtube.com/@JoeColantonio
Episode Details
- Show Notes: https://testtalks.libsyn.com/robot-framework-test-automation-automate-web-desktop-mobile-and-embedded-systems
- Published: 2026-11-17T16:05:00Z
- Duration: 36:16
- Author: Unknown
Overview
The episode examines why Robot Framework remains flexible across diverse domains - from medical device verification to Swagger documentation to low-code robotics - by exploring its architecture. As one contributor explains, “since 20 years, robot framework did not change in the fact that it’s in itself doesn’t do anything. Its power comes from the libraries and they are always evolving.” This design avoids becoming “a monolithic piece of test framework which would not be maintainable.”
Contributors share how the community formed through shared experiences: a style guide presentation led to a two-year working group, a failed lightning talk became a networking catalyst, and a first-time visitor’s sense of “wonderful sense of community” inspired her to lead Robocon’s first-ever program committee. The discussion also covers AI’s role, noting that Robot Framework’s keyword-based syntax makes it “a little more intuitive” for AI tools than syntax-heavy alternatives, while emphasizing that understanding test intent remains irreplaceable.
What If
-
What if you instrumented your test suite with OpenTelemetry to surface test results in your existing monitoring stack?
- Move: Integrate OpenTelemetry into your test framework to send results to a monitoring dashboard, as Simon’s team did with Robot MK and Jaunty.
- Why Now?: Simon’s team ran this as an experiment and found it “opens a lot of new ways to display the data”. He hopes to get it “into the next version of Jack and Kay”, suggesting the pattern is still emerging.
- Expected Upside: You could propose a unified view of test health alongside production metrics, reducing the gap between test execution and operational visibility.
-
What if you paired AI with exploratory testing sessions to build a regression suite in a high-churn development phase?
- Move: Have a tester write Robot Framework keyword tests in tandem with exploratory testing, using AI to scaffold custom keywords and pull in libraries quickly.
- Why Now?: Lydia’s team found this “made it work” during a phase where “there’s too much churn in the test cases” to normally automate.
- Expected Upside: You could reduce the budget for regression suite creation while keeping a human in the loop to validate whether failures are expected, as Lydia’s team did.
-
What if you documented a style guide for your test automation before your team scales?
- Move: Create a shared style guide covering project structure, naming conventions, and best practices for your framework of choice.
- Why Now?: Kelby’s guide “took two years of work” but became a reference point the team can “reference it when using AI tooling”.
- Expected Upside: You could propose this as a way to streamline onboarding for new developers and give AI tools a consistent reference for generating test code.
Takeaway
- Use Robot Framework’s library architecture to let one small team cover multiple tech stacks: “someone can jump to from a mobile project one day to a desktop project another day to some sort of embedded instrument work another day”.
- Pair AI with exploratory testing to build regression suites faster in high-churn phases: the tester could “write down in language what she was doing, put those in test cases quite easily”.
- Document a style guide for your test automation to improve consistency and give AI tools a reference: Kelby’s team found they could “reference it when using AI tooling”.
- At community events, use breaks to ask speakers to summarize talks you missed: Linda found “you can talk to people about them. And that’s actually where I made great connections”.
- Form a focused working group to make content decisions “with focus and without distractions of other people that wanted to share their ideas”.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.