Summary:
In this episode of the Testing 1, 2, 3 podcast, Joanna Schloss and Arthur Hicken dive into real-world stories and observations about the effects of software in everyday life, particularly in API first development. The conversation also touches on software testing issues, emphasizing the importance of collaboration across teams, the complexities of modern APIs, and solutions like service virtualization for realistic testing.

Abstract:
Joanna Schloss and Arthur Hicken reflect on how software and AI are changing everyday experiences, especially in the realm of vehicle technology and API-driven environments. They discuss issues with software testing in automotive systems, particularly software-defined vehicles, and the difficulty in debugging complex interactions within the car’s multiple computing devices. Arthur shares an amusing yet frustrating story about troubleshooting his Fiat 500E and the lessons learned from the experience. The episode also delves into the chaos that can arise when teams do not communicate effectively during the development process, as well as the critical need for testing systems to interact properly. Service virtualization is suggested as a solution to help teams test more effectively, simulate real-world conditions, and avoid the pitfalls of untested software.

Key Takeaways:

1. The Growing Complexity of Software-Defined Vehicles: Cars, particularly electric vehicles, are increasingly reliant on complex software systems that can lead to challenging and frustrating user experiences when things go wrong.
2. Testing Interactions Between Systems: The difficulty in testing how different software components interact within a system, especially in vehicles, is a significant challenge. Modern cars have many embedded systems that may not be tested together.
3. Miscommunication Between Teams: Lack of communication between different teams (e.g., back-end, front-end, API developers) can cause major issues, as seen in real-world examples of product development chaos.
4. Service Virtualization: This technique allows testing in situations where certain components or services are unavailable or incomplete, simulating real-world conditions to ensure systems function properly before going live.
5. Importance of Thorough Testing and Collaboration: Successful software development, especially in complex systems like cars or APIs, depends on clear specifications, collaboration, and realistic testing scenarios to prevent failure and ensure reliability.

This podcast highlights both the humor and the frustrations of the ever-evolving relationship between software, hardware, and real-world usage.

🔗 Explore More from Parasoft

Stay connected and dive deeper into the world of automated software testing and AI-driven quality assurance:

• 🌐 Website: www.parasoft.com
• 🎧 Podcast Hub: Testing 1-2-3 on Buzzsprout
• 💼 LinkedIn: Parasoft on LinkedIn
• 📘 Facebook: Parasoft on Facebook

Join our community for the latest insights, episodes, and discussions on software testing, AI integration, and quality assurance best practices.

As artificial intelligence (AI) continues to transform the automotive industry, one question remains at the center of innovation: Who’s accountable when AI goes wrong? In this thought-provoking episode of Testing 1-2-3, Parasoft’s Arthur Hicken (a.k.a. The Code Curmudgeon) and Chief Marketing Officer for Parasoft, Joanna Schloss tackle the ethical, legal, and technical challenges posed by AI in autonomous vehicles.

🚗 What You’ll Learn in This Episode:

• What is the "trolley problem," and why is it constantly referenced in discussions about AI ethics?
• Who’s legally responsible when an autonomous vehicle causes an accident— the manufacturer, the developer, or the driver?
• How Volvo’s bold move to accept liability may reshape consumer trust in self-driving technology.
• The role of software testing, quality assurance, and transparency in minimizing real-world risks.
• Surprising responses from popular AI tools like GitHub Copilot when asked about ethical decision-making and liability.

🎙️ Why This Episode Matters:
Whether you're a developer building enterprise applications, a QA engineer testing machine learning models, or a tech leader steering digital transformation, the implications of AI-driven automation go far beyond code. As AI systems increasingly influence safety-critical decisions, understanding your ethical and legal responsibilities as a technologist is essential.

🧠 Real Talk, Real Risks:
Arthur shares firsthand experiences using open-source software to enable semi-autonomous driving in his own vehicle—raising important questions around consent, responsibility, and risk. Joanna draws a compelling parallel to the real-world fallout of the 2024 CrowdStrike endpoint failure, highlighting how even non-automotive software can impact public safety in unexpected ways.

💡 Key Takeaways:

• Autonomous driving isn’t just a hardware problem—it’s a software quality problem.
• Product liability laws are being tested in new ways as AI makes more independent decisions.
• Software engineers must think beyond functionality to ethics, safety, and accountability.
• AI may lack principles, but your software design and testing shouldn't.

