-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Dev UI Testing #34090
Dev UI Testing #34090
Conversation
9aab9fb
to
8cb021f
Compare
Signed-off-by: Phillip Kruger <[email protected]>
Signed-off-by: Phillip Kruger <[email protected]>
Signed-off-by: Phillip Kruger <[email protected]>
572e2b4
to
1018d93
Compare
This comment has been minimized.
This comment has been minimized.
Sure, will do. Those are not DevUI tests though, we can only test GRPC services from what I can see. In the old DevUIs at least some of the bugs we had were related to issues in the HTML or templates... which we won't catch here. I suppose that's the best we can do easily with these more advanced Javascript-based UIs. |
Ok, from what I could see the existing tests mostly test data, even though that was part of html. I'll add more tests in the future that can test html , that is where we will probably use playwright |
This PR introduce a base class that can be used to test JsonRPC and Build time data calls for Dev UI.
It also:
@yrodiere - The Dev UI tests can now live in the extension (so move from integration-tests to extension). I did not move the Hibernate Search extension tests (I see the tests are skipped in the extension). Can you do the move in another PR ?