Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Category SDK
MCP toolkit
Certify
Resources
Skip to main content
This topic describes how to test your Category Action add-on after you have completed the build and deployment steps in Create a Category Add-on Manually with the CLI.

Prerequisites

Before you test, make sure you have completed the following:

Run interface validation tests to validate your SPI implementation

You can test your deployed API endpoint directly to validate SPI contract compliance. Requests go directly to your endpoint and bypass Alexa. This validates that your endpoint responds correctly to SPI requests (correct schemas, required fields, proper error codes). Update the test-config.json file with your endpoint and test credentials. This file is included in the starter project:
  • Food Ordering—/action/food-ordering/test-suites/test-config.json
  • Home Services—/action/home-services/test-suites/test-config.json
  • Local Booking—/action/local-booking/test-suites/test-config.json
  • Restaurant Reservation—/action/restaurant-reservation/test-suites/test-config.json
  • Ticketing—/action/ticketing/test-suites/test-config.json
Use the following commands to run these tests:
The following test-config.json shows examples of the core and comprehensive test data, but not the full file for brevity.
FieldDescription
interfaceNameSPI category name (e.g., RestaurantReservation)
provider.endpointYour API endpoint to test against
provider.timeoutRequest timeout in milliseconds
provider.endpointTestCredentials.usernameBasic auth username
provider.endpointTestCredentials.passwordBasic auth password
testData.coreMinimum required test scenarios (happy path per operation). For details about the request data for each operation, see the SPI reference for your category:
testData.comprehensiveExtended scenarios (multi-step flows like create+update, create+cancel)

Test in the web simulator

After deployment, you can test your add-on using the web simulator on the Alexa developer console. The web simulator tests the full Alexa+ interaction in isolated mode. Alexa+ routes requests to your add-on without TLN (Topic Language Navigation) or arbitration. For details on using the web simulator, see Test in the Web Simulator.

Test on an Alexa device

You need an Alexa-enabled device to test on a device. An Echo Show is recommended for multimodal testing. You use the web simulator to configure an override to send requests to your device. For details, see Test with a device. On-device testing validates:
  • Voice interaction quality
  • Multimodal UI rendering (on Echo Show)
  • End-to-end latency

Test account linking and permissions

Do these steps if your add-on uses account linking.
  1. In Simulator or on device, trigger an action that requires authentication.
  2. Alexa prompts: “To continue, please link your account in the Alexa app”.
  3. Scan the QR code via Mobile App and complete the flow on Alexa+ Store.
  4. Return to Simulator/device and retry the action.
  5. Verify the operation succeeds with the linked account.

Success criteria

The add-on is considered successfully developed and deployed when all the following conditions are met:
  1. All unit tests pass, and the add-on is able to build successfully.
  2. You can use alexa-ai deploy to deploy successfully. This ensures both AWS deployment and Alexa deployment succeed.
  3. The core and comprehensive integration tests pass successfully on the deployed endpoint.
  4. You can successfully test the add-on in the web simulator.
  5. You can complete an end-to-end test on an Alexa device.
Last modified on July 16, 2026