chore: auto-generate Lit test files #8561
Conversation
vursen
changed the title
vursen
force-pushed
the
auto-generate-lit-tests
branch
from
f29a54c to
7294d27
Compare
scripts/generateLitTests.js
Outdated
| return !/(-polymer|-lit)(\.generated)?\.test/u.test(testPath); | ||
| }) | ||
| .forEach((testPath) => { | ||
| console.log(testPath); |
There was a problem hiding this comment.
Could be moved into the if condition below so this only gets logged if the symlink doesn't exist yet. Otherwise it creates noise on every test run.
There was a problem hiding this comment.
Thanks, it's actually a leftover from the development. I'll remove it completely.
|
|
Hi @vursen and @vursen, when i performed cherry-pick to this commit to 24.5, i have encountered the following issue. Can you take a look and pick it manually? |
Co-authored-by: Sergey Vinogradov <[email protected]>
Co-authored-by: Sergey Vinogradov <[email protected]>
Co-authored-by: Vaadin Bot <[email protected]>
|
This ticket/PR has been released with Vaadin 24.7.0.alpha7 and is also targeting the upcoming stable 24.7.0 version. |
Description
The PR introduces automatic generation of Lit test files using symlinks:
generateLitTestsscript creates[name]-lit.generated.test.jssymlinks for[name].test.jstest files for components that have a Lit version. This effectively causes web-test-runner to run the same file twice while displaying them as separate files in the list of test files, which preserves the ability to open and debug these files separately.[name]-lit.generated.test.js.-lit.test.jsand-polymer.test.js, which makes it possible to transition back to a single test file approach gradually.Type of change