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

Update vue-core vitest configuration and sonar properties for front #10833

Merged

Conversation

pascalgrimaud
Copy link
Member

@pascalgrimaud pascalgrimaud added area: bug 🐛 Something isn't working client: vue labels Sep 14, 2024
@qmonmert
Copy link
Contributor

@pascalgrimaud I added tests for HomeRouter #10835 but if it is unused qou can close the PR

@@ -17,7 +17,14 @@ sonar.testExecutionReportPaths={{projectBuildDirectory}}/test-results/TESTS-resu
sonar.javascript.lcov.reportPaths={{projectBuildDirectory}}/test-results/lcov.info

sonar.sourceEncoding=UTF-8
sonar.exclusions=src/main/webapp/main.ts, src/main/webapp/app/main.ts, src/main/webapp/content/**/*.*, {{projectBuildDirectory}}/classes/static/**/*.*, src/main/webapp/app/index.tsx
sonar.exclusions=\
src/main/webapp/app/home/infrastructure/primary/*.*,\
Copy link
Collaborator

Choose a reason for hiding this comment

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

All infrastructure code, from all contextes, should be excluded since we can't get proper metrics on that

Copy link
Collaborator

Choose a reason for hiding this comment

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

In fact, since we can't merge coverrages in front it not a good idea to add a threshold. It will force people to make implementation details tests just to make CI pass

Copy link
Member Author

Choose a reason for hiding this comment

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

I agree on that, but as I'm really short on time.

So I'll keep this like this:

  • so I can do a patch release, fixing the deploy on GCP
  • the coverage will be back at 100% on sample app
  • then, someone can work on this for the next version v1.19.0
    • clean tests on infrastructure
    • update sonar properties propertly
    • keep consistency between angular / react / vue

Copy link
Member Author

@pascalgrimaud pascalgrimaud Sep 14, 2024

Choose a reason for hiding this comment

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

I'll create a dedicated ticket for that -> #10836

@pascalgrimaud pascalgrimaud force-pushed the 10822/vue-core-update-vitest-config branch from bf482d9 to 1b43990 Compare September 14, 2024 10:28
@pascalgrimaud pascalgrimaud merged commit 4ed33cc into jhipster:main Sep 14, 2024
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: bug 🐛 Something isn't working client: vue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vue-core module and coverage
3 participants