The Eclipse Foundation is home to the Eclipse IDE, Jakarta EE, and
hundreds of open source projects, including runtimes, tools,
specifications, and frameworks for cloud and edge applications, IoT, AI,
automotive, systems engineering, open processor designs, and many others.
The Eclipse Foundation is an international non-profit association
supported by our members, including industry leaders who value open
source as a key enabler for their business strategies.
Whether you intend on contributing to Eclipse technologies that are
important to your product strategy, or simply want to explore a specific
innovation area with like-minded organisations, the Eclipse Foundation is
the open source home for industry collaboration.
The Eclipse community consists of individual developers and organisations
spanning many industries. Stay up to date on our open source community
and find resources to support your journey.
The Eclipse Foundation provides our global community of individuals and
organisations with a mature, scalable, and vendor-neutral environment for
open source software collaboration and innovation.
Verification name. This name is automatically synced with file system name. Symbols in name which are not allowed in file names are replaced with
underscore character.
Comma-separated list of arbitrary hierarchical tags, i.e. resourcePerspective, jira/PC-1352, windows-only
Make a snapshot of AUT widget defined in
Widget field and copy it into verification.
Verifies whether AUT tree/table defined in
Widget matches the tree/table from a verification.
AUT tree/table widget for verification. You can set the value manually or using
Pick... button.
Styles option for verification. Can be All/Ignore Styles/Ignore Styled Text.
Turned on by default. If this option is off - verification fails if there are uncaptured children in AUT tree.
Turned on by default. If this option is off - verification ignores icons.
Captured tree/table.
Tree/Table verification is the most convenient way to assert the whole tree/table state at the end of the test case.
It is simpler than ECL assertions, where you explicitly select a separate tree/table items to verify their properties.
Style verification options
There are three options for style verification:
All
Ignore Styles
Ignore Styled text
All
Tree appearance is verified as is:
Verification fails if text style or content changes.
Ignore Styles
Styled text is verified as a plain text:
Verification fails if text content changes. Any style is accepted.
Ignore Styled Text
If there is a styled text - it will be ignored:
Verification fails if any unstyled text changed. Styled text may have any styles or content.