All new Partner Solutions and updates to existing Partner Solutions are tested and validated by our CI/CD system.

Partner Solutions enter the testing pipeline through GitHub. The GitHub repository for your Partner Solution is programmatically created in accordance with AWS standards via the GitHub API. The automated workflow includes these steps:

  1. You commit your changes to the develop branch of your GitHub repository.
  2. The Partner Solution CI system tests the changes by using a tool called TaskCat. For information about TaskCat, including how to use it for your own projects, refer to the Automated testing with TaskCat section of this guide.
  3. If the validation completes successfully, the CI system merges your changes into the main branch of the GitHub repository.
  4. When you’re ready to publish, the CI system performs another validation pass, creates an S3 bucket, and uploads the Partner Solution templates and scripts into that bucket. Your changes are now live.
Don’t rely on automated testing alone. For information about testing and debugging your code, refer to the Test your CloudFormation-based Partner Solution section of this guide.