Apart from unit testing itself, I want to be able to "preview" an entire path for a given subscriber or even better, a set of defined subscriber properties.
Since the "output" of an automation is chronological, show me the chronology! What happens on which day and at which time. If there is a split in potential paths, show me that along with which factors go into the decision and the potential paths the subscriber can follow.
The first version of this would be a read-only version of a workflow-type visual (similar to RM maybe) that's autogenerated from the spec. I could see versions that throw specific flags for common issues like unintended dead ends, a list of "exits" for the automation (where subscribers go when it's done), potential race conditions, and other common bugs.
Apart from unit testing itself, I want to be able to "preview" an entire path for a given subscriber or even better, a set of defined subscriber properties.
Since the "output" of an automation is chronological, show me the chronology! What happens on which day and at which time. If there is a split in potential paths, show me that along with which factors go into the decision and the potential paths the subscriber can follow.
The first version of this would be a read-only version of a workflow-type visual (similar to RM maybe) that's autogenerated from the spec. I could see versions that throw specific flags for common issues like unintended dead ends, a list of "exits" for the automation (where subscribers go when it's done), potential race conditions, and other common bugs.