Skip to content
This repository was archived by the owner on Sep 17, 2024. It is now read-only.
This repository was archived by the owner on Sep 17, 2024. It is now read-only.

Provide support for define output in BDD scenario  #1655

Closed
Closed
Provide support for define output in BDD scenario #1655
Labels
Team:AutomationLabel for the Observability productivity teamTeam:Obs-DCLabel for the Data Collection teamTestingarea:testAnything related to the Test automationimpact:highShort-term priority; add to current release, or definitely next.priority:highProduct teams are waiting on features to make progress on their roadmaprequested-by:Obs-DCsize:M1-5 daystriagedTriaged issues will end up in Backlog column in Robots GH Project
@ChrsMark

Description

@ChrsMark
ChrsMark
opened on Oct 14, 2021

It would be nice if we have a way to provide multiple outputs' support so as people that create scenarios can just define where the suite should check for events. Example:

Scenario: Logs collection from running pod
  Given "elastic-agent" is running with "logs generic"
   When "a pod" is deployed
   Then "elastic-agent" collects events with "kubernetes.pod.name:a-pod" found in "es index a"

cc: @mdelapenya

Metadata

Metadata

Assignees

No one assigned

    Labels

    Team:AutomationLabel for the Observability productivity teamTeam:Obs-DCLabel for the Data Collection teamTestingarea:testAnything related to the Test automationimpact:highShort-term priority; add to current release, or definitely next.priority:highProduct teams are waiting on features to make progress on their roadmaprequested-by:Obs-DCsize:M1-5 daystriagedTriaged issues will end up in Backlog column in Robots GH Project

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions