QA/UAT environment for routing configuration testing
A
Andre Leal
There is no way to test Concierge routers and routing configurations in a staging environment before deploying changes to production. Configurations cannot be copied between workspaces, so any testing setup requires manually rebuilding routers from scratch. For teams managing 20+ advanced routers, this creates significant risk when making changes and adds substantial overhead to any testing or deployment process.
Chili Piper should provide a dedicated QA or UAT environment where router configurations can be tested under the same conditions as production, along with the ability to copy configurations between workspaces to reduce manual rebuild effort.
Without this, every routing change is a live risk. Teams either skip testing entirely or invest significant time recreating complex logic in a separate workspace, neither of which is acceptable at scale.
Taylor Jennings
Merged in a post:
Test a Distro flow with sample data before publishing to see which path a record would take
H
Herman Komashko
Ability to Test before Publish. LeanData allows us to enter a test data and “run” through the journey to see which path it will take so we can do testing before we publish the update to real live environment. I know that we can spin up copies of Chilli Piper journeys and test it on our lower-level environments, but this is not as easy as being able to do it all inside a single tool