Difficulties adding TAGS to test executions in CI Test Visibility

[MaximilianoAdaro]

Description

I am encountering difficulties with adding tags to test executions in Datadog CI Test Visibility. Despite following the available documentation and attempting various methods, the tags I specify do not seem to be applied to the test runs as expected. This issue is impacting our ability to effectively filter and manage test results based on custom criteria.

Expected Behaviour

After test execution, I expect to see the custom tags applied to each test run in Datadog CI Test Visibility, allowing for efficient filtering and management based on these tags. Apart from the ENV and SERVICE variables.

Environment

• dd-trace version: v4.30.0
• CI/CD tool used: GitHub Actions

Thank you for your assistance!

[MaximilianoAdaro]

@juan-fernandez could you please help me with this issue?

[juan-fernandez]

@juan-fernandez could you please help me with this issue?

hey @MaximilianoAdaro !

Could you give me details about what you're trying? What test framework you're using and how you're adding custom tags. As always, a small reproducible case would be awesome 😄

[MaximilianoAdaro]

Thank you for the quick response @juan-fernandez ! Here are the additional details:

Test Frameworks Used:

• Cypress
• Playwright

Method of Adding Custom Tags: I am adding custom tags by specifying them in the GitHub Actions environment variables, using the DD_TAGS alongside DD_ENV and DD_SERVICE, which are working as expected. My goal is to apply these custom tags to all test executions to enhance filtering capabilities in the Datadog dashboards.

Here is an example of how I define these environment variables in my GitHub Actions workflow:

env:
  DD_ENV: staging
  DD_SERVICE: my-service
  DD_TAGS: team:myteam,feature:myfeature

Expected Display in Dashboards: I expect that these custom tags (team:myteam, feature:myfeature) will appear alongside the automatically applied env and service tags in the Datadog CI Test Visibility dashboards. This should allow us to filter test executions based on these custom criteria directly from the dashboard interface.

Hope this clarifies my approach. Thank you for your help!

[MaximilianoAdaro]

Or probably with Node Labels? Let me try

[juan-fernandez]

that's weird because we test just that in https://github.com/DataDog/dd-trace-js/blob/master/integration-tests/cypress/cypress.spec.js#L292-L293 (both in cypress and playwright)

did you check for those tags at the test detail view? You need to go at the Other tags section:

You might just be missing the creation of the facet:

I've just tested this manually and I think it works as intended

[MaximilianoAdaro]

Got it, I haven't seen the Other tags tab, thank you so much Juan for the quick help!