a.log

Running "jshint:all" (jshint) task
>> 2 files lint free.

Running "exec:run_cucumber_tests" (exec) task
@dialog @receive_message
Feature: new message

  All valid messages
  should be captured in their raw form
  persisted
  and then denorm'd to all related services

  Why:
  - we can run sentiment models on user's text to evaluate their state of mind
  - in the future, we will likely get in the intent business ourselves.  having the raw data will be useful.
  - in any consumer analytics environment, hold on to ALL the data you can, for as LONG as you can.

  Rules:
  - the inbound message must containt a bot key (which kong decodes to org and botId) as well as p/pId

  @acceptance @valid_message_received
  Scenario: Received valid message from existing user for active dialog
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    And there are Dialog records as follows:
      | dialogKey     |
      | DIALOG_RECORD |
    When a valid new message is received for an existing user who is actively dialoging
    Then save the Message
    And update Dialog with Message
    And update Identity with Message
    And create a summarized Event for Message

  @acceptance @valid_message_received
  Scenario: Received valid message from existing user for new dialog
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    And there are Dialog records as follows:
      | dialogKey     |
      | DIALOG_RECORD |
    When a valid new message is received for an existing user starting a new dialog
    Then save the Message
    And update Dialog with Message
    And update Identity with Message
    And create a summarized Event for Message

  @acceptance @valid_message_received
  Scenario: Received valid message from new user
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    And there are Dialog records as follows:
      | dialogKey     |
      | DIALOG_RECORD |
    When a valid new message is received from a new user
    Then save the Message
    And update Dialog with Message
    And update Identity with Message
    And create a summarized Event for Message

@event @custom_algo
Feature: event triggers custom algo

  Every time an event is added
  check if there if a custom algo
  has been mapped to a mutated fieldz

  Why:
  - Modeling data can unleash its true potential
  - Reacting to data mutations in realtime creates numerous applications

  Rules:
  - Every event must be associated to a singular identity and session

  @acceptance @custom_algo @event @custom_algo
  Scenario Outline: Event field mutation triggers custom algo to run
    Given there are EventAlgo mappings as follows:
      | eventAlgoKey |
      | ALGO_MAP_REC |
    When an Event of type Order containing an orderValue is received
    Then the associated Algo should fire

@event @receive_event
Feature: new event

  All valid events
  should be captured,
  persisted,
  associated to a singular identity,
  and denormalized back to identity

  Why:
  - Events are the data that fuels our AI
  - We support an infinite range of types to try and 3-d model consumer behavior

  Rules:
  - Every event must be associated to a singular identity and session

  @acceptance @valid_event_received @for_testing
  Scenario: Valid event received
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    When a valid new Event is received
    Then save the Event
    And update Identity with Event

@identity @identity_post
Feature: alias identity

  One off condition.  Used when a known foreignId wants to be applied
  directly against a known tin (a.k.a. identityId).

  Why:
  - Cross linking match keys is one of the most important things we can do.

  Rules:
  - ...

  @acceptance
  Scenario: Alias called for a known identity
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    When an aliased foreignId is received
    Then review medal match when upserting an Identity tin record
    And push update to all medal Identity views
    And push impacted Identity rollup to related services

@identity @identity_get
Feature: Search identity

  With proper credentials
  return the proper view of an identity
  scoped to tin, bronze, gold, or silver

  Why:
  - tons of applications of how we could externalize what we know about an identity for 3rd party services

  Rules:
  - need to be very locked down to make sure we only give access to proper requests.  Fatal place for leaks.

  @acceptance @identity @identity_get
  Scenario Outline: Updare received for Identity "match" field
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    Given request contains botKey with right access level
    When an Identity search request by tinId for tin type is received
    Then return the requested Identity record(s) or an appropriate response

  @acceptance @identity @identity_get
  Scenario Outline: Updare received for Identity "match" field
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    Given request contains botKey with right access level
    When an Identity search request by email for bronze type is received
    Then return the requested Identity record(s) or an appropriate response

  @acceptance @identity @identity_get
  Scenario Outline: Updare received for Identity "match" field
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    Given request contains botKey with right access level
    When an Identity search request by browserId for silver type is received
    Then return the requested Identity record(s) or an appropriate response

  @acceptance @identity @identity_get
  Scenario Outline: Updare received for Identity "match" field
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    Given request contains botKey with right access level
    When an Identity search request by p + pid for gold type is received
    Then return the requested Identity record(s) or an appropriate response

  @acceptance @identity @identity_get
  Scenario Outline: Updare received for Identity "match" field
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    Given request contains botKey with right access level
    When an Identity search request by foreignId for undefined type is received
    Then return the requested Identity record(s) or an appropriate response

  @acceptance @identity @identity_get
  Scenario Outline: Updare received for Identity "match" field
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    Given request contains botKey with right access level
    When an Identity search request by phone for undefined type is received
    Then return the requested Identity record(s) or an appropriate response

