Web Cog - v0.5.0

New Features

• For users running v0.9.0+ of the Crank CLI, all steps will now include extra data on failure or error outcomes to aid in debugging/diagnosis. [#84]

Installation

# Install this version
$ crank cog:install automatoninc/web:0.5.0

# Install the latest version
$ crank cog:install automatoninc/web

Thanks to Contributors

• @saludangelito 💻
• @roanlibelo ⚠️

Web Cog - v0.4.0

New Features

Check a page's Lighthouse performance score (Google PageSpeed Insight equivalent) [#55]

- step: When I navigate to https://example.com
- step: Then the desktop Lighthouse performance score should be 50 or higher

Check that Pardot tracking loads [#63]

- step: When I navigate to http://example.com
- step: Then the tracking code for pardot account 4567 and campaign 9876 should have loaded

Check that the LinkedIn Insight tag fired [#57]

- step: When I navigate to https://example.com
- step: Then the LinkedIn Insight tag for partner id 12345 should have fired

Check that the LinkedIn Conversion Pixel fired [#58]

- step: Given I navigate to https://example.com
- step: When I click the page element a.primary-cta
- step: Then the LinkedIn conversion pixel for partner id 12345 should have fired

Check that a Google Floodlight tag fired [#64]

- step: When I navigate to https://example.com
- step: Then a floodlight tag should have fired for advertiser 6789, group {{group.name}}, and activity {{activity.tag}}
  data:
    cMethod: Optional conversion method (one of standard, unique, or per session)
    withVariables:
      u8: Value of custom variable 8 (any variable can be optionally specified)

Check for a specific network request [#65]

- step: When I navigate to https://example.com
- step: Then there should be 1 matching network requests? for https://ads.example.com
  data:
    pathContains: /track
    withParameters:
      queryParam: Param Value
      orBodyJsonProperty: Value

Maintenance

• Fixed a bug where meta tag check attempts against non-existent tags would cause a test scenario to timeout [#77]

Installation

# Install this version
$ crank cog:install automatoninc/web:0.4.0

# Install the latest version
$ crank cog:install automatoninc/web

Thanks to Contributors

• @amcpanaligan 💻
• @saludangelito 💻
• @roanlibelo ⚠️

Web Cog - v0.3.1

Bug Fixes

• Prior to this release, the Click an element on a page and Submit a form by clicking a button steps would fail when the element being interacted with was obscured by another (most commonly a Cookie Compliance banner). As of v0.3.1, the behavior of these steps matches the behavior of the Fill out a form field step, which allowed interaction with obscured elements. [#48, #54]

Installation

# Install this version
$ crank cog:install automatoninc/web:0.3.1

# Install the latest version
$ crank cog:install automatoninc/web

Web Cog - v0.3.0

New Features

New step to click on a page element [#9 #13]

- step: Click the page element {{element.domQuerySelector}}

New step to scroll to a certain percentage depth of the page [#8, #15]

- step: Scroll to {{page.depth}}% of the page 

New step to focus the browser on a specific iframe [#44]

- step: Focus on the {{iframe.domQuerySelector}} frame

New step to validate that Marketo Munchkin tracker fires as expected [#7, #17]

- step: The tracking code for munchkin account id {{munchkin.account.id}} should load

New step to validate that Google Analytics tracked a pageview [#10, #18]

- step: Google Analytics should have tracked a pageview for tracking id {{ga.measurement.id}}
  data:
    withParameters:
      cd1: optional custom parameter checks here

New step to validate that Google Analytics tracked a custom event [#11, #23]

- step: Google Analytics should have tracked an event with category {{event.category}} and action {{event.action}} for tracking id {{ga.measurement.id}}
  data:
    withParameters:
      cd1: optional custom parameter checks here

Maintenance

• Improved support for <input type="radio" /> inputs [#45]
• Ensures tests are performed using a viewport that aligns more closely with modern desktops [#19]
• Sets user agent to a string less likely to be blocked by aggressive bot detection configurations [#33]
• Client code is now organized into mixins to support future vendor-specific steps [#12]

Installation

# Install this version
$ crank cog:install automatoninc/hubspot:0.2.0

# Install the latest version
$ crank cog:install automatoninc/hubspot

Thanks to Contributors

• @amcpanaligan 💻
• @saludangelito 💻
• @roanlibelo ⚠️

Web Cog - v0.2.0

New Features

New step to check last navigation response details [#3]

- step: Then the {{response.detail}} of the current page should {{comparison.operator}} {{test.expectation}}

Where:

• {{response.detail}} is one of status, text, or url
• {{comparison.operator}} is one of contain, not contain or be

New step to check meta tag values on current page [#4]

- step: Then the {{meta.name}} meta tag on the current page should {{comparison.operator}} {{test.expectation}}

Where:

• {{meta.name}} corresponds to the name or property attribute of a <meta> tag, or just title for the <title> tag
• {{comparison.operator}} is one of be, contain, not contain, not be longer than, or exist
• If the comparison operator is exist, then {{text.expectation}} may be omitted.

Installation

# Install this version
$ crank cog:install automatoninc/web:0.2.0

# Install the latest version
$ crank cog:install automatoninc/web

Web Cog - v0.1.3

Bug Fixes

• Prior to this release, the Fill out a form field step would pass when filling out hidden text fields, even though the text field was not actually filled out. This step now attempts to manually set a value on a hidden field before resulting in an error. [#2]

Installation

# Install this version
$ crank cog:install automatoninc/web:0.1.3

# Install the latest version
$ crank cog:install automatoninc/web