The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
If you want to stay informed about news about QF-Test, you can simply subscribe to our newsletter:
Subscribe to Newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [QF-Test] Different JDialogs with the same title, different components?
Hey everyone, We are using QFTest to test a Java Swing application and we have some questions regarding the identification of components, particularly the swing JDialogs. In the SUT we are testing, a JDialog pops up every time the user fills a form incorrectly, displaying a warning message about what is missing in the form. When recording the filling form action, QFTest detects the pop up of the warning JDialog as if it was always the same component no matter what warning message is displayed. Is there any way to make QFTest see the different dialogs displaying the different warning messages as if they were different components? Note that the title of the warning JDialogs is always the same (Warning!), is this what is making QFTest see the different JDialogs as if they were all the same component? In our testing we would like to react differently depending on the type of warning JDialog received, what would be the best approach if what suggested above is not possible? Using if sentences to check the content of the JDialog? Thanks in advanced, Best regards, Joaquín
|
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.