Test: src/lib/libraries/logger.ts

[palisadoes]

• Please coordinate issue assignment and PR reviews with the contributors listed in this issue Student Internship Programs talawa#359

The Talawa-API 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/lib/libraries/logger.ts
• We will need the API to be refactored for all methods, classes and/or functions found in this file for testing to be correctly executed.
• When complete, all all methods, classes and/or functions in the refactored file will need to be tested. These tests must be placed in a
  single file with the name __tests__/libraries/logger.spec.ts. 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:

• Create all API Resolver Tests #490

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 by visting this page. Login using your GitHub credentials.
• Create your own codecov.io to help with testing.
• The PR you create will show a report for the code coverage for the file you have added. You can also use that as a guide.

[KrutikaBhatt]

Hey @palisadoes, can I solve this issue?
I have read through the documentation and contribution guidelines. I will make sure to follow those guidelines.

[frey0-0]

is this issue still open? If yes I would like to work on it @palisadoes :)

[palisadoes]

1. Please refer to Tests for src/lib/libraries/logger.ts #951
2. We would like the tests to reach 100% code coverage

[KrutikaBhatt]

Hey @frey0-0, here are certain resources and blogs that I found useful and might help you to understand.

1. Winston logger documentation
2. Unit testing for logger in jest
3. A guide to winston logging
4. You can also check out the usage of winston spy here - Wiston-Spy

Hope this helps!

[noman2002]

@frey0-0 Any update on this one ??

[palisadoes]

Unassigning.

[arunavabasucom]

Can I work on this ?

[palisadoes]

@arunavabasu-03 You already have 2 issues assigned

[arunavabasucom]

I think @palisadoes sir , one of those issue got merged!!

[palisadoes]

We reopened the issue as coverage isn't 100%

[arunavabasucom]

Actually sir , #913 is going to take longer time so i uassign to me , can you assign me this one !!

[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.

[lata-11]

Hey! If this issue is not resolved yet. Can you assign me?

[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.

[Ladyperpetua]

@palisadoes can i please be assigned this issue?

[Ladyperpetua]

Thank you sir @palisadoes . on it

[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.

[palisadoes]

Unassigning due to inactivity and 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.

[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.

[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.

[Tweniee]

@palisadoes can you tell me whats pending in this issue,
as i can see someone already merged the PR related to this issue

[palisadoes]

The file does not have 100% code coverage as mentioned in the issue's initial comment.

@aashimawadhwa will be handling all issue queries and seeking reviewers for PRs. When necessary, this contributor will contact other contributors who will be able to assist. Please ask them for guidance on your future questions.

[aarishshahmohsin]

Can I be assigned this issue?

[lakshz]

Is this issue open? I can find tests/libraries/logger.spec.ts already on the develop branch.
If it's open, I want to work on this. Please assign it to me

[aarishshahmohsin]

I'm unassigning myself from this issue as I couldn't find a solution. I appreciate your understanding.

[palisadoes]

This issue has been attempted multiple times without success. Getting 100% coverage may not be possible.

[Tweniee]

I want to try just need a bit guidance about the project