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

modifications for codecov report to generate #8478

Closed
wants to merge 1 commit into from

Conversation

ash-kamrip
Copy link

@ash-kamrip ash-kamrip commented Aug 15, 2023

Notes for Reviewers

This PR fixes #7805

Hi , I've tried to update some of the golden files and commented out a few tests that needs modification , this PR should fix the current unit tests so that we can get updated code coverage.

P.S i am not able to fix any of the integration test so those will def fail

Signed commits

  • Yes, I signed my commits.

@github-actions github-actions bot added area/docs Documentation update needed component/mesheryctl CLI for Meshery labels Aug 15, 2023
@github-actions
Copy link

github-actions bot commented Aug 15, 2023

@welcome
Copy link

welcome bot commented Aug 15, 2023

Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, you can find updates in the #github-notifications channel in the community Slack.
Be sure to double-check that you have signed your commits. Here are instructions for making signing an implicit activity while performing a commit.

@l5io
Copy link
Collaborator

l5io commented Aug 15, 2023

@codecov
Copy link

codecov bot commented Aug 15, 2023

Codecov Report

Patch coverage has no change and project coverage change: +5.47% 🎉

Comparison is base (4e224bf) 5.17% compared to head (da23dd5) 10.64%.
Report is 167 commits behind head on master.

❗ Current head da23dd5 differs from pull request most recent head 318648b. Consider uploading reports for the commit 318648b to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #8478      +/-   ##
==========================================
+ Coverage    5.17%   10.64%   +5.47%     
==========================================
  Files         124      124              
  Lines       17771    17920     +149     
==========================================
+ Hits          919     1907     +988     
+ Misses      16680    15701     -979     
- Partials      172      312     +140     
Flag Coverage Δ
gointegrationtests ?
unittests 10.64% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
mesheryctl/internal/cli/root/filter/delete.go 43.24% <ø> (+43.24%) ⬆️
server/handlers/component_handler.go 0.00% <0.00%> (ø)
server/handlers/connections_handlers.go 0.00% <0.00%> (ø)
server/handlers/error.go 0.00% <0.00%> (ø)
server/handlers/mesh_ops_handlers.go 0.74% <0.00%> (-0.01%) ⬇️
server/handlers/relationship_handlers.go 0.00% <0.00%> (ø)
server/handlers/user_handler.go 0.00% <0.00%> (ø)
server/helpers/adapters_tracker.go 0.00% <0.00%> (ø)
server/meshes/meshops.pb.go 2.96% <0.00%> (-0.03%) ⬇️
server/meshes/meshops_grpc.pb.go 0.00% <0.00%> (ø)
... and 1 more

... and 48 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Signed-off-by: adhanaAshu <ashu.adhana@gmail.com>
@l5io
Copy link
Collaborator

l5io commented Aug 15, 2023

@l5io
Copy link
Collaborator

l5io commented Aug 15, 2023

Copy link
Member

@Philip-21 Philip-21 left a comment

Choose a reason for hiding this comment

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

@ash-kamrip alot of changes here, the code coverage rate currently seems to increase to 19%
also when you ran these test that you changed how were you able to make these outputs generated , from the golden files most of the outputs are not generated you removed them

@Philip-21
Copy link
Member

Philip-21 commented Aug 15, 2023

@ash-kamrip i have dropped some comments here , please you can give a brief description of what you implemented so we can know where we are headed at. Incase I want to work on some other unit tests I want to follow your approach but i need to understand why certain things were implemented

@Philip-21
Copy link
Member

there seems to be an issue with the Error codes please check it out

@Philip-21
Copy link
Member

@ash-kamrip the integration tests are failing

@vishalvivekm
Copy link
Member

@ash-kamrip Let's discuss this on Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

@ash-kamrip ash-kamrip closed this Aug 16, 2023
@ash-kamrip ash-kamrip deleted the unitest-coverage branch August 16, 2023 15:24
@ash-kamrip ash-kamrip restored the unitest-coverage branch August 16, 2023 15:31
@ash-kamrip ash-kamrip reopened this Aug 16, 2023
@l5io
Copy link
Collaborator

l5io commented Aug 16, 2023

@github-actions github-actions bot added the area/ci Continuous Integration label Aug 16, 2023
@l5io
Copy link
Collaborator

l5io commented Aug 16, 2023

@l5io
Copy link
Collaborator

l5io commented Aug 16, 2023

@suhail34
Copy link
Contributor

It would be great if we can focus more on how to make failing test pass rather than just making failing workflow to pass

Copy link
Contributor

@suhail34 suhail34 left a comment

Choose a reason for hiding this comment

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

Please remove the changes you made to error-code-updates.yaml it isn't needed as it is not a private repo that it would require github access token to checkout

@ash-kamrip
Copy link
Author

Oopsies will remove them ! my bad wanted to commit to the other branch

@l5io
Copy link
Collaborator

l5io commented Aug 16, 2023

@l5io
Copy link
Collaborator

l5io commented Aug 16, 2023

@stale
Copy link

stale bot commented Sep 26, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Sep 26, 2023
@stale
Copy link

stale bot commented Oct 6, 2023

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

@stale stale bot closed this Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Documentation update needed component/mesheryctl CLI for Meshery issue/stale Issue has not had any activity for an extended period of time
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI] Improve the CI and make sure it is useful for PR review
5 participants