Greengrass IPC test runs using Greengrass Development Kit Command-Line Interface (GDK CLI).

For Greengrass IPC sample to work, it should be deployed as a Greengrass component.
The following files defines this component:

• gdk-config.json - gdk reads this file to build and publish component.
• copy_files.sh - utility to copy all required files for gdk to be able to build the component.
• recipe.yaml - defines a component's details, dependencies, artifacts, and lifecycles.

The first step is to build GreengrassV2 component artifacts and recipes from its source code:

gdk component build

Then the following command builds the testing module:

gdk test-e2e build

Finally, the test can run:

gdk test-e2e run

The test behavior is defined in the component.feature config file using a domain-specific language called Gherkin.

The test spins up Greengrass core, installs and configures Greengrass component dependencies (including the custom Greengrass component described in the previous section). After everything is set up, it performs checks. They are defined at the very bottom of the file and basically grep a log file for specific messages.

On completion, the test creates log files in testResult directory with the run details. The component's logs are stored in testResult/gg-<RANDOM_STRING>/software.amazon.awssdk.sdk-gg-ipc.log file. Though, if error occurred before the component started its execution, this file might be absent.