Code Coverage : Create Tests for OrganizatioEvents.tsx

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/screens/OrganizationEvents/OrganizationEvents.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/screens/OrganizationEvents/OrganizationEvents.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.

hello 👋🏽 I would like to work on this.

hello @palisadoes i would like to work on this issue .could you please assign this task to me

@VenomFate-619 Are you still working on this?

I'm on it. But due to some issue I am unable to access organization event page on frontend. Many people have reported that issue on slack. So , this issue is an blockage for me , that why's I am unable to do that.

@VenomFate-619 Is there an issue created for the organization access difficulty? Please add the link here if it exists

I want to work on this issue. Please allow me to work on it.

I'm going to reassign this to @shivakr07. This issue has been open for some time without action.

@shivakr07 Any progress ?

Unassigned due to inactivity.

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.

Hey! I would love to give a shot at this issue. Can I be assigned, please?

I just saw GH-527 with @beingnoble03. Linking the PR to this issue would be great.

Do let me know if I may help with this, anyways :v:

Thanks @bigBrain1901! @palisadoes we'll let you know if there are any other duplicate issues. I think this one can be safely closed, it's a duplicate for #482.