Adding Frontend/API testing functionality to pipeline/stacks.

[ophilli]

😔 This branch cannot be rebased due to conflicts. Perhaps you need to rebase & force push onto your branch? Or perhaps you need to eat it and make a merge commit.

[DillonRanwala]

I tried rebasing with a force push, but that didn't seem to do anything. On my end, I'm not seeing any merge conflicts, but I can still try to make a merge commit.

[DillonRanwala]

I tried rebasing with a force push, but that didn't seem to do anything. On my end, I'm not seeing any merge conflicts, but I can still try to make a merge commit.

Update, I didn't rebase properly the first time. I dropped a commit which I think might have been the issue, and I'm not seeing any merge conflicts on my end.

[DillonRanwala]

Notes on testing in Beta before approving this change to Prod.

• CodePipeline successfully ran the ShellStep tests for curling the front end and testing the APIs with dummy data.
• Also, the TestAPILambda was successfully created and succeeded when tested (via the Lambda service test option).
• The Beta websites were working with the Cloudfront distribution.
• Normal visit requests were handled correctly by the API gateway and lambdas while being put in the DynamoDB tables.
• The Beta tables were changed to have a TTL attribute, and the test items from the pipeline and testing canary were properly deleted automatically from all tables (by using the last_updated field).
• New and existing non-test items were not affected by the new TTL setting.

Therefore, I feel confident in pushing this change to Production.