The new additions can be used for the implementation of both classic signal-oriented communication and new, design paradigms like service-oriented communication. CANoe 14 can also be used to test software-only systems in virtual environments. These two changes allow CANoe version 14 to be used in industries outside of the automotive industry.
For over 20 years CANoe has been used in the development and testing of ECUs and control systems for the automotive sector. With changes occurring in other markets, CANoe is now applicable for software testing in many other areas. In Vector’s second major release this year, the company has introduced a new communication concept that supports applications with service-oriented architectures (SOA) in addition to classic signal-oriented communication.
The change allows both classic and service-oriented workflows to be used in parallel. CANoe users can continue to use it as they normally would. It can also be deployed to support users who implement SOA projects, such as within AUTOSAR Adaptive. In the automotive industry, the focus of the systems to be tested is moving from real ECUs to software-only systems. Here, CANoe can handle a greater number of software interfaces than classic network accesses. The new communication concept also makes CANoe ideal for applications outside the automotive industry, such as medical technology or Industry 4.0.
Continuous Integration (CI) is a frequently used method to increase the quality of software. A characteristic feature of a CI workflow is the frequent and automated testing of program code at an early stage. CANoe 14 supports this process by making it easy to integrate the deployment of the remaining system and the execution of automated tests into a CI tool chain. Access to the CI methodology means significantly more flexibility for users when simulating and testing in purely simulated runtime environments, since it is now possible to work on a server or in a cloud.