{"id":196430,"date":"2025-03-21T13:49:42","date_gmt":"2025-03-21T13:49:42","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/knowledge\/?post_type=topic&p=196430"},"modified":"2026-03-18T13:41:05","modified_gmt":"2026-03-18T13:41:05","slug":"leveraging-scade-test-automation-framework-to-streamline-testing-of-arinc-661-widgets","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/leveraging-scade-test-automation-framework-to-streamline-testing-of-arinc-661-widgets\/","title":{"rendered":"Leveraging SCADE Test Automation Framework to streamline testing of ARINC 661 widgets"},"content":{"rendered":"

\n
\n Photo credit: Miguel Cuenca @Pexels<\/a><\/em>\n<\/p>\n

The ARINC 661<\/a> avionics standard, developed by Aeronautical Radio, Inc., is pivotal in modern Cockpit Display Systems (CDS): it enhances the efficiency, usability, and safety of aircraft cockpit interfaces. Ansys has been an active member in the ARINC 661 standard definition committee<\/a> since its inception, more than two decades ago.<\/p>\n

With the increased sophistication of avionics systems, ARINC 661 has become complex, featuring almost 120 widgets in Supplement 9. Each widget has unique behavior and display, making it time-consuming to test an ARINC 661 Server implementation.<\/p>\n

In this blog series, we will explore a streamlined approach for testing the ARINC 661 Widgets using the SCADE Test Automation Framework (TAF) for widgets implemented with Ansys SCADE Solutions for ARINC 661 Compliant Systems.<\/p>\n

In this article, we will first discuss the benefits and challenges of automatically testing ARINC 661 Widgets. We will then cover the features of TAF and how it addresses these challenges. Finally, we will guide you through the setup of the environment and share a concise example of testing a widget.<\/p>\n

So, let’s get started on our journey.<\/p>\n

Quick Introduction to ARINC 661 Widgets and their test automation<\/h4>\n

ARINC 661 is a standard for defining interactive avionics display systems. Its intent is to minimize the effort and cost of improving cockpits as technology evolves (new avionics systems, new features on existing systems, new hardware in the cockpit). Widely adopted across the aerospace industry, it promotes interoperability between avionic systems and simplifies vendor integration. <\/p>\n

It is composed of UAs (for the logic), a CDS (server implementing the Widgets defined in the standard), and a safe runtime communication protocol. <\/p>\n

If you are not familiar with this standard, we invite you to check our entry-level introduction to ARINC 661 in this previous blog post<\/a>.<\/p>\n

\n
\n <\/em>\n<\/p>\n

The initial testing activities for a hand-coded CDS project with 94 widgets are estimated<\/a> to require around 300 person-months, excluding verification activities. With ARINC 661 Supplement 9 specifying 119 widgets and this number continually increasing, the workload for testing future CDS projects will only grow.<\/p>\n

The need for automated testing in the development of ARINC 661 Widgets cannot be overstated, as it offers numerous benefits that significantly improve the efficiency and reliability of the testing process. By automating tests, development teams can achieve faster results, which is essential in today’s fast-paced world.<\/p>\n

Automated testing also aligns seamlessly with CI\/CD practices, empowering developers to quickly identify and fix issues early in the project while ensuring that changes do not disrupt the implementation. It also supports Continuous Improvement initiatives by enabling teams to consistently improve test cases and test procedures, maintaining high-quality software while keeping pace with rapid development cycles. Additionally, incorporating automated testing with TDD (Test Driven Development<\/a>) leads to better design and maintainable implementations.<\/p>\n

Automated testing eliminates human error, providing reliable results every time it is run, removing the need for tedious manual scenarios, and freeing up test engineers for other critical tasks in the development process. This boosts morale and energy levels. By enabling reproducibility, automated testing facilitates multi-target testing, ensuring that the CDS system functions consistently across various embedded hardware configurations.<\/p>\n

These benefits of automatically testing ARINC 661 widgets make it a crucial component of an efficient development cycle. However, it encounters several challenges in its implementation:<\/p>\n