Dima Kovalenko
unread,Mar 23, 2009, 4:08:04 PM3/23/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to selenium-users...@googlegroups.com
Gotcha, well being in QA i run into the position of having to type out the steps to replicate a bug in step by step sequence.
What i found out is, I can record a script in IDE and then save it as HTML file, then attach the HTML file to the bug report so that the developer can run it on his own IDE instance.
So, the easiest way to share the recorded selenium scripts is, after you are finished recording, go to File>Save Test Case, and save the file as HTML. Then on the other IDE, you can go to File>Open and open the test case you just recorded.
Take this with a little grain of salt, because most people come to conclusion that "Record/Playback" is a big marketing scheme, and there is not a single test application that will work perfectly like that. If the page loading times change, or the text is re-written on the website, some things that expect those fluid references might break.
I'll recomend a couple of suggestions so that one person can record a script and another person can run it easily.
1) add sleep, and wait commands everywhere while recording. If you recorded a click to submit a query, add a "wait for page to load" command after the click.
2) If you going to add some asserts, or verifications, make sure you check for text that you know wont change too often, or your script will just fail
3) make sure you are aware if developers change the IDs and Names of elements often, because that might break things.
\\ But you can give selenium IDE to some non-techy people and have them record scripts like they would and give them to programmers. Programmers might have to add some short delays and sleeps here and there, but it will work just fine 98% of the time.