Improve jmix-testing skill: add Masquerade E2E, test type comparison, and fix gaps#7
Open
edurbs wants to merge 1 commit into
Open
Improve jmix-testing skill: add Masquerade E2E, test type comparison, and fix gaps#7edurbs wants to merge 1 commit into
edurbs wants to merge 1 commit into
Conversation
… fix gaps - Add test type comparison table for quick reference - Add End-to-End UI Tests (Masquerade) section with setup, view wrappers, writing tests, imports, Selenide config, and fragments - Clarify @TestComponent vs @findby distinction - Add Key Packages table mapping annotations/classes to packages - Add @ExtendWith(AuthenticatedAsAdmin.class) to integration test examples - Add doc reference links for UI integration tests and Masquerade - Clarify @uitest behavior (starts Vaadin + configures views + auth) - Update checklist and forbidden sections Closes jmix-framework#6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
@TestComponentvs@FindBydistinction (Masquerade vs Selenium annotations)@ExtendWith(AuthenticatedAsAdmin.class)@UiTestbehavior in the section descriptionCloses #6
Changes
Test Type Comparison (new)
A quick-reference table so agents immediately pick the right approach instead of guessing between
@UiTestand Masquerade.Masquerade Section (new)
Complete coverage of the Masquerade E2E testing library:
jmix.ui.ui-test-mode=true+ Selenide configurationui_autotest/for tests,test_support/view/for wrappers@TestView, extendingio.jmix.masquerade.sys.View<T>@TestComponent(preferred) vs@FindBy(Selenium fallback)Selenide.open(),Masquerade.$j(), Selenide assertions$j()overloads documented$j(WrapperClass.class)@TestComponentvs@FindByClarification (new)Explains the most confusing aspect for agents:
@TestComponentis Masquerade's annotation — field name matchesj-test-idby default@FindByis a Selenium annotation (org.openqa.selenium.support) — use only for elements withoutj-test-idj-test-idHTML attribute is generated whenjmix.ui.ui-test-mode=trueMinor Fixes
@ExtendWith(AuthenticatedAsAdmin.class)(was missing — agents would copy without auth)@UiTestsection now explains what the annotation doesReferences