[Bug Report] Performing comprehensive testing of all mutations and debugging any non-functional mutations.

[Ayush0Chaudhary]

Describe the bug
Currently some services are failing. For example chatservice, direct message and some unidentified. They are failing because of talawa-api shift to non-nested schema. Many are unidentified too.

We should make our app at-least functional

We should solve these bugs before the GSoC period starts so that the selected people can focus on there ideas.

I'll make a task list of all the errors and correct them accordingly.

Current Failing services list

• DirectChat Service
• Fetch Comment Services
• Create Comment Services
• User Config
• Membership Request
• Event Fetch
• Logout service

Additional details

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship #359

[Ayush0Chaudhary]

@palisadoes @noman2002

[Ayush0Chaudhary]

I'll do the thorough testing and update the list

[literalEval]

This is a great issue @Ayush0Chaudhary. Though we increased our testing in the past, many of the tests are poorly written just for the sake of increasing the coverage. Please be thorough in your testing and use the mocks properly.

[Ayush0Chaudhary]

@literalEval
I was thinking of testing if the mutation used by our mobile app are working properly. Was not thinking about writing tests for them.
Maybe we can do that in other issues.

[literalEval]

That's great.

[Ayush0Chaudhary]

@palisadoes I guess the list is complete.
Should we make a single issue or multiple small issue, Actually these issues are quite small to solve

[palisadoes]

So that means we should close this?

[Ayush0Chaudhary]

Why don't we create individual issues for them?
We can add check boxes in this issue to keep track.
or
I can solve all of the above issue in 1 PR
@palisadoes

[palisadoes]

Fix them in one PR.

[github-actions]

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]

This issue did not get any activity in the past 180 days and thus has been closed. Please check if the newest release or develop branch has it fixed. Please, create a new issue if the issue is not fixed.