A Selenium UI recording tool is a good starting point to help people learn. Quickly though it becomes pretty limiting and specialized testers need to switch over to using code.
The Selenium IDE I like using at this point is Oxygen. It's Atom with a Selenium recorder built in. It records and gives you code with details about the XPath and CSS Selectors provided in comments above each recorded action. It's the best tool I've found for quickly getting off of record-playback dependency and into working with code. The Oxygen IDE provides intellisense and real debugging. It strikes the right balance of allowing you to record when you need to, but then getting out of the way and providing you with a real IDE so you can work with the code.
The Selenium IDE I like using at this point is Oxygen. It's Atom with a Selenium recorder built in. It records and gives you code with details about the XPath and CSS Selectors provided in comments above each recorded action. It's the best tool I've found for quickly getting off of record-playback dependency and into working with code. The Oxygen IDE provides intellisense and real debugging. It strikes the right balance of allowing you to record when you need to, but then getting out of the way and providing you with a real IDE so you can work with the code.
http://oxygenhq.org
I did a blog post not too long ago about some of it's quirks on Windows... https://scriptmonkey.wordpress.com/2016/06/03/oxygen-for-sel...