Feature: Run Elastic Agent e2e test on PRs

  Scenario:  A developer creates a PR
    When the PR has changes for Filebeat, Metricbeat, or the Elastic Agent
    Then a new Docker image for the Elastic Agent is build
    And the e2e tests are launched for the docker image of the PR

  Scenario:  A developer creates a PR
    When the PR has changes for Filebeat, Metricbeat, or the Elastic Agent
    And the PR has the label `skip-ci`
    And the e2e tests are launched for the docker image of the PR

  Scenario: A developer push changes to a PR
    When the PR has changes for Filebeat, Metricbeat, or the Elastic Agent
    Then a new Docker image for the Elastic Agent is build
    And the e2e tests are launched for the docker image of the PR

  Scenario:  A developer push changes to a PR
    When the PR has changes for Filebeat, Metricbeat, or the Elastic Agent
    And the PR has the label `skip-ci`
    And the e2e tests are launched for the docker image of the PR

  Scenario: A developer push changes to a PR
    When the PR has changes for Filebeat, Metricbeat, or the Elastic Agent
    Then a new Docker image for the Elastic Agent is build
    And the e2e tests are launched for the docker image of the PR

  Scenario:  A developer creates a PR
    When a developer put a comment `/test agent` on a PR
    Then a new Docker image for the Elastic Agent is build
    And the e2e tests are launched for the docker image of the PR

  Scenario:  A developer creates a PR
    When a developer trigger manually a job in Jenkins with the param `agent_e2e` enabled
    Then a new Docker image for the Elastic Agent is build
    And the e2e tests are launched for the docker image of the PR