Article: Low-level testing solutions and challenges
Low-level testing is a kind of software testing, that is checking if each module, function, class, and method work correctly. It verifies the system functionality at the source code level, processor instructions, registers, memory, or hardware interface. Low-level tests are commonly used in embedded systems that are integrated with hardware and have limited resources.
The aim is to identify and eliminate logical, syntactical, or implementation bugs in the code before it’s integrated with other system components. Typically, low-level tests are carried out by developers creating and modifying the source code.
Article: The matter of an embedded systems test infrastructure team tasks
Today, embedded systems are used in a wide range of industries and devices we use, from smartphones through TV sets to cars. To assure the systems are of the highest quality, it is essential to test them and, for that to happen, create appropriate test environments. The test infrastructure team provides the essential elements for conducting tests as well as the tools for the management of the testing process itself. They are the key component both for testers, who need access to the right set of tools, as well as for the customer himself who expects reliable test results.
An important part of the test infrastructure are test environments. Testing of embedded systems is focused on the actual device, which may require various types of sensors, actuators or communication interfaces (used for interaction with the surroundings or other systems) in order to work properly. When testing particular components such as an ECU (Electronic Control Unit), for example, the test environment simulates input signals and allows the tester to check output signals produced by the device. Therefore, one of the primary tasks of the infrastructure department is finding solutions, which enable us to simulate the environment, in which the device under test will be used.
In our company, B&R X20 series, controllers, and Vector VT System devices are commonly used for this purpose, which the tester is operating using the Vector CANoe software. While the Vector VT System uses a build-in communication interface within CANoe, it was the test infrastructure team’s task to create a real-time communication solution with the other components.