# Testing point picking
**URL:** https://discourse.paraview.org/t/testing-point-picking/3524
**Category:** Development
**Created:** [February 6, 2020, 8:51pm UTC](https://discourse.paraview.org/t/testing-point-picking/3524 "2020-02-06T20:51:10Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@dcthomp](https://discourse.paraview.org/u/dcthomp)
#### Post date: [February 6, 2020, 8:51pm UTC](https://discourse.paraview.org/t/testing-point-picking/3524/1 "2020-02-06T20:51:10Z")
Is there a way to record and play back render-window pick events (the ‘p’, ‘1’, and ‘2’ keys; with or without Ctrl/Cmd modifiers used to snap to dataset points)? The key presses appear to be recorded but do not result in pick events upon playback. I don’t see any existing ParaView tests of picking. Should we be adding something to QtTesting that observes these events and emits something other than keypresses?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [February 7, 2020, 2:27am UTC](https://discourse.paraview.org/t/testing-point-picking/3524/2 "2020-02-07T02:27:53Z")
Qt testing is missing that, but to be honest it is missing lots of feature to make it more viable as a generic tool. You may want to open an issue though :
[https://gitlab.kitware.com/paraview/qttesting/issues](https://gitlab.kitware.com/paraview/qttesting/issues)
In any case, testing picking would require interacting with the viewport widget, which is always finicky as the coordinate of the position of the mouse can vary depending on the system/resolution it is used on.
---
### Author:  [@dcthomp](https://discourse.paraview.org/u/dcthomp)
#### Post date: [February 7, 2020, 1:51pm UTC](https://discourse.paraview.org/t/testing-point-picking/3524/3 "2020-02-07T13:51:25Z")
Thanks Mathieu. I’ve [filed an issue](https://gitlab.kitware.com/paraview/qttesting/issues/25); finicky as it may be, it is picking for widgets that we need to test.