Community
Participate
Working Groups
The test recording system does not seem to capture keyboard shortcuts - at least not control-S for "Save." To reproduce: 1. Start recording. 2. Choose File > New > File 3. Specify the file's location (your testsuite project will do) and name 4. Type some contents into the file. 5. Press control-S to save the file. 6. Click the "close" box on the file's editor tab. 7. Stop recording. You will see that the captured test script does not contain anything about the control-S action. If this is a limitation of the recording technology, we should document it ("Always use menu items like File > Save, never use keyboard shortcuts") so people aren't quite so surprised later.
Yes, this is a limitation of the tool. I'll mark this as an enhancement to support keyboard binding. I will update 111391 to include this limitation in the userguide document
Setting the version to 4.2 and the target milestone to unspecified. I will wait for the plan until this is approved for 4.2.
Update version to 4.2
Note that keyboard events can be captured if position-based recording is turned on. There are some issues with position-based recording that I will be fixing in defect 110726. Ctrl+S can be simulated with something like: <macro version="0.1" > <shell id="org.eclipse.ui.internal.WorkbenchWindow" return-code="-1"> <command type="key-down" detail="262144" ischarset="false"/> <command type="key-down" detail="19" ischarset="true"/> <command type="key-up" detail="19" ischarset="true"/> <command type="key-up" detail="262144" ischarset="false"/> </shell> </macro>
Capturing keyboard shortcuts is focus dependent (i.e. the editor needs to have focus for the shortcut to have an affect). Any focus dependent command is considered to fall under position-based recording. If position-based recording is enabled, then keyboard shortcuts will be captured as mentioned in the previous command. I'm marking this as won't fix.
ACTION: Please verify/close this defect.
Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
