Code Coverage: Create tests for src/components/CheckIn/CheckInWrapper.tsx

[palisadoes]

We will need unittests done for all methods, classes and functions found in this file.

Any widgets, components, modals referenced in this file must also have unittests done

PR Acceptance Criteria

• When complete this file must show at least 100% coverage when merged into the code base.
• The current code coverage for the file can be found here
• The PR will show a report for the code coverage for the file you have added. You can use that as a guide
• Please coordinate issue assignment and PR reviews with the contributors listed in this issue Student Internship Programs talawa#359

[duplixx]

hey @palisadoes , can you assign me this issue i wanna work on it
Thanks !!

[noman2002]

@duplixx You already have 2 issues in your name. Please get the PRs merged first, then I'll assign more. As per the rules only 2 issues can be assigned at once.

[duplixx]

hey @noman2002 , you can assign me this as my previous PR is merged now!!

[github-actions]

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

[lakshz]

Please assign this to me.

[noman2002]

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[adi790uu]

Hey @noman2002 I want to work on this issue!

[punitkr03]

Hey ,I want to work on this, please assign me.

[noman2002]

@adi790uu You already have 2 issues assigned to you.

[punitkr03]

Het @noman2002, I just found this comment in the test file. If the memory leak is fixed I can uncomment it. Suggestions?

[punitkr03]

I tried uncommenting it and the memory leak is still there. I will try to fix that as well.
Update: The issue is with @mui/x-data-grid. However, this issue is fixed in recent release of the package. I tried updating the package but it broke other things. What can be my next steps?

[punitkr03]

@noman2002 Hey, I have been waiting for your input.

[noman2002]

@aashimawadhwa @EshaanAgg Please answer his queries.

[EshaanAgg]

@punitkr03 I had left the comment to show what the prospective test must look like after the memory leak in broken. The test is not full proof as it hasn't been tested in the wild due to the aforementioned leak.

• Please first make sure that the memory leak is indeed fixed.
• If it is so, then you can try writing the tests for the same from a fresh perspective, and see how 100% coverage can be achieved. Use the provided test as reference, and not as a strict format.

[github-actions]

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

[palisadoes]

Unassigning due to inactivity and no pull request

[DIWAKARKASHYAP]

@noman2002 I have read the issue. I can solve it. Could you please assign this to me?

[DIWAKARKASHYAP]

Hello @noman2002 @palisadoes
I am facing an issue. When I run the Talawa-admin develop branch, this happens

talawa.mp4

but the main branch is working fine

[punitkr03]

@DIWAKARKASHYAP You have to run talawa-api either in docker container or manually. So fork talawa-api repo and set it up too. I will recommend using docker.

[DIWAKARKASHYAP]

I am using docker for talawa api ,

page is automatically reload

[punitkr03]

Did u set your NODE_ENV in .env file to development?

[DIWAKARKASHYAP]

yes all variable are setup , the main branch is working properly but develop branch give me this problem

[github-actions]

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

[palisadoes]

Removing assignment due to inactivity

[ashutuptiwari]

@palisadoes I'd like to work on this :D

[ashutuptiwari]

@Cioppolo14
PS: the memory leak is still not fixed

[Cioppolo14]

@ashutuptiwari Please fix the memory leak as part of this issue.

[ashutuptiwari]

Alright, can you please describe the leak @Cioppolo14

[palisadoes]

Alright, can you please describe the leak @Cioppolo14

If you have discovered that it's still there, you should be able to find it and fix it.

[github-actions]

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

[palisadoes]

Unassigning due to inactivity and/or no submitted PR. 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.

[Anvita0305]

Hello, @noman2002 @Cioppolo14 I would like to work on this issue. Can you please assign it to me? Thanks!