When You Can't Touch the Code: Testing Embedded Systems Securely

About

Imagine a passenger aircraft grounded indefinitely just because its embedded system testing fell short under unexpected conditions.


Testing embedded systems is brutally difficult, especially when you can’t touch the code, install anything on the device, or rely on standard automation tools. As systems become more connected, more complex, and more locked down, traditional testing approaches fall apart. Manual testing can’t scale. Custom frameworks become brittle. And most automation simply can’t operate in restricted, offline, or hardware-dependent environments.


In this webinar, we’ll look at the common problems teams face across industries such as aerospace, manufacturing, healthcare, financial services, and retail. To illustrate the impact, we routinely see up to 5× increases in test coverage on devices where teams previously had zero code access or ability to instrument the system, all achieved through a non-invasive, visual, model-based approach. You’ll see how this method can finally give testers the access, coverage, and repeatability needed in these tough environments.


We’ll cover how to:

  • Free engineers from repetitive, time-consuming nightly 6-hour sanity tests by automating end-to-end workflows across multiple embedded systems and devices.
  • Test locked-down devices with zero code access and validate workflows others can’t reach.
  • Run repeatable 24/7 regressions, complete with traceable, audit-grade artefacts for compliance.
  • Uncover hidden edge cases with AI-driven exploration before they escalate in production

If you’re in charge of quality in challenging, high-stakes settings, this session gives you the practical guide you need.


Sign up to see how non-invasive testing can succeed where other methods fail.


Please select the session that works best for your time zone:

  • 24 February – 9:00 AM PT (Americas Session)
  • 25 February – 3:00 PM CET (European Session)

Presenters

  • Lindsey Rominsky
    Technical Customet Success Manager ​
    Keysight Technologies
    Lindsey Rominsky is a Technical Customer Success Manager at Keysight Technologies. She has a long career as a leader in software development including positions at IBM, General Dynamics, and Lockheed Martin. During her 14 years at Lockheed, she designed, developed, documented, tested, installed and trained a web-based tool that replaced a legacy critical component of mission operations at over 20 different customer sites. She was also a champion of agile development methodology to effectively manage her team and drive applications development.
  • Karamveer Singh
    Senior Solutions Engineer ​
    Keysight Technologies
    Karamveer Singh is an expert in edge computing capabilities and automated software testing. He has successfully managed several high-profile projects, including developing automated test frameworks for eCommerce websites and implementing edge computing capabilities in IoT devices.

    Karamveer's certification as a Scrum Master allows him to understand and address the distinct challenges of software development teams, and he has a wealth of experience in using agile techniques to enhance project outcomes. With his expertise in automated testing, Karamveer has effectively assisted many organizations in improving their testing processes and providing superior software quality.
  • Mike Wager
    Product Marketing Manager
    Keysight Technologies
    Mike Wager is a Product Marketing Manager at Keysight. Over the last decade, he has brought product ideas and services to life for digital technologies, SaaS applications, and software development. In his current role, Mike communicates the unique benefits of AI-driven test automation for various industries and use cases, including aerospace and defence, automotive IVI systems, retail point-of-sale, and enterprise applications.

Reserve Your Spot

Error: Please enter your first name.
Error: Please enter your last name.
This field is required.
This field is required.
This field is required.
This field is required.
This field is required.
When You Can't Touch the Code: Testing Embedded Systems Securely