The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
But if you want to stay informed about news about QF-Test, you can simply
Subscribe to Newsletter
To get up-to-date information about each release - including minor releases - you can
subscribe to the RSS feed or follow us on social media.
Alternatively, QF-Test also provides release information itself.
Another source of information is our blog, where there are current articles on general topics, on the company QFS and also various "how-tos"
subscribe to blog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] Hot keys not working properly
Hello Polihron, Thank you for providing a run-log with the details. for the record, I'm answering to the whole list as this is quite interesting. Hot-key processing is different for each GUI toolkit and it is not always compatible with the optimizations and filtering QF-Test applies during recording in order to get concise tests. In your case - associated labels in Swing - the PRESSED, TYPED and RELEASED events must be replayed to different component. Most notably, the RELEASED has to happen on the label. Please try to temporarily disable the option Record->Events->Abstract keystroke events when recording hot-keys. Instead of a single keystroke you should get three (or more, for the Alt key) nodes for PRESSED, TYPED and RELEASED events. In my experiment, replaying these consistently moved the focus to the right place. If it still doesn't work, please send another run-log directly to me. Again for the record: Because QF-Test automatically ensures focus for the target of key or text input events, we don't make use of hot-keys during normal tests. As a dedicated test this may still be a good idea when followed by a 'focused' check to ensure the mnemonics for keyboard shortcuts were assigned correctly. Best regards, Greg Gregor Schmid <Gregor.Schmid@?.de> writes: > Hello Polihron, > > I'm afraid it's a bit difficult to answer this question without > detailed information. > > Could you please set the option > > Run-log->Content->Number of events to log for error diagnosis > > to 1000, re-run the failing sequence and send it to our support? > > Please make sure that there's an error after the failing key event, > either by checking for some result you didn't get or by adding an SUT > script with > > rc.logError("dummy error") > > Best regards, > Greg > > Polihron Markendudis <p.markendudis@?.com> writes: > >> Hello QF community, >> We've been having a problem with the functionality of hot keys for a software we are currently >> testing. The issue apperas as we try to record an action, witch replicates the usage of a specific >> hot key. For exaple: >> >> I have a textfield "Name" and if I press Alt + N, the field gets focused ( the cursor appears). As >> i record the event and run it , the cursor appears for just a second and then dissappears, leaving >> the textfield unselected. >> >> In a manual test everything seems to work ok with the hot keys. The same issue appears with >> comboboxes aswell. >> >> Hot key functions work fine if i try to select a button ( Ex: Alt + C for a "Cancel" button) , so >> i guess it is just when selection is involved. >> >> Any feedback will be appreciated, thanks. >> >> _______________________________________________ >> qftest-list mailing list >> qftest-list@?.de >> http://www.qfs.de/mailman/listinfo/qftest-list -- Gregor Schmid E: gregor.schmid@?.de T: +49 8171 38648-11 F: +49 8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer HRB München 140833
|
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.