chore(ci): add end to end testing mechanism

.github/workflows/run-e2e-tests.yml

@@ -0,0 +1,35 @@
+name: run-e2e-tests
+on:
+  workflow_dispatch: {}
+env:
+  AWS_DEFAULT_REGION: us-east-1
+  E2E_TESTS_PATH: tests/e2e/
+jobs:
+  run:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write # needed to interact with GitHub's OIDC Token endpoint.
+      contents: read
+    strategy:
+      matrix:
+        version: ["3.7", "3.8", "3.9"]
+    steps:
+      - name: "Checkout"
+        uses: actions/checkout@v3
+      #########################
+      # Release new version
+      #########################
+      - name: "Use Python"
+        uses: actions/setup-python@v3
+        with:
+          python-version: ${{ matrix.version }}
+          architecture: "x64"
+      - name: Install dependencies
+        run: make dev
+      - name: Configure AWS credentials
+        uses: aws-actions/configure-aws-credentials@v1
+        with:
+          role-to-assume: ${{ secrets.AWS_TEST_ROLE_ARN }}
+          aws-region: ${{ env.AWS_DEFAULT_REGION }}
+      - name: Test
+        run: make e2e-test

MAINTAINERS.md

@@ -13,6 +13,7 @@
   - [Triage Bug Reports](#triage-bug-reports)
   - [Triage RFCs](#triage-rfcs)
   - [Releasing a new version](#releasing-a-new-version)
+    - [Run end to end tests](#run-end-to-end-tests)
     - [Changelog generation](#changelog-generation)
     - [Bumping the version](#bumping-the-version)
     - [Drafting release notes](#drafting-release-notes)
@@ -171,7 +172,15 @@ Some examples using our initial and new RFC templates: #92, #94, #95, #991, #122
 
 Firstly, make sure you are using the `develop` branch and it is up to date with the origin.
 
-There are three main steps to release a new version: Changelog generation, version bumping, and drafting release notes.
+There are four main steps to release a new version: Run end to end tests, Changelog generation, version bumping, and drafting release notes.
+
+#### Run end to end tests
+
+You can run tests either from your local machine's shell by exporting `AWS_PROFILE` environment variable and running `make e2e tests`. 
+You may also do this directly from GitHub Console. Go to actions tab and choose `run-e2e-tests` workflow from workflow's list. Pick the branch and run tests.
+
+> **Q: What if there's an error?**
+To be agreed
 
 #### Changelog generation
 

Makefile

@@ -17,14 +17,17 @@ lint: format
 	poetry run flake8 aws_lambda_powertools/* tests/*
 
 test:
-	poetry run pytest -m "not perf" --cov=aws_lambda_powertools --cov-report=xml
+	poetry run pytest -m "not (perf or e2e)" --cov=aws_lambda_powertools --cov-report=xml
 	poetry run pytest --cache-clear tests/performance
 
 unit-test:
 	poetry run pytest tests/unit
 
+e2e-test:
+	poetry run pytest -n 3 --dist loadscope --durations=0 --durations-min=1 tests/e2e
+
 coverage-html:
-	poetry run pytest -m "not perf" --cov=aws_lambda_powertools --cov-report=html
+	poetry run pytest -m "not (perf or e2e)" --cov=aws_lambda_powertools --cov-report=html
 
 pre-commit:
 	pre-commit run --show-diff-on-failure