Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(uat): implement ggmq scenario based on GGAD-1-T24 #375

Conversation

eschastlivtsev
Copy link

@eschastlivtsev eschastlivtsev commented Jul 21, 2023

Description of changes:

  • Add T24 scenario

Why is this change necessary:
Implement scenarios

How was this change tested:
Run scenario locally

Test results:

Given my device is registered as a Thing....................................passed
And my device is running Greengrass.........................................passed
When I create a Greengrass deployment with components.......................passed
And I create client device "publisher"......................................passed
And I create client device "subscriber".....................................passed
And I update my Greengrass deployment configuration, setting the component aws.greengrass.clientdevices.Auth configuration to:.passed
And I update my Greengrass deployment configuration, setting the component aws.greengrass.client.Mqtt5JavaSdkClient configuration to:.passed
When I associate "publisher" with ggc.......................................passed
When I associate "subscriber" with ggc......................................passed
And I deploy the Greengrass deployment configuration........................passed
Then the Greengrass deployment is COMPLETED on the device after 5 minutes...passed
And the aws.greengrass.clientdevices.mqtt.EMQX log on the device contains the line "is running now!." within 1 minutes.passed
And I discover core device broker as "default_broker" from "publisher" in OTF.passed
And I connect device "publisher" on aws.greengrass.client.Mqtt5JavaSdkClient to "default_broker" using mqtt "v3".passed
And I connect device "subscriber" on aws.greengrass.client.Mqtt5JavaSdkClient to "default_broker" using mqtt "v3".passed
When I subscribe "subscriber" to "iot_data_0" with qos 1....................passed
When I publish from "publisher" to "iot_data_0" with qos 1 and message "Test message0" and expect status 0.passed
And message "Test message0" received on "subscriber" from "iot_data_0" topic within 5 seconds.passed
And I update my local deployment configuration, setting the component aws.greengrass.clientdevices.Auth configuration to:.passed
Then the local Greengrass deployment is SUCCEEDED on the device after 120 seconds.passed
Then I wait 65 seconds......................................................passed
When I publish from "publisher" to "iot_data_0" with qos 1 and message "Test message1" and expect status 0.passed
And message "Test message1" is not received on "subscriber" from "iot_data_0" topic within 10 seconds.passed
And I update my local deployment configuration, setting the component aws.greengrass.clientdevices.Auth configuration to:.passed
Then the local Greengrass deployment is SUCCEEDED on the device after 120 seconds.passed
Then I wait 65 seconds......................................................passed
When I publish from "publisher" to "iot_data_0" with qos 1 and message "Config update works" and expect status 0.passed
And message "Config update works" received on "subscriber" from "iot_data_0" topic within 5 seconds.passed

All clients:

[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v3-sdk-java: As a customer, I can reset CDA config and update it and CDA will use the new config'
[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v3-mosquitto-c: As a customer, I can reset CDA config and update it and CDA will use the new config'
[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v3-paho-java: As a customer, I can reset CDA config and update it and CDA will use the new config'
[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v3-paho-python: As a customer, I can reset CDA config and update it and CDA will use the new config'
[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v5-sdk-java: As a customer, I can reset CDA config and update it and CDA will use the new config'
[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v5-mosquitto-c: As a customer, I can reset CDA config and update it and CDA will use the new config'
[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v5-paho-java: As a customer, I can reset CDA config and update it and CDA will use the new config'
[INFO ] 2023-07-20 18:14:25.209 [main] StepTrackingReporting - Passed: 'GGMQ-1-T24-v5-paho-python: As a customer, I can reset CDA config and update it and CDA will use the new config'

Any additional information or context required to review the change:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@eschastlivtsev eschastlivtsev force-pushed the GGMQ-205-implement-ggmq-scenario-based-on-ggad-1-t-24 branch from 7b413a7 to e72597c Compare July 21, 2023 14:38
@MikeDombo MikeDombo merged commit 9744afa into aws-greengrass:uat-dev Jul 21, 2023
6 of 7 checks passed
@eschastlivtsev eschastlivtsev deleted the GGMQ-205-implement-ggmq-scenario-based-on-ggad-1-t-24 branch July 24, 2023 07:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants