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 vitest #126

Merged
merged 10 commits into from
Jun 29, 2024
Merged

Add vitest #126

merged 10 commits into from
Jun 29, 2024

Conversation

hwinther
Copy link
Owner

@hwinther hwinther commented Jun 29, 2024

Add vitest, workflow reporting of test results and coverage, and one basic test + mocks to get it running

Description 💬

Motivation and Context 🥅

How has this been tested? 🧪

  • Local build ⚒️
  • Local tests 🧪
  • (optional) Local run and endpoint tested in swagger 🚀

Screenshots (if appropriate) 💻

Types of changes 🌊

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist ☑️

  • The pull request title starts with the jira case number (when applicable), e.g. "TEST-1234 Add some feature"
  • The person responsible for following up on requested review changes has been assigned to the pull request
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Highly optional checks, only use these if you have a reason to do so ✔️

  • This PR changes the database so I have added the create-diagram label to assist reviewers with a db diagram
  • This PR changes platform or backend and I need others to be able to test against these changes before merging to dev, so I have added the deploy-azure label to deploy before merging the PR

Checklist for the approver ✅

  • I've checked the files view for spelling issues, code quality warnings and similar
  • I've waited until all checks have passed (green check/without error)
  • I've checked that only the intended files are changed

@hwinther hwinther self-assigned this Jun 29, 2024
@hwinther hwinther enabled auto-merge (squash) June 29, 2024 23:10
@github-actions github-actions bot added dependencies Pull requests that update a dependency file frontend labels Jun 29, 2024
Copy link

github-actions bot commented Jun 29, 2024

frontend

✅ Build successful

✅ No linting issues 🎊

Copy link

Todo Commenter

.github/actions/frontend-build/action.yml
TODO:
  • ,FIXME:,BUG:" Line: 150
FIXME:
  • ,BUG:" Line: 150
BUG:
  • " Line: 150
src/frontend/src/mock.ts
TODO:
  • can be used to mock the API during development Line: 1
src/frontend/src/test/testUtils.tsx
TODO:
  • also remove it afterAll Line: 41

@hwinther Please take a look 👀

Copy link

Code Coverage

Package Line Rate Branch Rate Health
frontend 0% 100%
frontend.src 0% 0%
frontend.src.api.endpoints.blogging 17% 0%
frontend.src.api.endpoints.send-message 20% 0%
frontend.src.api.endpoints.service 65% 22%
frontend.src.api.endpoints.weather-forecast 91% 50%
frontend.src.api.mutators 86% 100%
frontend.src.pages._error 0% 0%
frontend.src.pages.about 100% 100%
frontend.src.pages.blogs 0% 100%
frontend.src.pages.blogs.@id 0% 0%
frontend.src.pages.index 78% 100%
frontend.src.renderer 0% 0%
frontend.src.test 88% 50%
Summary 31% (97 / 310) 8% (12 / 160)

@hwinther hwinther disabled auto-merge June 29, 2024 23:37
@hwinther hwinther merged commit 1832ea5 into dev Jun 29, 2024
21 checks passed
@hwinther hwinther deleted the feature/TEST-0005-Add-vitest branch June 29, 2024 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file frontend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant