Skip to content

test: align extending guide harness with runtime config#230

Open
ikenyal wants to merge 1 commit into
aws-devtools-labs:mainfrom
ikenyal:test/extending-guide-config-registry
Open

test: align extending guide harness with runtime config#230
ikenyal wants to merge 1 commit into
aws-devtools-labs:mainfrom
ikenyal:test/extending-guide-config-registry

Conversation

@ikenyal

@ikenyal ikenyal commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Problem

The BlocksBackend guide harness assumes the generated template contains exactly one Lambda. The config registry also creates Lambda-backed CDK custom resources, so the current assertion fails even when the Blocks backend is correct. The guide harnesses also use handler.addEnvironment() for resource identifiers, contrary to the current registerConfig() guidance.

Issue #, if available: N/A

Changes

  • Register the guide fixture resource identifiers through registerConfig().
  • Verify resource identifiers are included in the generated runtime config rather than direct Lambda environment variables.
  • Identify the Blocks handler by its production runtime environment instead of counting all Lambda resources.

Validation

  • Ran npm run build.
  • Ran npm run lint:deps.
  • Ran npx tsc --noEmit -p test-apps/extending-blocks-guide/tsconfig.json.
  • Ran npx tsc --noEmit -p test-apps/extending-blocks-guide-blocksbackend/tsconfig.json.
  • Ran npm run test:mock --workspace test-extending-blocks-guide.
  • Ran npm run test:synth --workspace test-extending-blocks-guide.
  • Ran npm run test:synth --workspace test-extending-blocks-guide-blocksbackend.

Checklist

  • PR description included
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ikenyal
ikenyal requested a review from a team as a code owner July 17, 2026 20:06
@changeset-bot

changeset-bot Bot commented Jul 17, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 9df04a7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant