@ows_metadata
Feature: XML Echoboom
  In order to ensure echoboom XML is valid

  Scenario: Has a item node
    Given I have a film XML for dms 731 for upc 884385029036
    Then the XML should have a item tag

  Scenario: Has a guid with 884385029036
    Given I have a film XML for dms 731 for upc 884385029036
    Then The XML should have a node guid with 884385029036 tag

  Scenario: Has a title with Shades of Winter: Between
    Given I have a film XML for dms 731 for upc 884385029036
    Then The XML should have a node title with World of Darkness:  Terror of The Under Hell tag

  Scenario: Has a programmingtype with full movie tag
    Given I have a film XML for dms 731 for upc 884385029036
    Then The XML should have a node programmingtype with full movie tag

  Scenario: Has a sub-category with Extreme Sports Compilations
    Given I have a film XML for dms 731 for upc 884385029036
    Then The XML should have a node sub-category with Movies tag

  Scenario: Has a genre with Documentaries
    Given I have a film XML for dms 731 for upc 884385029036
    Then The XML should have a node genre with Children & Family tag

  Scenario: Has a sub-genre with Sports Documentaries
    Given I have a film XML for dms 731 for upc 884385029036
    Then The XML should have a node sub-genre with Kids’ TV tag

  Scenario: Has a captions node
    Given I have a film XML for dms 731 for upc 884385029036
    Then the XML should have a captions tag

  Scenario: Has a content node
    Given I have a film XML for dms 731 for upc 884385029036
    Then the XML should have a content tag

  Scenario: Has a include node
    Given I have a film XML for dms 731 for upc 884385029036
    Then the XML should have a include tag