-
-
Notifications
You must be signed in to change notification settings - Fork 341
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
[runtime] hide queries in the browser #1155
Conversation
Your Render PR Server URL is https://toolpad-pr-1155.onrender.com. Follow its progress at https://dashboard.render.com/web/srv-cd43d3ta499ckjpeeeug. |
await editorModel.componentEditor.waitFor(); | ||
await editorModel.componentEditor.waitFor({ state: 'visible' }); | ||
|
||
const labelControlInput = editorModel.componentEditor.getByLabel('label', { exact: true }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i guess i hadn't found this selector that gets the input for a label? seems pretty useful
await labelControlInputLocator.fill(TEST_VALUE_2); | ||
|
||
await expect(firstInputLabelLocator).toHaveText(TEST_VALUE_2); | ||
await inputByLabel.waitFor({ state: 'visible' }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we're not checking if the value in the label matches in the end anymore? Was there any issue with that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes we are, if the value doesn't match this selector wouldn't locate elements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh it checks with that value already, i missed that. looks good then!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for improving that test, it's definitely an improvement!
I was waiting to see if it was still flaky or if the issue that made it flaky was unrelated, it was seeming a bit less flaky lately.
Just left a question about one of the changes to the test.
Fixes #1052
@apedroferreira had a bit of trouble with the propControls test. I refactored the locators to be a bit more stable