You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For datefields with a start date/time and an end date/time, the test for And entity field ":field" should contain ":value" fails. The step definition checks for a value, but for these fields the value is an array instead of a scalar date string. Date fields with both a start and end date are retrieved as an array instead of as a scalar due to the unpredictability of entity_metadata_wrapper().
I've submitted a pull request with a potential fix: #10
The text was updated successfully, but these errors were encountered:
I've committed that code with the to-do you added:
* @todo : Update method to handle date fields with start and end dates
* The call to $wrapper->$field->value() returns either an array or a scalar
* because entity_metadata_wrapper() makes the date field values array
* unpredictable. When working with date fields that have both a start and
* end time, an array is returned instead of a scalar. If we want to test
* for start and end dates, we would want to use Behat syntax similar to
* "Then entity field ":field should contain "<start_date> - <end_date>".
* This method would need to be updated to handle that approach.
For datefields with a start date/time and an end date/time, the test for And entity field ":field" should contain ":value" fails. The step definition checks for a value, but for these fields the value is an array instead of a scalar date string. Date fields with both a start and end date are retrieved as an array instead of as a scalar due to the unpredictability of entity_metadata_wrapper().
I've submitted a pull request with a potential fix: #10
The text was updated successfully, but these errors were encountered: