Closed seankimkdy closed 2 months ago
321 tests +5 321 :white_check_mark: +5 4s :stopwatch: +2s 50 suites +1 0 :zzz: ±0 1 files ±0 0 :x: ±0
Results for commit 7f081c14. ± Comparison against base commit ddba24eb.
:recycle: This comment has been updated with latest results.
For the detailed report, please go to Checks tab
, click Build and Test
, and then download unit_test_coverage
artifact at the bottom of build page.
The coverage result does not include the functional test results.
For the detailed report, please go to Checks tab
, click Build and Test
, and then download unit_test_coverage
artifact at the bottom of build page.
The coverage result does not include the functional test results.
Resolves #453. Some unique things/limitations about AWS
Faking AWS Server for Unit Testing Unlike GCP and Azure, faking an HTTP server did not work. I used middlewares instead which is a bit of a different concept.
fakeDeserializeMiddleware
should look a lot likegetFakeServerHandler
in GCP or Azure.Using Namespaces for Resource Cleanup during Integration Test AWS does not have resource groups in the sense that Azure does, nor does it have a nice isolation mechanism like GCP project does. There's no clean way to delete resources by a group, so I had to write a custom deletion by hand in
TeardownAwsTesting
. This is also why namespace has to be unique as there can be many different tests going on in the same account for AWS.VPC Quota Limit There's currently a limit of default 5 VPCs per region in AWS. This will not do as we tend to have more >5 ongoing PRs. We should ask for an service quota increase.