@identity @identity_post
Feature: upsert identity

  Whenever data is received about a user
  whether from external source
  or from other internal process
  it should be upserted
  to the proper, medaled user / identity record

  Why:
  - What we know about users underpins the ability to respond to them

  Rules:
  - ...

  @acceptance
  Scenario: Update received for Identity "custom" field
    Given there are Identity records as follows:
      | identityKey   |
      | TIN_RECORD    |
      | BRONZE_RECORD |
      | GOLD_RECORD   |
    When an Identity update is received for a non-matching field
    Then upsert an Identity tin record
    And push update to all medal Identity views
    And push Identity rollup to related services

@makenu
Feature: universal browserId request

  Provide cross domain browser tracking
  store Id in utu.ai domain cookie
  retrieve or set on demand
  return Id to requestor
  to store in local domain

  Why:
  - lets us track browsers directly and cross domain synch

  Rules:
  - ...

  Components:
    WebSDK
    Makenu

  @acceptance
  Scenario: Request received to provide cookieId for given browser
    Given request originates from a taggable browser
    When request made for uTu.ai browserId
    Then the browser should be tagged for the utu.ai domain
    And uTu.ai cookieId should be returned

@makenu
Feature: conversant link tracker

  any link we present via a dialog
  we will shorten the link
  proxy any clicks that it gets
  and cookie the browser

  Why:
  - this is one way we can match a conversant key to a digital one
  - enables us to show digital behavior tied to a click

  Rules:
  - ...

  Components:
    Identity
    Makenu

  @acceptance
  Scenario: NOT first click
    When the dialog link is clicked
    Then the browser should be tagged for the utu.ai domain

  @acceptance
  Scenario: First click alias
    Given dialog rendered link has NOT been clicked
    And there is only one participant in the dialog
    When the dialog link is clicked
    Then the browser should be tagged for the utu.ai domain
    And the browserId should be aliased to the dialog identity

@makenu
Feature: success pixel tracker

  provide a success pixel to clients
  for conversion tracking
  on target sites or pages

  Why:
  - verify that a desired action took place post the dialog

  Rules:
  - ...

  Components:
    Makenu

  @acceptance
  Scenario: success pixel click
    Given the uTu success pixel has been deployed on a client site
    When the success pixel is clicked
    Then the browser should be tagged for the utu.ai domain

Warnings:

