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
[mesheryctl] Increase code coverage in mesheryctl
upto 80%
#3988
Comments
This issue has been labeled with 'component/mesheryctl'. Note that after making changes you need to update it in the mesheryctl command tracker spreadsheet.
|
Hey @piyushsingariya I would like to work on this. |
mesheryctl
upto 80%
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. |
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. |
Hi @shikharvashistha, checking in on the this issue. Do you have progress to report, by chance? |
Thanks for asking @leecalcote . As of now I don't have any progress on this issue, but would like to continue with it if possible which I was unable to due to my offline exams schedule. |
Hi @leecalcote @piyushsingariya I would like to work on this issue. If someone else is working, I would like to collaborate with them. Thanks |
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. |
I am interested to contribute in this issue. Pl. give me permission. So, that I can check and try solve. |
@piyushsingariya @alphaX86 can I assist with this issue? I can start with |
@nishi6verma @pk-218, this is great. // @alphaX86 @hexxdump |
Hi @nishi6verma @pk-218, are you guys taking a look at it |
Thanks sir.
…On Tue, 30 Aug 2022, 11:40 pm Lee Calcote, ***@***.***> wrote:
@nishi6verma <https://github.com/nishi6verma> @pk-218
<https://github.com/pk-218>, this is great. // @alphaX86
<https://github.com/alphaX86> @hexxdump <https://github.com/hexxdump>
—
Reply to this email directly, view it on GitHub
<#3988 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZSUWWC4RR6FO7ACM2JKIOLV3ZFCTANCNFSM5C2OXBXQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, I am looking on it.
…On Tue, 21 Feb 2023, 1:51 am Swathi L, ***@***.***> wrote:
Hi @nishi6verma <https://github.com/nishi6verma> @pk-218
<https://github.com/pk-218>, are you guys taking a look at it
—
Reply to this email directly, view it on GitHub
<#3988 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZSUWWHYZYJ7XNZTW3Q2OR3WYPG5VANCNFSM5C2OXBXQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This is not a good news. Maybe I can help on this one. |
Making good progress here, @Aisuko 👏 |
@Freedisch you can write the new test cases for |
I'd like to suggest you split test cases into several PRs, it will be more effective for us merging them. |
Current Behavior
The current code coverage is less than 30% check here https://app.codecov.io/gh/meshery/meshery
Expected Behavior
Increase this code coverage up to 80%, this time!
Contributor Guides and Resources
The text was updated successfully, but these errors were encountered: