#redhen

I am just getting started testing a new Redhen CRM instance using Behat. I'm using the Drupal API. While writing tests is coming along nicely, I don't see how to write tests that target the CRM's native objects, contacts, orgs, and lists.

The only connection that has turned up between Behat and Redhen from searches is three extremely basic tests that were the result of a sprint on Redhen Raiser. These tests don't target anything unique about the CRM but test basic things like logging in to Drupal.

I would like to be able to write a test along the lines of:

Given individuals:

I’ve been doing membership sites for some years in Drupal 6, using a rather messy combination of CCK fields, User Role plus Ubercart Expiry Date to track membership. With the upgrade to Drupal 7 I hunted for a better solution and eventually decided upon the RedHen suite of modules. They provide lightweight CRM functionality, integration with membership and registration systems, and good compatibility with Commerce.

Has anyone any experience with integrating or using redhen for a front-end to salesforce particularly when that salesforce org is using the non-profit starter pack (NPSP)

From reading the documentation I understand the salesforce module and redhen share the same parents but I'm less sure about the how,why & when you would mix Redhen, salesforce module & salesforce

We've just made the decision to go with Redhen instead of Party CRM as a company. So I thought it would be appropriate to start sharing ideas, drafts and notes here :-)

One of the UX things I've been thinking about for quite some time is how to enable users to do powerful profiling and segmentation without confusing interfaces or too many interface options.

An idea that seems to work quite well is to use the concept of "baskets" like in a web shop. You have to see the "basket" as a sort of extension of views bulk operations.