test: abbreviate integration to int, rename vitest config files

[matejchalk]

Motivation

• I find it quite cumbersome to type out integration-test repeatedly, abbreviating to int-test would be more convenient.
• The vite.config.{type}.ts file pattern doesn't realiably recognized by tooling because of the custom suffixes. Also, it may not be clear that the configuration is only for Vitest, not for Vite - vitest.config.ts naming is another standardized config file name, which would be more appropriate in our case.

Changes

• Renamed *.integration.test.ts files to *.int.test.ts.
• Renamed vite.config.{unit|integration|e2e}.ts files to vitest.{unit|int|e2e}.config.ts.
• Replaced all references to changed files as needed.

Follow-up

For running E2E tests, typing out npx nx nxv-e2e <project>-e2e is cumbersome. I'd like to rename the nxv-e2e target to e2e-test. Then all our testing targets would have intuitive names - unit-test, int-test, e2e-test.

I've submitted a PR to @push-based/nx-verdaccio which adds an option to rename the inferred nxv-e2e target. Once that's released, we can rename the target on our end.

• feat: support custom target names push-based/nx-verdaccio#79

[github-actions]

Code PushUp

😟 Code PushUp report has regressed – compared current commit b7a003d with previous commit f0a2a01.

🕵️ See full comparison in Code PushUp portal 🔍

🏷️ Categories

🏷️ Category	⭐ Previous score	⭐ Current score	🔄 Score change
Performance	🟡 56	🟡 51
Code coverage	🟢 91	🟢 90
Security	🟡 61	🟡 61	–
Updates	🟡 77	🟡 77	–
Accessibility	🟢 92	🟢 92	–
Best Practices	🟢 100	🟢 100	–
SEO	🟡 61	🟡 61	–
Type Safety	🟢 100	🟢 100	–
Bug prevention	🟢 100	🟢 100	–
Miscellaneous	🟢 100	🟢 100	–
Code style	🟢 100	🟢 100	–
Documentation	🔴 23	🔴 23	–

👎 2 groups regressed, 👎 7 audits regressed, 10 audits changed without impacting score

🗃️ Groups

🔌 Plugin	🗃️ Group	⭐ Previous score	⭐ Current score	🔄 Score change
Lighthouse	Performance	🟡 56	🟡 51
Code coverage	Code coverage metrics	🟢 91	🟢 90

19 other groups are unchanged.

🛡️ Audits

🔌 Plugin	🛡️ Audit	📏 Previous value	📏 Current value	🔄 Value change
Lighthouse	Speed Index	🟨 5.1 s	🟨 5.8 s
Lighthouse	Largest Contentful Paint	🟨 3.4 s	🟨 3.7 s
Lighthouse	Total Blocking Time	🟥 1,660 ms	🟥 2,450 ms
Code coverage	Line coverage	🟩 90.2 %	🟨 86.5 %
Lighthouse	Time to Interactive	🟥 12.3 s	🟥 13.0 s
Lighthouse	First Contentful Paint	🟥 3.0 s	🟥 3.1 s
Code coverage	Branch coverage	🟨 86.3 %	🟨 85.7 %
Lighthouse	Avoids enormous network payloads	🟩 Total size was 1,901 KiB	🟩 Total size was 1,942 KiB
Lighthouse	Minimizes main-thread work	🟥 10.3 s	🟥 13.0 s
Lighthouse	JavaScript execution time	🟥 4.9 s	🟥 6.3 s
Lighthouse	Max Potential First Input Delay	🟥 1,110 ms	🟥 1,790 ms
Lighthouse	Metrics	🟩 100%	🟩 100%
Lighthouse	Uses efficient cache policy on static assets	🟨 30 resources found	🟨 30 resources found
Lighthouse	Server Backend Latencies	🟩 110 ms	🟩 170 ms
Lighthouse	Network Round Trip Times	🟩 30 ms	🟩 40 ms
Lighthouse	Initial server response time was short	🟩 Root document took 420 ms	🟩 Root document took 410 ms
Lighthouse	Cumulative Layout Shift	🟩 0	🟩 0

587 other audits are unchanged.

[vmasek]

Thanks for doing this, I experimented with similar changes in past as the DX was not good testing wise.
I'll try out if JB IDE picks it up now.