|
13 | 13 | - [Triage Bug Reports](#triage-bug-reports)
|
14 | 14 | - [Triage RFCs](#triage-rfcs)
|
15 | 15 | - [Releasing a new version](#releasing-a-new-version)
|
16 |
| - - [Run end to end tests](#run-end-to-end-tests) |
17 | 16 | - [Changelog generation](#changelog-generation)
|
18 | 17 | - [Bumping the version](#bumping-the-version)
|
19 | 18 | - [Drafting release notes](#drafting-release-notes)
|
| 19 | + - [Run end to end tests](#run-end-to-end-tests) |
20 | 20 | - [Releasing a documentation hotfix](#releasing-a-documentation-hotfix)
|
21 | 21 | - [Maintain Overall Health of the Repo](#maintain-overall-health-of-the-repo)
|
22 | 22 | - [Manage Roadmap](#manage-roadmap)
|
@@ -166,17 +166,6 @@ When necessary, be upfront that the time to review, approve, and implement a RFC
|
166 | 166 |
|
167 | 167 | Some examples using our initial and new RFC templates: #92, #94, #95, #991, #1226
|
168 | 168 |
|
169 |
| -### Run end to end tests |
170 |
| - |
171 |
| -In order to run end to end tests you need to install CDK CLI first and bootstrap your account with `cdk bootstrap` command. For additional details follow [documentation](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html). |
172 |
| - |
173 |
| -To run locally, export `AWS_PROFILE` environment variable and run `make e2e tests`. To run from GitHub Actions, use [run-e2e-tests workflow](https://github.com/awslabs/aws-lambda-powertools-python/actions/workflows/run-e2e-tests.yml) and pick the branch you want to run tests against. |
174 |
| - |
175 |
| -**NOTE**: E2E tests are run as part of each merge to `develop` branch. |
176 |
| - |
177 |
| -> **Q: What if there's an error?** |
178 |
| -To be agreed |
179 |
| - |
180 | 169 | ### Releasing a new version
|
181 | 170 |
|
182 | 171 | > TODO: This is an area we want to increase automation while keeping communication at human level.
|
@@ -220,7 +209,13 @@ The best part comes now. Replace the placeholder `[Human readable summary of cha
|
220 | 209 | Once you're happy, hit `Publish release`. This will kick off the [Publishing workflow](https://github.com/awslabs/aws-lambda-powertools-python/actions/workflows/publish.yml) and within a few minutes you should see the latest version in PyPi, and all issues labeled as `pending-release` will be notified.
|
221 | 210 |
|
222 | 211 | > TODO: Wait for @am29d new Lambda Layers pipeline work to complete, then add how Lambda Layers are published
|
| 212 | +### Run end to end tests |
| 213 | + |
| 214 | +In order to run end to end tests you need to install CDK CLI first and bootstrap your account with `cdk bootstrap` command. For additional details follow [documentation](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html). |
223 | 215 |
|
| 216 | +To run locally, export `AWS_PROFILE` environment variable and run `make e2e tests`. To run from GitHub Actions, use [run-e2e-tests workflow](https://github.com/awslabs/aws-lambda-powertools-python/actions/workflows/run-e2e-tests.yml) and pick the branch you want to run tests against. |
| 217 | + |
| 218 | +**NOTE**: E2E tests are run as part of each merge to `develop` branch. |
224 | 219 | ### Releasing a documentation hotfix
|
225 | 220 |
|
226 | 221 | You can rebuild the latest documentation without a full release via this [GitHub Actions Workflow](https://github.com/awslabs/aws-lambda-powertools-python/actions/workflows/rebuild_latest_docs.yml). Choose `Run workflow`, keep `develop` as the branch, and input the latest Powertools version available.
|
|
0 commit comments