This package contains two kind of tests:
To run these tests execute npm run test from the repository root (they run together with unit tests)
or npm run test:dir packages/integration-tests/lib/test-in-memory (to run them in isolation).
The create-amplify e2e suite tests the first-time installation and setup of a new amplify backend project. To run this suite, run
npm run test:dir packages/integration-tests/lib/test-e2e/create_amplify.test.js
To run end-to-end deployment or sandbox tests, credentials to an AWS account must be available on the machine. Any credentials that will be picked up by the default node credential provider should work. This includes setting environment variables for a default profile.
To run deployment suite, run
npm run test:dir packages/integration-tests/lib/test-e2e/deployment/*.deployment.test.js
To run sandbox suite, run
npm run test:dir packages/integration-tests/lib/test-e2e/sandbox/*.sandbox.test.js
To run deployment or sandbox test for specific project, specify exact test file, for example
npm run test:dir packages/integration-tests/lib/test-e2e/sandbox/data_storage_auth_with_triggers.sandbox.test.js
When working locally with sandbox tests, it is sometimes useful to retain deployment of test project to avoid full re-deployments while working
on single test project incrementally. To retain deployment set AMPLIFY_BACKEND_TESTS_RETAIN_TEST_PROJECT_DEPLOYMENT environment
variable to true. This flag disables project name randomization and deployment cleanup, so that subsequent runs of same test
target the same CFN stacks. This option is not available for deployment tests (hotswap is not going to work there anyway).
The backend-output e2e suite compares outputs from current codebase backend client to the backend client released on npm.
To run this suite, run
npm run test:dir packages/integration-tests/lib/test-e2e/backend_output.test.js