configured load tests for azure #1057
Conversation
| "serverless": "1.83.3", | ||
| "serverless-artillery": "0.5.2", |
There was a problem hiding this comment.
So bad we're still relying on this, as this package has been abandoned. Just as a reminder for ourselves, there's a pending issue related to finding an alternative or building this capability within Booster #934
| @@ -86,7 +86,8 @@ | |||
| "integration/azure-deploy": "TESTED_PROVIDER=AZURE BOOSTER_ENV=azure mocha --forbid-only --exit --config \"integration/provider-specific/azure/deployment/.mocharc.yml\" \"integration/provider-specific/azure/deployment/**/*.integration.ts\"", | |||
| "integration/azure-nuke": "TESTED_PROVIDER=AZURE BOOSTER_ENV=azure mocha --forbid-only --exit --config \"integration/provider-specific/azure/nuke/.mocharc.yml\" \"integration/provider-specific/azure/nuke/**/*.integration.ts\"", | |||
| "integration/azure-end-to-end": "TESTED_PROVIDER=AZURE BOOSTER_ENV=azure mocha --forbid-only --exit --config \"integration/provider-unaware/end-to-end/.mocharc.yml\" \"integration/provider-unaware/end-to-end/**/*.integration.ts\"", | |||
| "integration/azure-func": "TESTED_PROVIDER=AZURE BOOSTER_ENV=azure mocha --forbid-only --exit --config \"integration/provider-unaware/end-to-end/.mocharc.yml\" \"integration/provider-unaware/functionality/**/*.integration.ts\"" | |||
| "integration/azure-func": "TESTED_PROVIDER=AZURE BOOSTER_ENV=azure mocha --forbid-only --exit --config \"integration/provider-unaware/end-to-end/.mocharc.yml\" \"integration/provider-unaware/functionality/**/*.integration.ts\"", | |||
| "integration/azure-load": "TESTED_PROVIDER=AZURE AWS_SDK_LOAD_CONFIG=true BOOSTER_ENV=azure mocha --forbid-only --exit --config \"integration/provider-unaware/load/.mocharc.yml\" \"integration/provider-unaware/load/**/*.load.ts\"" | |||
There was a problem hiding this comment.
Should we add this call on the "integration/azure" script (line 85)?
javiertoledo
force-pushed
the
main
branch
3 times, most recently
from
bcad4f1 to
672334e
Compare
…_test_azure # Conflicts: # package-lock.json # packages/framework-integration-tests/package.json
|
/integration sha=792b5d6bf320704a207d5acc1ef92b1cf2284cac |
|
⌛ Integration tests are running... Check their status here 👈 |
|
❌ Oh no! Integration tests have failed |
|
/integration sha=f7a32b7d18aaa1b7d0c961433089a3edcd42fb26 |
|
⌛ Integration tests are running... Check their status here 👈 |
|
❌ Oh no! Integration tests have failed |
…_test_azure # Conflicts: # common/config/rush/pnpm-lock.yaml
|
/integration sha=3e61b829586e58a7c565b7c83ed144ee0d7fdd6a |
|
⌛ Integration tests are running... Check their status here 👈 |
|
❌ Oh no! Integration tests have failed |
Description
In this PR we are configuring the load tests for the Azure provider. Basically we have reverted serverless framework to the old version because it is not compatible with Serverless Artillery and then we have had to increase the timeout in the tests and adapted the load to be manageable by Azure. We achieve 200 requests/sec during 10 sec followed by 400 req/sec for 10sec.
Changes
Checks