Don’t miss this essential conversation for anyone working with or around AI.
Hit play, subscribe to Testing 1-2-3, and join us as we break down the intersection of ethics, automation, and accountability—one question at a time.

🔗 Explore More from Parasoft

Stay connected and dive deeper into the world of automated software testing and AI-driven quality assurance:

• 🌐 Website: www.parasoft.com
• 🎧 Podcast Hub: Testing 1-2-3 on Buzzsprout
• 💼 LinkedIn: Parasoft on LinkedIn
• 📘 Facebook: Parasoft on Facebook

Join our community for the latest insights, episodes, and discussions on software testing, AI integration, and quality assurance best practices.

Welcome back to Testing 1, 2, 3 with Joanna Schloss and Arthur Hicken!

In this episode, the duo is joined by Michal Rozenau, a seasoned MISRA C expert and project lead engineer at Parasoft.

Tune in as they unpack the latest MISRA C:2025 update, how it's evolving to accommodate AI-generated code, and what it means for safety-critical embedded systems. The trio also explores the growing interest in Rust, its intersection with MISRA, and the broader push for reliable software standards in the age of automation and machine learning.

Whether you're a compliance pro or just dipping your toes into MISRA, this episode has something for everyone.

🔗 Explore More from Parasoft

Stay connected and dive deeper into the world of automated software testing and AI-driven quality assurance:

• 🌐 Website: www.parasoft.com
• 🎧 Podcast Hub: Testing 1-2-3 on Buzzsprout
• 💼 LinkedIn: Parasoft on LinkedIn
• 📘 Facebook: Parasoft on Facebook

Join our community for the latest insights, episodes, and discussions on software testing, AI integration, and quality assurance best practices.

Join hosts Joanna and Arthur in this insightful episode of Testing 1-2-3 as they dive into the evolving world of Rust programming, testing best practices, and the vibrant Rust community. Recorded live from The Brewery in London during a major tech conference, Arthur shares firsthand observations from the event, including keynote attendance, session highlights, and the growing momentum behind Rust’s adoption.

Key Discussion Points:

• Rust’s Testing Landscape: Explore the unique challenges of ensuring quality, safety, and security in Rust code. Learn why the language’s reliance on external libraries demands scrutiny and how open-source tools like code scorecards evaluate project health through code reviews, static analysis, and unit testing.
• Tooling Gaps & Opportunities: Discover why Rust’s ecosystem currently leans on open-source solutions for static analysis and coverage, and why commercial tooling is critical for scalability. Arthur breaks down the hurdles of measuring code coverage via LLVM and the community’s push for robust, enterprise-ready solutions.
• Static Analysis Beyond Bug Hunting: Unpack how Rust developers view static analysis not just as a bug detector but as a way to enforce context-specific coding standards—a paradigm shift for safer, more reliable software.
• Community Momentum: With 400+ attendees and growing interest in cybersecurity sessions, hear how Rust’s community is expanding and what this means for developers prioritizing safety-critical systems.

Featured Insights:

• Why writing custom static analysis checkers is possible but not practical for most teams.
• The role of unit testing and coverage metrics in Rust’s maturation.
• Arthur’s take on the future of commercial tooling and collaborative quality practices.

Subscribe to the Testing 1-2-3 Podcast for deep dives into software development, testing strategies, and expert interviews.

Listen now to stay ahead in the fast-paced world of software quality! 🎧

Keywords: Rust programming, Rust testing, code quality, static analysis, unit testing, code coverage, cybersecurity, open-source tools, Rust community, software security, Embedded World, Parasoft, LLVM, software development best practices.

Join hosts Joanna Schloss, Chief Marketing Officer at Parasoft, and Arthur Hicken, Senior Software Evangelist at Parasoft, in Episode 3 of Testing 1, 2, 3 as they dive into the fast-evolving world of embedded software, AI’s disruptive role in development, and the urgent need for safety and security in an increasingly connected world. Recorded on Valentine’s Day, this episode balances technical insights with lighthearted banter as the duo explores:

1. The Software Revolution in Embedded Systems
   • How cars evolved from 50 lines of code to 100 million—and why modern vehicles are now "moving computers."
   • The risks of IoT vulnerabilities (e.g., hacking tire pressure sensors to control critical systems).
   • Why agile workflows, CI/CD pipelines, and automated testing are non-negotiable for today’s developers.
