Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
E2E: Improve support to interact with panel edit options #1272
base: main
Are you sure you want to change the base?
E2E: Improve support to interact with panel edit options #1272
Changes from 12 commits
e0abc09
f82174a
03ab082
95e8075
03dbc35
6a75306
4ea35b0
ef91a82
b5a1776
6f3f4ac
ef666ca
3441a14
c73e46f
dd03be6
09e628a
fffa740
82629ba
858b5fe
52fdb3d
b8d32a2
9a76a3a
64160a0
7bbe0bd
c36f555
44c31f3
bd9eac6
3570835
1138214
94798d1
8bb16e9
a410338
760ad9e
6d42378
57e103c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Isn't there an e2e selector for this? If not, we should add one to Grafana.
One problem with this and the other new matchers is that that they don't have access to the test context. There's no way for them to check grafanaVersion and use the resolved selectors.
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.
But IDK - the Selector class has access to the context, so maybe it can be encapsulated there instead?
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.
hmm, that is a valid concern. But I think we can fix that in the
index.ts
file.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.
The
ctx
is available with that the selectors as well. So I will see if I can change these to selectors from the grafana-selectors package istead.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.
How? This is fine in older versions of Grafana, but we need a stable e2e-selector in Grafana to be future proof. Looks like there's a data-testid set here. Can we use that instead of the classnames?
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.
hmm, I don't think we pass the data-testid when rendering the select component. Or I can't find it in the dom.
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.
Okay, can we add a new one 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.
Here as well. This is fine in older versions of Grafana, but now can we add a selector to this element?