talawa-admin icon indicating copy to clipboard operation
talawa-admin copied to clipboard

Published 20 hours ago • verified publisher icon PalisadoesFoundation

Code Coverage: Create tests for AddOnEntry.tsx

Open palisadoes opened this issue 2 years ago • 1 comments

The Talawa-Admin code base needs to be 100% reliable. This means we need to have 100% test code coverage.

Tests need to be written for file src/components/AddOn/core/AddOnEntry/AddOnEntry.tsx

  • When complete, all methods, classes and/or functions in the file will need to be tested.
  • These tests must be placed in a single file with the name src/components/AddOn/core/AddOnEntry/AddOnEntry.test.tsx. You may need to create the appropriate directory structure to do this.

IMPORTANT:

Please refer to the parent issue on how to implement these tests correctly:

  • #241

PR Acceptance Criteria

  • When complete this file must show 100% coverage when merged into the code base. This will be clearly visible when you submit your PR.
  • The current code coverage for the file can be found here. If the file isn't found in this directory, or there is a 404 error, then tests have not been created.
  • Create a code coverage account for your repo's preferred branch to generate the values when you do your commits for that branch to your repo.
    • NOTE: Make sure you select the correct branch when you do the setup, or else the reporting will fail. You must also create a CODECOV GitHub secret for your repo as part of the process.
  • The PR will show a report for the code coverage for the file you have added. You can also use that as a guide.

palisadoes avatar Mar 02 '22 22:03 palisadoes

I'd like to work on this issue.

ShwetKhatri2001 avatar Mar 19 '22 11:03 ShwetKhatri2001

@palisadoes I would like to work on this issue, please assign it to me.

aashimawadhwa avatar Jan 19 '23 18:01 aashimawadhwa

Hi if no one is working on this then i would love to work on this.

ayushbhaimehta avatar Feb 08 '23 13:02 ayushbhaimehta

@ayushbhaimehta Any update ?

noman2002 avatar Feb 18 '23 19:02 noman2002

I actually forgot to unassign myself. I got occupied at other things.

ayushbhaimehta avatar Feb 19 '23 04:02 ayushbhaimehta

Hi @palisadoes @noman2002 I'd like to work on this issue. Can this issue be assigned to me?

Sukriti-m avatar Mar 05 '23 07:03 Sukriti-m

Hey! If this is available. Please assign me.

lata-11 avatar Mar 09 '23 17:03 lata-11

@lata-11 If the issue has already been assigned, please don't ask to be assigned. We want everyone to get a chance.

palisadoes avatar Mar 09 '23 17:03 palisadoes

This issue did not get any activity in the past 10 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

github-actions[bot] avatar Mar 20 '23 00:03 github-actions[bot]

Unassigning due to inactivity others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

palisadoes avatar Mar 20 '23 04:03 palisadoes

Unassigning due to inactivity others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

I apologise for the delay in submitting a PR. I was facing some errors in the installation of project but now it is fixed. I will submit my final PR by tomorrow. Kindly reassign this issue to me.

Sukriti-m avatar Mar 20 '23 04:03 Sukriti-m