Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RF v7.0 and Legacy output file format #180

Closed
damies13 opened this issue Mar 6, 2024 · 1 comment
Closed

RF v7.0 and Legacy output file format #180

damies13 opened this issue Mar 6, 2024 · 1 comment
Labels
Agent Issue Affects the Agent enhancement New feature or request
Milestone
v1.3.0

Comments

@damies13
Copy link
Owner

damies13 commented Mar 6, 2024

In robot framework V7.x the xml file output has changed from what it was in previous versions, see backwards incompatible changes

The timestamp format in output.xml has also been changed from the custom
YYYYMMDD HH:MM:SS.mmm format to ISO 8601_ compatible
YYYY-MM-DDTHH:MM:SS.mmmmmm. Using a standard format makes it
easier to process output.xml files, but this change also has big positive
performance effect.

We may be able to get away with this as we also need to create a new V3 listener when robot framework V7.x (Issue #67), so as part of the v3 Listner we use the new date format, but if not we may need to fall back and use Legacy output file format (--legacyoutput) when the RF version is >= 7

This is a placeholder issue in case we can't handle this in Issue #67 with the new V3 listener.
@damies13 damies13 added enhancement New feature or request Agent Issue Affects the Agent labels Mar 6, 2024
@damies13 damies13 added this to the v1.3.0 milestone Mar 6, 2024
@damies13 damies13 changed the title RF &.0 and Legacy output file format RF v7.0 and Legacy output file format Mar 6, 2024
damies13 added a commit that referenced this issue Mar 10, 2024
@damies13
Update version to Issue-#180-Legacy-File-Output
f14aa0e
damies13 added a commit that referenced this issue Mar 10, 2024
@damies13
This is all I thing we need to do for Issue #180, I expect this code …
44a05d9 
…may never get used?
damies13 added a commit that referenced this issue Mar 10, 2024
@damies13
This should be better,
b2a2145 
Seems the xml mode was broken in code for Issue #67 for this release
This should fix it again - Issue #180
that was a lucky catch
@damies13
Copy link
Owner Author

Confirmed this is working now, merging into release branch

damies13 added a commit that referenced this issue Mar 14, 2024
@damies13
Regression test for Issue #180
42b27b3
github-actions bot pushed a commit that referenced this issue Mar 14, 2024
Merge branch 'Test-Result-Reporter-macos-latest-3.12' into Issue-#180-…
6876973 
…Legacy-File-Output
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Agent Issue Affects the Agent enhancement New feature or request
Projects
None yet
Milestone
v1.3.0
Development

No branches or pull requests
1 participant
@damies13