Skip to content

Conversation

@gibiw
Copy link
Contributor

@gibiw gibiw commented Nov 3, 2025

  • Adjusted the duration values in the JUnit test cases from 0.05 seconds to 50.0 seconds to reflect accurate execution times.
  • Enhanced the test assertions to validate the duration of execution results, ensuring consistency with the updated values.

Note

Converts JUnit test case durations from seconds to milliseconds and updates tests to expect and assert the new values; also fixes range variable capture for test cases.

  • Parser (internal/parsers/junit/junit.go):
    • Set Execution.Duration to milliseconds: duration := testCase.Time * 1000 and use &duration.
    • Fix range variable capture by shadowing testCase inside the loop.
  • Tests (internal/parsers/junit/junit_test.go):
    • Update expected durations from 0.05 to 50.0.
    • Add assertions to verify Execution.Duration is set and equals expected.

Written by Cursor Bugbot for commit 6746f3a. This will update automatically on new commits. Configure here.

- Adjusted the duration values in the JUnit test cases from 0.05 seconds to 50.0 seconds to reflect accurate execution times.
- Enhanced the test assertions to validate the duration of execution results, ensuring consistency with the updated values.
@gibiw gibiw merged commit 463dbf0 into main Nov 3, 2025
6 checks passed
@gibiw gibiw deleted the fix/junit branch November 3, 2025 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants