Skip to content

Conversation

@greypilgrim
Copy link
Contributor

@greypilgrim greypilgrim commented Sep 3, 2025

PR Description

Configure coverage with jest

What type of PR is this? (check all applicable)

  • πŸ”§ Feature
  • πŸ› Bug Fix
  • πŸ“ Documentation Update
  • 🎨 Style
  • πŸ’» Code Refactor
  • πŸ”₯ Performance Improvements
  • βœ… Test
  • πŸ”¨ Build
  • πŸ” CI

Why is this PR important?

To adequately test code, search for dead code, etc.

Related Tickets & Documents

@Verus20 LL-351

How to test

  1. Open terminal in repo
  2. run npm i
  3. run npx jest
  4. Confirm report was generated
  5. profit

Added to documentation?

  • πŸ“œ README.md
  • πŸ““ Github pages
  • πŸ“• Confluence
  • πŸ†• Other (if so please list here)
  • ❌ no documentation needed

[optional] What gif best describes this PR?

https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExNGlkcjMyMnplZng3NmV6d243bDAwM3ZoaHp5b3dneGQ3eW1pY2F3OCZlcD12MV9naWZzX3NlYXJjaCZjdD1n/6d1Q6XoDH4Kl7pc36D/giphy.gif

@greypilgrim greypilgrim marked this pull request as ready for review September 3, 2025 04:35
@greypilgrim greypilgrim requested a review from pogi7 September 3, 2025 04:36
@pogi7 pogi7 requested a review from Verus20 September 3, 2025 05:13
Copy link
Contributor

@pogi7 pogi7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to defer to @Verus20 for merging this code, since it's related to his ticket.
Please title PRs with the ticket name somewhere in the PR title. So LL-346 would be a good PR title name.

Copy link

@Verus20 Verus20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd recommend adding in some documentation to the README to explain how to run code coverage, i.e if you were showing someone new to LL how to run code coverage how would they go about doing that?

other then that doc update, lgtm

@greypilgrim greypilgrim changed the title Create test directory LL 346: Create test directory Sep 12, 2025
…lude instructions on running coverage testing

Signed-off-by: greypilgrim <[email protected]>
@greypilgrim
Copy link
Contributor Author

@pogi7 @Verus20 Made the changes and pushed, just need review(if necessary) and okay to merge

Copy link
Contributor

@pogi7 pogi7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

Copy link

@Verus20 Verus20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

LL-351: Setup testing framework for browser repo
@codecov
Copy link

codecov bot commented Sep 26, 2025

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

@pogi7
Copy link
Contributor

pogi7 commented Sep 26, 2025

CI/CD fails since no passes are defined yet. Will add tests in other PRs.

@pogi7 pogi7 merged commit 7b1eabf into master Sep 26, 2025
1 check failed
@pogi7 pogi7 deleted the LL-346-Setup-code-coverage-for-browser-repo branch September 26, 2025 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants