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

feat: reimplement rserve route #813

Merged
merged 29 commits into from
Feb 18, 2025
Merged

feat: reimplement rserve route #813

merged 29 commits into from
Feb 18, 2025

Conversation

marikaris
Copy link
Collaborator

@marikaris marikaris commented Oct 25, 2024

how to test:

  • explain here what to do to test this (or point to unit tests)

todo:

  • updated docs in case of new feature
  • added tests => e2e test should work on both Rserve and Rock, might need additional profile

Sorry, something went wrong.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@marikaris marikaris marked this pull request as ready for review November 14, 2024 07:06
@marikaris
Copy link
Collaborator Author

Sonar is failing, but coverage has been increased a lot. The added in code, is mostly old code that we're reintroducing. This code doesn't have many tests. Mostly because the complexity of tests that would have to be written, writing those tests would take up more time than having them would ever grant us.

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
67.4% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

@marikaris marikaris changed the title POC: reimplement rserve route feat: reimplement rserve route Nov 15, 2024
@marikaris marikaris requested a review from mswertz November 26, 2024 13:49
Copy link
Member

@mswertz mswertz left a comment

Choose a reason for hiding this comment

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

Code looks good. Would like a quick chat for final acceptance.

Is it possible to reuse exact tests between Rock and Rserve using a parameter to run all test twice using either or? Maybe even a totally outside parameter via gradle. Or is this maybe we what I see.

@marikaris
Copy link
Collaborator Author

Code looks good. Would like a quick chat for final acceptance.

Is it possible to reuse exact tests between Rock and Rserve using a parameter to run all test twice using either or? Maybe even a totally outside parameter via gradle. Or is this maybe we what I see.

I think the rock code lacks in the amount of tests it has. I have reintroduced the tests we had for rserve and added a couple new tests. I have tested both paths using our releasetest, using both profiles (rserve/rock) and that test succeeds both ways.

@mswertz
Copy link
Member

mswertz commented Jan 7, 2025

we discussed: use e2e test and then run on both.
Will probably require a specific profile in the preview server.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Will add back in when molgenis/GCC#511 is done
@marikaris
Copy link
Collaborator Author

we discussed: use e2e test and then run on both. Will probably require a specific profile in the preview server.

Discussed during this meeting, e2e can now run on both profiles, but ci cannot handle it yet:
Outcome of local tests:

[[1]]
[1] "Running tests for profile [vanilla-xenon] took: 1.27586139837901"
 
[[2]]
[1] "Running tests for profile [donkey] took: 1.49913598299026"

Will add this into CI bit, when https://github.com/molgenis/GCC/issues/511 is done.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
67.4% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

@marikaris marikaris merged commit 0e9fae1 into master Feb 18, 2025
3 of 4 checks passed
@marikaris marikaris deleted the feat/#809-vanilla-rserve branch February 18, 2025 11:43
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.

None yet

3 participants