apache / apache/pekko-connectors
Add AWS only tests for MQTT behaviour that is only visible in AWS IoT
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 82
- Forks
- 50
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 78
Description
In https://github.com/apache/pekko-connectors/pull/1152, fixes were applied for behaviour that is only specific against AWS IoT. Once that PR is merged, we should speak with ASF Infra to setup an AWS IoT account (we already have one for S3) so that we can write specific tests that only run on the test AWS IoT account.
The tests should be split in a similar way that S3 is (see S3IntegrationSpec which implements a base/common set of tests and then we have MinioS3IntegrationSpec/AWSS3IntegrationSpec which specifies against which system the tests is run against and also any additional tests that should only be run on that system and/or specific tests that shouldn't be run on that system).
Might need help from @sbmpost to write the tests specific for AWS
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the S3IntegrationSpec, MinioS3IntegrationSpec, and AWSS3IntegrationSpec examples, then inspect the MQTT integration tests and the changes from pull request 1152. Coordinate with ASF Infra to confirm the AWS IoT test account and identify the AWS-only behaviours to cover. Done means shared and AWS-specific tests are separated and the AWS-only suite runs against the test account.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, scala
- Domain
- cloud, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100