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.

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

add jest coverage threshold #12

Closed
wants to merge 1 commit into from

Conversation

harley-harris
Copy link
Contributor

@harley-harris harley-harris commented Jan 4, 2024

DRAFT PR DO NOT MERGE

USED TO TEST GITHUB ACTION.

This draft PR has been preserved to keep a record of the conversation notes and to account for branch renaming, see #13 for implementation

Copy link

github-actions bot commented Jan 4, 2024

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 97.33% 73/75
🟢 Branches 100% 16/16
🟢 Functions 90% 18/20
🟢 Lines 100% 64/64

Test suite run success

29 tests passing in 7 suites.

Report generated by 🧪jest coverage report action from d799045

@harley-harris harley-harris force-pushed the NTRNL-281-add-jest-coverage-threshold branch 6 times, most recently from bb7b1c8 to 0a33886 Compare January 4, 2024 14:29
@@ -19,3 +19,6 @@ jobs:
- run: npm ci
- run: npm run build
- run: npm test

- name: Jest Coverage Report
Copy link
Contributor

Choose a reason for hiding this comment

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

I would have created another config file, something like

name: Jest Coverage Report

on: [pull_request]

jobs:
  jest-coverage-report:

    runs-on: ubuntu-latest

    steps:
      - name: Checkout Repository
        uses: actions/checkout@v4

      - name: Coverage Report
        uses: ArtiomTr/jest-coverage-report-action@v2  

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I had to add this to the step:

        uses: actions/setup-node@v3
        with:
          node-version: '20.x'

as the coverage report was failing to build the report without it

Copy link
Contributor

Choose a reason for hiding this comment

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

It looks good to me 👍, change the node action to latest version actions/setup-node@v4

@harley-harris harley-harris force-pushed the NTRNL-281-add-jest-coverage-threshold branch 5 times, most recently from 34d42ac to 45938f7 Compare January 5, 2024 11:45
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.

2 participants