Repository navigation
test: improve test coverage for value commit scenarios - #6429
Conversation
| expect(numberField.inputElement.validity.badInput).to.be.true; | ||
| }); | ||
|
|
||
| it('should not commit but validate on Enter', async () => { |
There was a problem hiding this comment.
This test fails due to a missing Enter handler for handling bad input: #5113
There was a problem hiding this comment.
After an internal discussion, we've decided to skip this test for now. The issue will be fixed later.
| expectValidationOnly(); | ||
| }); | ||
|
|
||
| it('should not commit but validate on Enter', async () => { |
There was a problem hiding this comment.
This test fails due to a missing Enter handler for handling bad input: #5113
There was a problem hiding this comment.
After an internal discussion, we've decided to skip this test for now. The issue will be fixed later.
1c46ae6 to
4e3286c
Compare
Co-authored-by: Serhii Kulykov <iamkulykov@gmail.com>
|
Kudos, SonarCloud Quality Gate passed!
|
|
This ticket/PR has been released with Vaadin 24.2.0.alpha11 and is also targeting the upcoming stable 24.2.0 version. |








Description
The idea is to create a test file that would collect all the tests related to the user committing a value. Currently, such tests are scattered across different places, making it difficult to know what might cause the value to change and feel confident about the test coverage when refactoring something.
The new tests aim to cover all main scenarios where the user commits a value using actions like blur, Enter.
Depends on
Part of #6426
Type of change