1) Background:
   Step: Given there are Identity records as follows: - features\dialog\post_message.feature:17
   Message:
     Undefined. Implement with the following snippet:

       this.Given(/^there are Identity records as follows:$/, function (table, callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

2) Background:
   Step: And there are Dialog records as follows: - features\dialog\post_message.feature:22
   Message:
     Undefined. Implement with the following snippet:

       this.Given(/^there are Dialog records as follows:$/, function (table, callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

3) Scenario: Received valid message from existing user for active dialog - features\dialog\post_message.feature:27
   Step: When a valid new message is received for an existing user who is actively dialoging - features\dialog\post_message.feature:28
   Message:
     Undefined. Implement with the following snippet:

       this.When(/^a valid new message is received for an existing user who is actively dialoging$/, function (callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

4) Scenario: Received valid message from existing user for active dialog - features\dialog\post_message.feature:27
   Step: Then save the Message - features\dialog\post_message.feature:29
   Message:
     Undefined. Implement with the following snippet:

       this.Then(/^save the Message$/, function (callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

5) Scenario: Received valid message from existing user for active dialog - features\dialog\post_message.feature:27
   Step: And update Dialog with Message - features\dialog\post_message.feature:30
   Message:
     Undefined. Implement with the following snippet:

       this.Then(/^update Dialog with Message$/, function (callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

6) Scenario: Received valid message from existing user for active dialog - features\dialog\post_message.feature:27
   Step: And update Identity with Message - features\dialog\post_message.feature:31
   Message:
     Undefined. Implement with the following snippet:

       this.Then(/^update Identity with Message$/, function (callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

7) Scenario: Received valid message from existing user for active dialog - features\dialog\post_message.feature:27
   Step: And create a summarized Event for Message - features\dialog\post_message.feature:32
   Message:
     Undefined. Implement with the following snippet:

       this.Then(/^create a summarized Event for Message$/, function (callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

8) Background:
   Step: Given there are Identity records as follows: - features\dialog\post_message.feature:17
   Message:
     Undefined. Implement with the following snippet:

       this.Given(/^there are Identity records as follows:$/, function (table, callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

9) Background:
   Step: And there are Dialog records as follows: - features\dialog\post_message.feature:22
   Message:
     Undefined. Implement with the following snippet:

       this.Given(/^there are Dialog records as follows:$/, function (table, callback) {
         // Write code here that turns the phrase above into concrete actions
         callback(null, 'pending');
       });

10) Scenario: Received valid message from existing user for new dialog - features\dialog\post_message.feature:35
    Step: When a valid new message is received for an existing user starting a new dialog - features\dialog\post_message.feature:36
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^a valid new message is received for an existing user starting a new dialog$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

11) Scenario: Received valid message from existing user for new dialog - features\dialog\post_message.feature:35
    Step: Then save the Message - features\dialog\post_message.feature:37
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^save the Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

12) Scenario: Received valid message from existing user for new dialog - features\dialog\post_message.feature:35
    Step: And update Dialog with Message - features\dialog\post_message.feature:38
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^update Dialog with Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

13) Scenario: Received valid message from existing user for new dialog - features\dialog\post_message.feature:35
    Step: And update Identity with Message - features\dialog\post_message.feature:39
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^update Identity with Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

14) Scenario: Received valid message from existing user for new dialog - features\dialog\post_message.feature:35
    Step: And create a summarized Event for Message - features\dialog\post_message.feature:40
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^create a summarized Event for Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

15) Background:
    Step: Given there are Identity records as follows: - features\dialog\post_message.feature:17
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

16) Background:
    Step: And there are Dialog records as follows: - features\dialog\post_message.feature:22
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Dialog records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

17) Scenario: Received valid message from new user - features\dialog\post_message.feature:43
    Step: When a valid new message is received from a new user - features\dialog\post_message.feature:44
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^a valid new message is received from a new user$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

18) Scenario: Received valid message from new user - features\dialog\post_message.feature:43
    Step: Then save the Message - features\dialog\post_message.feature:45
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^save the Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

19) Scenario: Received valid message from new user - features\dialog\post_message.feature:43
    Step: And update Dialog with Message - features\dialog\post_message.feature:46
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^update Dialog with Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

20) Scenario: Received valid message from new user - features\dialog\post_message.feature:43
    Step: And update Identity with Message - features\dialog\post_message.feature:47
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^update Identity with Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

21) Scenario: Received valid message from new user - features\dialog\post_message.feature:43
    Step: And create a summarized Event for Message - features\dialog\post_message.feature:48
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^create a summarized Event for Message$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

22) Background:
    Step: Given there are EventAlgo mappings as follows: - features\event\custom_algo.feature:15
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are EventAlgo mappings as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

23) Scenario: Event field mutation triggers custom algo to run - features\event\custom_algo.feature:26
    Step: When an Event of type Order containing an orderValue is received - features\event\custom_algo.feature:21
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^an Event of type (.*) containing an (.*) is received$/, function (eType, matchKey, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

24) Scenario: Event field mutation triggers custom algo to run - features\event\custom_algo.feature:26
    Step: Then the associated Algo should fire - features\event\custom_algo.feature:22
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^the associated Algo should fire$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

25) Background:
    Step: Given there are Identity records as follows: - features\event\post_event.feature:17
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

26) Scenario: Valid event received - features\event\post_event.feature:24
    Step: When a valid new Event is received - features\event\post_event.feature:25
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^a valid new Event is received$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

27) Scenario: Valid event received - features\event\post_event.feature:24
    Step: Then save the Event - features\event\post_event.feature:26
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^save the Event$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

28) Scenario: Valid event received - features\event\post_event.feature:24
    Step: And update Identity with Event - features\event\post_event.feature:27
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^update Identity with Event$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

29) Background:
    Step: Given there are Identity records as follows: - features\identity\alias_identity.feature:13
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

30) Background:
    Step: Given there are Identity records as follows: - features\identity\get_identity.feature:14
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

