This idea was mentioned by @jurgenhaas at a team meeting:
A user should be able to perform a dry-run on existing ECA instances, meaning that the dry-run would just go through all the conditions but would not apply the changes made within actions being executed. This might be thought as an approach similar to an rsync dry-run.
Providing the ability to perform dry-runs will help on investigating possible problems within given ECA configs. It could also be used as a "try it out and see if it works" feature for end users.
We may need to consider if we want to support both "dummy" content entities and/or real existing records.
Postponed
2.1
User interface
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
