Testing published smart home action after updates

[lj-smarthome]

It seems once a smart home action is published, there's no way to test changes made to the action since smart home actions are not supported via Alpha / Beta deployments. So I'm wondering what's the expected flow / approach to test changes before publishing a new version.

1. Should I create a separate project and use that for testing the changes?

2. If so, how to generate the test suite results that can be accepted by the published action which is required when publishing a new version (note these two would have different project ids)?

In general the process to update a published smart home action is really confusing and I cannot find any clear guidelines on it. Please advise.

Thanks!

[GoogleDevForum · Accepted solution]

Thanks for reaching out!
Yes, in the Google Home Developer Console (GHDC), the process for testing an already launched (live) Smart Home action remains the same. To test changes, you will need to create a separate test project (Project B) in the console. From there, you can run the test suite on Project B, and once the tests are successful, you can submit your main project (Project A) for certification review. During the review, you will need to provide the test suite results from Project B.

For more detailed instructions on testing an approved integration and submitting certification for an integration update, please refer to our developer documentation here: Testing and Updating Certified Integrations.