[wjg]

Point-and-click is definitely THE next technical milestone. And I think it's essential, because right now I have a bit of a conflicting message to QA analysts: stop fumbling with writing automation scripts and come into my environment and ... write automation scripts!

I think such a feature would go a long way in eliminating that initial "so I have to write the automation?" hurdle, and I agree it provides a clearer and shorter path to extracting value from the product.

I appreciate the feedback!

[glougheed]

The thing that I have found about point and click however is that some issues can't be solved with this method. I really like the idea of positioning it as a starter and you can augment that script from this point. So are you thinking about them being able to edit the output as well?

[wjg]

Exactly. There was a time when I didn't want to do point-and-click at all because it is very limited, like you say. But, it might be the spark needed to get someone to try it initially.

Maybe a "Record Automation" button, that when clicked will record the user's actions and output a basic Flytrap script that enters values / clicks page items.

From there, they can manually edit the generated script to perform more elaborate automations.

It may get the user to dip their toes in the water without the commitment of having to learn a language just to test a product out.

Really appreciate your thoughts.