Behavior test run posts comment with "Integration Tests Results" title

Open Beginner friendly

#4,944 opened on Sep 10, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 88/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: python
Domain: testing

Research direction

Start in tests/integration/utils/generate_markdown_report.py at generate_markdown_report and inspect how the consolidated results expose each instance's test_type. Update the generated title so behavior runs use “Behavior Tests Results” while regular integration runs retain “Integration Tests Results”; done means the two result comments are distinguishable.

Written by the indexing model from the issue text.

Description

bug priority:low testing

Problem

When a release PR is tagged with the behavior-test label, the Run Integration Tests workflow runs the behavior test suite and posts a results comment on the PR. However, that comment uses the title:

🧪 Integration Tests Results

…which is the same title used by the regular integration test run. This makes it hard to tell the two result comments apart on a PR.

For context, see this example comment from a behavior-test run: https://github.com/OpenHands/software-agent-sdk/pull/4942#issuecomment-5624939445 (the linked run is https://github.com/OpenHands/software-agent-sdk/actions/runs/34524458141).

The corresponding release checkpoints are:

Integration tests pass (tagged with integration-test)
Behavior tests pass (tagged with behavior-test)
Example tests pass (tagged with test-examples)

Expected behavior

When the run is a behavior test run, the results comment should be titled:

🧪 Behavior Tests Results

Regular integration test runs should keep the existing # 🧪 Integration Tests Results title.

Root cause

The title is hardcoded as # 🧪 Integration Tests Results in tests/integration/utils/generate_markdown_report.py (generate_markdown_report), so it is identical regardless of which test suite actually ran. The consolidated results already carry per-instance test_type (integration / behavior / condenser), so the correct title can be derived from the data.

This issue was created by an AI agent (OpenHands) on behalf of @juanmichelini.

Dominant language: Python
Stars: 1.1k
Forks: 542
Avg merge: 1d 22h
Merged PRs (30d): 139

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
[pcied] Honour PCIE_DETACH_INFO on platforms that are not smartswitches Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

sonic-net/sonic-platform-daemons#900 · Opened Sep 21, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026

More Python issues