31) Background:
    Step: Given there are Identity records as follows: - features\identity\get_identity.feature:14
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

32) Background:
    Step: Given there are Identity records as follows: - features\identity\get_identity.feature:14
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

33) Background:
    Step: Given there are Identity records as follows: - features\identity\get_identity.feature:14
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

34) Background:
    Step: Given there are Identity records as follows: - features\identity\get_identity.feature:14
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

35) Background:
    Step: Given there are Identity records as follows: - features\identity\get_identity.feature:14
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

36) Background:
    Step: Given there are Identity records as follows: - features\identity\post_identity.feature:16
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there are Identity records as follows:$/, function (table, callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

37) Scenario: Request received to provide cookieId for given browser - features\makenu\browserId_makenu.feature:20
    Step: Given request originates from a taggable browser - features\makenu\browserId_makenu.feature:21
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^request originates from a taggable browser$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

38) Scenario: Request received to provide cookieId for given browser - features\makenu\browserId_makenu.feature:20
    Step: When request made for uTu.ai browserId - features\makenu\browserId_makenu.feature:22
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^request made for uTu\.ai browserId$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

39) Scenario: Request received to provide cookieId for given browser - features\makenu\browserId_makenu.feature:20
    Step: Then the browser should be tagged for the utu.ai domain - features\makenu\browserId_makenu.feature:23
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^the browser should be tagged for the utu\.ai domain$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

40) Scenario: Request received to provide cookieId for given browser - features\makenu\browserId_makenu.feature:20
    Step: And uTu.ai cookieId should be returned - features\makenu\browserId_makenu.feature:24
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^uTu\.ai cookieId should be returned$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

41) Scenario: NOT first click - features\makenu\click_track_makenu.feature:20
    Step: When the dialog link is clicked - features\makenu\click_track_makenu.feature:21
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^the dialog link is clicked$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

42) Scenario: NOT first click - features\makenu\click_track_makenu.feature:20
    Step: Then the browser should be tagged for the utu.ai domain - features\makenu\click_track_makenu.feature:22
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^the browser should be tagged for the utu\.ai domain$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

43) Scenario: First click alias - features\makenu\click_track_makenu.feature:25
    Step: Given dialog rendered link has NOT been clicked - features\makenu\click_track_makenu.feature:26
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^dialog rendered link has NOT been clicked$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

44) Scenario: First click alias - features\makenu\click_track_makenu.feature:25
    Step: And there is only one participant in the dialog - features\makenu\click_track_makenu.feature:27
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^there is only one participant in the dialog$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

45) Scenario: First click alias - features\makenu\click_track_makenu.feature:25
    Step: When the dialog link is clicked - features\makenu\click_track_makenu.feature:28
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^the dialog link is clicked$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

46) Scenario: First click alias - features\makenu\click_track_makenu.feature:25
    Step: Then the browser should be tagged for the utu.ai domain - features\makenu\click_track_makenu.feature:29
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^the browser should be tagged for the utu\.ai domain$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

47) Scenario: First click alias - features\makenu\click_track_makenu.feature:25
    Step: And the browserId should be aliased to the dialog identity - features\makenu\click_track_makenu.feature:30
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^the browserId should be aliased to the dialog identity$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

48) Scenario: success pixel click - features\makenu\success_pixel_makenu.feature:17
    Step: Given the uTu success pixel has been deployed on a client site - features\makenu\success_pixel_makenu.feature:18
    Message:
      Undefined. Implement with the following snippet:

        this.Given(/^the uTu success pixel has been deployed on a client site$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

49) Scenario: success pixel click - features\makenu\success_pixel_makenu.feature:17
    Step: When the success pixel is clicked - features\makenu\success_pixel_makenu.feature:19
    Message:
      Undefined. Implement with the following snippet:

        this.When(/^the success pixel is clicked$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

50) Scenario: success pixel click - features\makenu\success_pixel_makenu.feature:17
    Step: Then the browser should be tagged for the utu.ai domain - features\makenu\success_pixel_makenu.feature:20
    Message:
      Undefined. Implement with the following snippet:

        this.Then(/^the browser should be tagged for the utu\.ai domain$/, function (callback) {
          // Write code here that turns the phrase above into concrete actions
          callback(null, 'pending');
        });

17 scenarios (17 undefined)
76 steps (50 undefined, 26 skipped)
0m00.000s

Done.