This framework is a collection of building blocks that supports end to end automation from the customer perspective using Cucumber as the feature driver. AWS Greengrass uses the same building blocks to qualify software changes on various devices.
- AWS Resource Management (
aws-greengrass-testing-resources) - A platform abstraction over Java Process API
- A bunch of common steps (
aws-greengrass-testing-features) - The ability for features to be driven through IDT.
- Example use-cases and components (
aws-greengrass-testing-components) - Service discovery for extensions such as other AWS resources, steps, and configuration.
First time instructions
Install the latest StreamManger SDK locally.
Unix Based Systems
If the directory ./aws-greengrass-testing-components/aws-greengrass-testing-components-streammanager/lib/streammanager exists in your project, remove it by running the following command:
rm -rf ./aws-greengrass-testing-components/aws-greengrass-testing-components-streammanager/lib/streammanager
This makes sure that when you run the following commands you get a fresh version of the project's submodules.
From the root of the project run:
git submodule update --init
mvn process-resources
Windows
For the git submodule update --init command to work on Windows the core.longpaths setting
must be enabled on git. To do that:
- Open a command prompt as Administrator
- Run
git config --global core.longpaths true
Windows has a limit of 260 chars for file names. When pulling the submodules, the file names have paths that are longer than 260 characters, which causes pulling the submodule to fail.
Note:
After enabling core.longpaths, if the directory .\aws-greengrass-testing-components\aws-greengrass-testing-components-streammanager\lib\streammanager exists in your project, remove it by running the following command, or delete the folder using the UI.
rm .\aws-greengrass-testing-components\aws-greengrass-testing-components-streammanager\lib\streammanager
This makes sure that when you run the following commands you get a fresh version of the project's submodules.
From the root of the project run:
git submodule update --init
mvn process-resources
After the command succeeds you should be able to find this jar
aws-greengrass-testing-components/aws-greengrass-testing-components-streammanager/lib/streammanager/sdk/aws-greengrass-stream-manager-sdk-java.jar
Regular compilation instructions
Replace compile with package to build shared jars.
mvn clean compile
Run integration tests
- Download the latest Greengrass archive at the example component path:
curl https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-nucleus-latest.zip -o aws-greengrass-testing-examples/aws-greengrass-testing-examples-component/greengrass-nucleus-latest.zip
-
Get credentials for an AWS account. The test needs credentials to identify the AWS account to use and to create test resources in the account. For instructions, see Set default credentials and Region. The credentials must be available on the device. Some options are:
- Copy temporary credentials and set them as env variables
- Set the AWS profile for your environment
-
Configure user credentials for Windows devices
- Open the Windows Command Prompt (cmd.exe) as an administrator.
- Create user in the LocalSystem account on the Windows device. Replace user-name with the same name of your current system user. Replace password with a secure password.
net user /add user-name password
- Download and install the PsExec utility from Microsoft on the device.
- Use the PsExec utility to store the user name and password in the Credential Manager instance for the LocalSystem account.
- Run the following command. Replace user-name and password with the user's user name and password that you set earlier.
psexec -s cmd /c cmdkey /generic:user-name /user:user-name /pass:password
- If the PsExec License Agreement opens, choose Accept to agree to the license and run the command.
- Run the following command. Replace user-name and password with the user's user name and password that you set earlier.
-
Run the integration tests (For Windows device, open the Windows Command Prompt (cmd.exe) as an administrator to run below tests):
- Example component tests:
mvn clean -DskipTests=false -pl aws-greengrass-testing-examples/aws-greengrass-testing-examples-component -am integration-test
- MQTT tests:
mvn clean -DskipITs=false -pl aws-greengrass-testing-features/aws-greengrass-testing-features-mqtt/ -am integration-test
- Cloud component tests:
mvn clean -DskipTests=false -pl aws-greengrass-testing-features/aws-greengrass-testing-features-cloudcomponent/ -am integration-test
- Example component tests:
Running tests with an HSM
Any test can be run with an HSM configuration. HSM configuration parameters are defined in the HsmParameters.java file. If ggc.hsm.configured is set to true, you must configure the other HSM parameters. When an HSM is configured, this initial config file is used to start Greengrass. Before you run tests with an HSM, following is required:
- Install the HSM on the DUT.
- Create and add a device certificate to the HSM, along with a private key. You specify the certificate ARN and HSM labels for the key and cert as parameters.
- Install the PKCS library on the host or the DUT. If the library is on the DUT, specify the library path with a prefix "dut:"
- Similarly, the PKCS plugin jar can be on the host agent or on the DUT. If it is on the DUT, specify the path with the prefix "dut:"
Debugging test failures
Set the test log path using the "test.log.path" property in the project. The default value is
"testResults". By default, logs for the example component test run are found at aws-greengrass-testing-examples/aws-greengrass-testing-examples-component/testResults
Fixing licenses
mvn license:format
See CONTRIBUTING for more information.
This project is licensed under the Apache-2.0 License.
GitHub issue is the preferred channel to interact with our team.