question

I'm looking for answer to this question as well. The process.env variable provides a lot of information, but nothing stood out as a test/prod indicator.

In the absence of a better solution, I am currently using a config file to set the environment. That way, when I submit for release, I only have to change "qa" to "prod" in one place before the submission. It's a dangerous solution, but seems to be the only option that allows us to straddle two separate skills and keep them cloned. Along with this approach, we are going the route that it seems like other developers are going with Alexa-hosted skills by having a separate testing and production skill. With the separate skills, we can just set our config file to "qa" or "prod" independently. I sure wish process.env exposed something that told us what environment or git branch the app is associated with. Would make life much easier.