Repository navigation
test: move components integration tests to own package - #3896
Conversation
Co-authored-by: Sergey Vinogradov <mr.vursen@gmail.com>
|
Kudos, SonarCloud Quality Gate passed!
|
tomivirkki
left a comment
There was a problem hiding this comment.
Getting rid of the unnecessary devDependencies in component packages makes sense, but should the integration tests still run for a PR targeting one of the components used in the ITs? They're not too heavy after all and the parallel run would probably eliminate increases in the total test duration.
Yes, that's how it already works. We get changed packages and if for example |
|
This ticket/PR has been released with Vaadin 23.1.0.rc1 and is also targeting the upcoming stable 23.1.0 version. |








Description
Fixes #3892
Type of change