AUnit | Unit testing framework for Arduino platforms

The Set_Up_Case and Tear_Down_Case routines are run at the start and end of a test case. The Set_Up and Tear_Down routines are run before and after a specific test routine within a test case. This is best illustrated using the minimal example shown below. The example borrows quite some example code from the AUnit cookbook.

tests.ads (a new test case that contains 3 test routines: Test_A, Test_B and Test_C)

You need .map instead of .forEach to return an array so that React can render it effectively.

Also returning from the callback inside .forEach has no use since .forEach doesn't return an array. It returns undefined.

.forEach is useful when you want to change the contents of existing array without returning a new one. In React, JSX requires an array as a result of .map operation.

Also more valid points covered by @zhulien

According to RM B.3 (70):

An Ada parameter of an array type with component type T, of any mode, is passed as a t* argument to a C function, where t is the C type corresponding to the Ada type T.

Hence, there's no need to use package Interfaces.C.Pointers. You can just use an Ada array type. A small example:

main.cpp

To answer directly, I am fairly sure that there won't be a major issue with what you are doing here. It is a bit Hacky but the mechanism should handle it fine (as you have found). I will experiment a little and update here if there are issues.

Additionally It is interesting that you have actually done this now as we are currently working on providing a more comprehensive testing framework (unsure of exact targeted version) which might well help you further. I would be interested in gaining some insight into what you are doing and how we might make your life easier please message me if you would be interested in telling me more.

The slack statement in catch block has wrong syntax for string concatenation, ${environment} should either be wrapped in double quotes (") or ${} removed to fix the issue: