test(debugger): validate probe creation in expression language tests

[watson]

Motivation

The test_expression_language_contextual_variables test was XPASS'ing for Node.js

Changes

Modified the test to validate the actual feature implementation instead of explicitly failing:

• Added assertion in _assert() to verify probes are successfully created before validation

The test now:

• For languages with method probe support: Creates probes, validates they emit correctly, and checks @return and @duration values
• For Node.js: Naturally fails when probes cannot be created with a clear error message: "Expected probes to be created for validation. Check if the language supports the required probe type for this test."

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added, removed or renamed?
  • Get a review from R&P team

[watson]

• test(debugger): validate probe creation in expression language tests #6129 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

CODEOWNERS have been resolved as:

tests/debugger/test_debugger_expression_language.py                     @DataDog/debugger @DataDog/system-tests-core

[nccatoni]

Ideally this test should check that the feature is implemented. I see that @tylfin created this test. Would it be possible to add such an assertion ?

[watson]

@nccatoni good point. I've updated the PR to do that now

[nccatoni]

Thank you for the changes. LGTM, you might also want a review from someone familiar with the feature