| Summary: | Windows automation framework "XAML" - support control "Border" | ||
|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Markus Tiede <markus.tiede> |
| Component: | RC | Assignee: | Project Inbox <jubula.rc-inbox> |
| Status: | CLOSED FIXED | QA Contact: | Oliver Goetz <Oliver.Goetz> |
| Severity: | enhancement | ||
| Priority: | P2 | CC: | alexandra.schladebeck, sebastian.jubula |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 425256, 426981 | ||
|
Description
Markus Tiede
I'm marking this as wontfix since I am reasonably sure that we won't be adding any support for borders. We don't support borders in other toolkits, and the range of meaningful actions for a functional test is probably incredibly limited. If someone has other arguments, please reopen with more information. Re-opening (as we need to check whether we need implicit support for this) and setting the dependency as mentioned in comment 1. We support this component. I checked the object mapping and executed a small test on some buttons inside this container successfully. Verified. I was able to map components inside a Border container and successfully executed simple click tests on it. |