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.

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

Enable Junit reports for Scalatest #3756

Merged
merged 17 commits into from
Oct 7, 2022
Merged

Conversation

4e6
Copy link
Contributor

@4e6 4e6 commented Oct 4, 2022

[ci no changelog needed]

Pull Request Description

Changelog

  • enable graphical test results for Scalatest tests like we have for stdlib tests

Important Notes

Sometimes the report is created on a different workflow, like here. Turned out it is a known issue in GitHub Actions https://github.com/orgs/community/discussions/24616

Checklist

Please include the following checklist in your PR:

  • The documentation has been updated if necessary.
  • All code conforms to the
    Scala,
    Java,
    and
    Rust
    style guides.
  • All code has been tested:
    • Unit tests have been written where possible.
    • If GUI codebase was changed: Enso GUI was tested when built using BOTH
      ./run ide build and ./run ide watch.

@4e6 4e6 self-assigned this Oct 4, 2022
@4e6 4e6 changed the title Enale Junit reports for Scalatest Enable Junit reports for Scalatest Oct 4, 2022
@4e6 4e6 force-pushed the wip/db/scalatest-junit-report branch 4 times, most recently from a732fc3 to 6bfe4b5 Compare October 5, 2022 13:32
@4e6 4e6 force-pushed the wip/db/scalatest-junit-report branch from 99d9131 to d579b00 Compare October 6, 2022 08:39
@4e6 4e6 marked this pull request as ready for review October 6, 2022 12:14
@4e6 4e6 requested a review from mwu-tow October 6, 2022 12:14
Copy link
Contributor

@mwu-tow mwu-tow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The workflow is generated by the build script, I'll update it later, separately.
In the meantime, this can go as-is.

Copy link
Contributor

@hubertp hubertp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if build.sbt compiles, I'm good with it

Seq(Tests.Argument("-oI")) ++
sys.env
.get("ENSO_TEST_JUNIT_DIR")
.map { junitDir =>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This compiles? I would expect Seq vs Option mismatch

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's because, Option is an Iterable, and can be accepted by ++ method

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@4e6 4e6 added the CI: Ready to merge This PR is eligible for automatic merge label Oct 6, 2022
@4e6 4e6 removed the CI: Ready to merge This PR is eligible for automatic merge label Oct 6, 2022
@4e6 4e6 added the CI: Ready to merge This PR is eligible for automatic merge label Oct 6, 2022
@mergify mergify bot merged commit f168cd0 into develop Oct 7, 2022
@mergify mergify bot deleted the wip/db/scalatest-junit-report branch October 7, 2022 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants