Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: setup code coverage #5

Open
3 tasks
richard-ramos opened this issue Nov 15, 2022 · 0 comments
Open
3 tasks

chore: setup code coverage #5

richard-ramos opened this issue Nov 15, 2022 · 0 comments
Labels
test Issue related to the test suite with no expected consequence to production code track:conversational-security Conversational security track (Secure Messaging)

Comments

@richard-ramos
Copy link
Member

richard-ramos commented Nov 15, 2022 •
edited by fryorcraken
Loading

Problem

There is no code coverage tracking in js-noise.

js-noise is a small purpose focus library so high coverage should be expected

Acceptance Criteria

  • Decide on tooling to generate coverage and do it
  • Decide on tooling to track coverage as part of PR flow and do it
  • Review current coverage, decide on target, improvement and do them

Notes

Migration to Jest is likely to make this easier.
@fryorcraken fryorcraken added this to Waku Nov 15, 2022
@fryorcraken fryorcraken moved this to Triage in Waku Feb 22, 2023
@fryorcraken fryorcraken added test Issue related to the test suite with no expected consequence to production code track:conversational-security Conversational security track (Secure Messaging) labels Mar 23, 2023
@fryorcraken fryorcraken moved this from Triage to To Do in Waku Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
test Issue related to the test suite with no expected consequence to production code track:conversational-security Conversational security track (Secure Messaging)
Projects
Waku
Status: To Do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richard-ramos @fryorcraken