Community
Participate
Working Groups
Though we don't open native message boxes during replay, we still should be able to intercept their properties like title and message. It would be great if we could give an ability to assert their properties. Some suggestions on how it might look like: set-dialog-result MessageBox 128 get-view "Quality Mockups" | get-group "MessageBox Test" | get-button "Message Box with YES/NO Buttons" | click with [get-last-message-box] { get-property title | equals "Warning" | verify-true get-property message | equals "Yes or No?" | verify-true }
New Gerrit change created: https://git.eclipse.org/r/54103
Verified on https://git.eclipse.org/r/54103 RCPTT Test added.
Gerrit change https://git.eclipse.org/r/54103 was merged to [master]. Commit: http://git.eclipse.org/c/rcptt/org.eclipse.rcptt.git/commit/?id=620d170fc775b51c812827debd5f5561c708857a
Fixed in https://git.eclipse.org/r/54103. The script should be written manually and look like: set-dialog-result MessageBox 256 get-view "Q7 Quality Mockups" | get-group "MessageBox Test" | get-button "Message With Question" | click get-last-message-box | get-property title | equals "Question" | verify-true get-last-message-box | get-property message | equals "This MessageBox with question" | verify-true
Fixed
See https://www.eclipse.org/rcptt/documentation/faq/assert-native-message-box/ for the details.