2. Safety-Critical Challenges
   • The growing overlap between security, safety, and reliability in automotive, medical, and aerospace systems.
   • Why standards like MISRA, CERT, and UL2900 are critical for certifying code in high-stakes environments.
   • The "curmudgeon’s rule of testing": Ensuring tests prove functionality and expose failures meaningfully.
3. AI’s Double-Edged Sword
   • Can AI-generated code meet safety-critical standards? Spoiler: Guardrails are essential.
   • Why AI accelerates productivity for experts but amplifies risks for novices.
   • The future of AI in testing: Generating smarter test cases vs. creating "meaningless noise."
4. Industry Shifts & Upcoming Events
   • Embedded World 2024 preview: What to expect from Nuremberg (March 12–13) and the push for Rust in safety-critical systems.
   • The rise of "software-defined everything" and how startups disrupt traditional industries.
   • A playful debate: VI vs. Emacs (share your hot takes!).

Key Quotes:

• "100 million lines of code can’t be understood by humans—tooling isn’t optional anymore."
• "AI in safety-critical systems is like handing a toddler a chainsaw: powerful but dangerous without oversight."
• "MISRA isn’t about making life harder—it’s about coding for analyzability and trust."

Tune In If You’re:

• A developer, tester, or engineer in automotive, IoT, or embedded systems.
• Curious about AI’s role in coding and testing (and its limitations).
• Preparing for Embedded World or Rust Nation and want insider perspectives.

Stay Connected:

• Follow Parasoft for updates on industry events, tools, and standards.

Cybersecurity Mandates & the Future of Software Security

Cybersecurity is no longer an afterthought—it’s becoming a mandated priority for software teams across industries. A new executive order is setting the stage for stricter security regulations, pushing companies to adopt more robust security measures, comply with unified standards, and provide concrete proof of software integrity. But what does this mean for developers, testers, and organizations that build and deploy critical applications?

In this episode, Arthur Hicken (the Code Curmudgeon) and Joanna Schloss (CMO at Parasoft) break down the most impactful aspects of this executive order, explaining how it will reshape the way software security is approached. They discuss the evolving role of penetration testing, the push for software security attestations, and how organizations can prepare for future compliance requirements.

Key Takeaways:

• Mandatory Cybersecurity Standards: How the government is moving toward consolidated, enforceable security benchmarks for software development.
• The Role of Penetration Testing: Why companies will need to provide proof of security measures rather than just claim compliance.
• Software Security Attestations: The shift from informal security commitments to structured, auditable security validations.
• The Future of Compliance: What developers, testers, and security professionals need to do now to align with emerging regulations.

Don’t get caught off guard—tune in to learn how you can stay ahead of these critical changes and strengthen your software security strategy.

Kick off the new year with actionable insights on overcoming Agile challenges and embracing AI-driven innovations in software testing! In this episode of Testing 1-2-3, brought to you by Parasoft, Arthur Hicken (the Code Curmudgeon) and Joanna Schloss (Chief Marketing Officer at Parasoft) dive into practical New Year’s resolutions for software teams.

From improving collaboration between developers and testers to tackling flaky test automation and mastering test data management, Arthur and Joanna share strategies to help your team thrive in Agile environments. They also explore the growing role of AI in software testing and why continuous learning is essential to stay ahead in today’s fast-evolving tech landscape.

Whether you’re a seasoned Agile practitioner or just starting your journey, this episode is packed with tips to help you deliver higher-quality software in 2025 and beyond. Tune in and make this year your most efficient and innovative yet!

Testing 1-2-3 is your go-to podcast for all things software testing, performance, and security—brought to you by the experts at Parasoft. Don’t miss it!

Developers need love too! Advocating for developers isn’t new, but in a world where they're constantly under pressure to keep pace with the demands of digital transformation, expecting developers to care about security can create friction in many DevSecOps environments.

Studies suggest that security teams believe developers don’t take the security of applications seriously and will sacrifice security in favor of innovation. Shifting this perception requires strong collaboration combined with automating and integrating well-established security practices into developers' existing workflows.

Join us to discuss:

• Being a developer advocate.
• Building a culture that reduces friction in DevSecOps.
• Approaches for integrating security into developers daily activities.