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

Do some more involved testing in CI #43

Open
NoxHarmonium opened this issue Jun 19, 2022 · 1 comment
Open

Do some more involved testing in CI #43

NoxHarmonium opened this issue Jun 19, 2022 · 1 comment
Labels
tech-debt Does not affect the end user, but impedes development of the plugin

Comments

@NoxHarmonium
Copy link
Contributor

The CI script at the moment just packages each example project. It proves that the plugin compiles and that the example projects don't throw any errors but it doesn't really test any assertions.

We should probably write some tests that check that the generated CF looks correct and that the lambda bundles contain the right files.

We could also use the deploy-all/verify-all scripts (or something similar) to actually deploy the examples somewhere and check that they work IRL

@NoxHarmonium
Copy link
Contributor Author

NoxHarmonium commented Aug 12, 2022

I've started working on this. It's in a branch (https://github.com/agiledigital-labs/aws-durable-lambda/tree/issue-43-int-test) , its mostly there I just need to work out a good IAM policy to assign the role that Github actions uses to deploy the example projects. I have a sandbox AWS account I can use, I'm just hesitant to give the role full admin access to the environment.

@NoxHarmonium NoxHarmonium added the tech-debt Does not affect the end user, but impedes development of the plugin label Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-debt Does not affect the end user, but impedes development of the plugin
Projects
None yet
Development

No branches or pull requests

1 participant