OpenHands / OpenHands/software-agent-sdk
Behavior test run posts comment with "Integration Tests Results" title
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 539
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 137
Description
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.
Contributor 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.
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.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100