[WICKET-7030] Add Convenience Methods in BaseWicketTester

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 10.0.0-M1
• Component/s: wicket-core
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Johannes Renoth
• Created: 13/Mar/23 16:40
• Updated: 15/Mar/23 08:20
• Resolved: 15/Mar/23 08:20

Description

Since BasewicketTester does not have methods to conveniently search for components by wicket ID only, ignoring the path from last last rendered page, we could add them.

For example we could add

Optional<Component> getFirstComponentByWicketId(String id)
List<Component> getAllComponentsByWicketId(String id)

to enable the Tester to do the following without the manual use of IVisitor

tester.startComponentInPage(myComponent);

var nestedComponent = tester.getFirstComponentByWicketId("myNestedComponent");

assertThat(nestedComponent).isPresent(). ...

// Other Example
tester.startComponentInPage(myComponentWithListView);

var result = tester.getAllComponentsByWicketId("repeterNestedItem");

assertThat(result).hasSize(4)
.extracting(c -> c.isVisible())
.containsExactly(true, false, true, true);

Issue Links

• links to: GitHub Pull Request #555
• links to: Pull Request