Use Amazon IoT Greengrass Testing Framework - Amazon IoT Greengrass
How it worksChangelog
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Use Amazon IoT Greengrass Testing Framework

Greengrass Testing Framework (GTF) is a collection of building blocks that supports end-to-end automation from the customer perspective. GTF uses Cucumber as the feature driver. Amazon IoT Greengrass uses the same building blocks to qualify software changes on various devices. For more information, see Greengrass Testing Framework on Github.

GTF is implemented using Cucumber, a tool used to run automated tests, to encourage a Behavior-Driven Development (BDD) of the components. In Cucumber, the features of this system are outlined in a special type of file called feature. Each feature is described in a human-readable format called scenarios which are specifications that can be converted into automated tests. Each scenario is outlined as a series of steps that define the interactions and outcomes of this system under test using a domain-specific language called Gherkin. A Gherkin step is linked to the programming code using a method called step definition which hard wires the specification to the test flow. Step definitions in GTF are implemented with Java.

Topics

How it works

Amazon IoT Greengrass distributes the GTF as a standalone JAR that consists of several Java modules. To use GTF for end-to-end testing of components, you must implement the tests within a Java project. Adding the testing standable JAR as a dependency in your Java project enables you to use the existing functionality of the GTF and extend it by writing your own custom test cases. To run the custom test cases, you can build your Java project and run the target JAR with the configuration options described in Greengrass Testing Framework configuration options.

GTF standalone JAR

Greengrass uses Cloudfront as a Maven repository to host different versions of the GTF standalone JAR. For a full list of GTF versions, see GTF releases.

GTF standalone JAR includes the following modules. It is not limited to only these modules. You can pick and choose each of these dependencies separately in your project or include all of them at once with the testing standalone JAR file.

  • aws-greengrass-testing-resources: This module provides abstraction for managing the lifecycle of an Amazon resource during the course of a test. You can use this to define your custom Amazon resources using ResourceSpec abstraction so GTF can take care of creation and removal of those resources for you.

  • aws-greengrass-testing-platform: This module provides platform-level abstraction for the device under test during the test lifecycle. It contains APIs used to interact with the OS independent of the platform and can be used to simulate the commands running in the device shell.

  • aws-greengrass-testing-components: This module consists of sample components that are used for testing the Greengrass core features such as deployments, IPC, and other features.

  • aws-greengrass-testing-features: This module consists of reusable common steps and their definitions which are used for testing within in the Greengrass environment.

Topics

Changelog

The following table describes the changes in each version of the GTF. For more information, see the GTF Releases page on GitHub.

Version

Changes
1.2.0
New features

  • Adds network-related steps to configure MQTT and internet network connectivity during tests.

  • Adds system metric steps to monitor device RAM and CPU use.

Bug fixes and improvements

  • Greengrass CLI local deployment step retries until it succeeds.

  • Tests gracefully stop Greengrass nucleus instead of killing it.

  • Adds improvement where GTF polls the Amazon IoT Credentials endpoint until credentials are retrievable for the thing and role alias.

  • Fixes missing artifacts and recipe directories. This version also fixes missing component versions.

  • Fixes an issue where GTF fails during docker image cleanup if the docker image does not exist.

  • Adds CURRENT keyword as version of component.

1.1.0
New features

  • Adds the ability to install a custom component with configuration. This requires a recipe for the custom component.

  • Adds the ability to update a local deployment with a custom configuration.

Bug fixes and improvements

  • Fixes log context GTF version inconsistency issue.

1.0.0

Initial version.